Note: "When client side OCI or NET have an incident, an ADR directory is created in the user's home and the incident and dumps are located within.
The root is named oradiag_<username>. So finding this directory structure indicates some failure on the client side.
The reason the ADR is created in the user's home directory and not in the Client Oracle home: permissions.
I was puzzled that my db server host had this directory even though I've never installed the Client there. Dev explained that "Every DB interaction
uses OCI (SQLPLUS, etc.) from a client side." Thus you use it during install, for example, often without knowing it.
set linesize 121
col value format a75
SELECT * FROM gv$diag_info;
Change the ADR Repository Location
ALTER SYSTEM SET diagnostic_dest = <new location>;
Add the parameter ADR_BASE_listener=<location> to the listener.ora file
The ADR Command Interpreter (ADRCI) is a command-line tool that you use to manage Oracle Database diagnostic data.
ADRCI is a command-line tool that is part of the fault diagnosability infrastructure introduced in Oracle Database Release 11g. ADRCI enables:
Viewing diagnostic data within the Automatic Diagnostic Repository (ADR).
Viewing Health Monitor reports.
Packaging of incident and problem information into a zip file for transmission to Oracle Support.
Diagnostic data includes incident and problem descriptions, trace files, dumps, health monitor reports, alert log entries, and more.
ADRCI has a rich command set, and can be used in interactive mode or within scripts.
In addition, ADRCI can execute scripts of ADRCI commands in the same way that SQL*Plus executes scripts of SQL and PL/SQL commands.
ADR data is secured by operating system permissions on the ADR directories, hence there is no need to log in to ADRCI.
create report <report_type> <report_id>
SELECT run_id, name, check_name, run_mode, status, error_number
adrci> set homepath diag\rdbms\orabase\orabase
adrci> create report hm_run HM_RUN_1
adrci> show report hm_run hm_run_1
echo <ON | OFF>
ardci> echo on
ardci> echo off
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
adrci> spool /home/oracle/adr.log
adrci> show alert -term
adrci> spool off
ADR Metadata Folder
The ADR Metadata folder contains, right now, 44 files that are external tables queryable via adrci using SQL: External tables that are not visible in CDB_OBJECTS_AE.
Start by making a list of the current metadata file names and then try these examples using your file names if they differ from mine.
adrci> show homes
adrci> set home diag\rdbms\orabase2\orabase2
adrci> desc dfw_config_item
adrci> desc incident
-- the statement must be written on one line as I have done here ... you can not hit enter and continue on a new line
adrci> SELECT create_time, status, suspect_component, impact FROM incident;
adrci> CREATE VIEW adr_test_view AS SELECT problem_id, impact1 FROM problem;
adrci> desc adr_test_view
adrci> SELECT * FROM adr_test_view;
SQL> conn / as sysdba
-- the view does not exist as a database object
SQL> SELECT owner, object_type, last_ddl_time
WHERE object_name = 'ADR_TEST_VIEW';
adrci> DROP VIEW adr_test_view;
-- the view definition is stored in view.ams and viewcol.ams
SQL> conn / as sysdba
SQL> desc gv$hm_run
SQL> SELECT run_id, name, check_name, run_mode, status, error_number