Oracle Automated Diagnostic Data Archive (ADR), Automated diagnostics workflow, Adrci Tools

1. Automated Diagnostics Workflow:

With an in-memory tracing tool that is always turned on, the database component can capture diagnostic data the first time a critical error failure occurs. A special repository, called an automated diagnostic repository, is automatically maintained to hold diagnostic information about critical error events. This information can be used to create an unexpected event package to be sent to Oracle support services for investigation.

The following is a typical diagnostic session workflow:
1) Unexpected events cause an alert in Oracle Enterprise Manager (EM).

2) The DBA can view this alert through the alert (alert) page of EM.

3) DBAs can refine the details to unexpected events and issues.

4) The DBA may decide or Oracle Support Services can request that the information be packaged and sent to Oracle Support services via MetaLink. The DBA can add files to the automatically packaged data.

2. Automatic Diagnostic Data Archive (ADR)

ADR is a file-based repository for database diagnostic data (such as tracking, accidental event dumps and packages, alert logs, health monitoring reports, core dumps, and so on). It uses a unified directory structure for multiple instances and multiple products stored outside of any database. Therefore, you can use it to diagnose problems when the database is closed.

Starting with Oracle database 11g R1, databases, automated storage management (ASM), Cluster readiness Services (CRS), and other Oracle products or components store all diagnostic data in ADR. Each instance of each product stores diagnostic data in its own ADR home directory. For example, in a Real application Clusters environment with shared storage and ASM, each DB instance and each ASM instance has a home directory in the ADR.

With a unified directory structure for ADR, a unified diagnostic data format for a variety of products and instances, and a unified set of tools, customer and Oracle technical support can correlate and analyze diagnostic data for multiple instances.

The ADR root is also known as the ADR base directory, and its location is set by the Diagnostic_dest initialization parameter. If this parameter is ignored or left blank, the database will be set at startup with the following settings: If the environment variable oracle_base is set, the Diagnostic_dest is set to $ORACLE _base. Diagnostic_dest. If the environment variable oracle_base is not set, the Diagnostic_dest is set to $ORACLE _home/log.

3.ADR Command line tool Adrci

Adrci is a command-line tool that is part of the database troubleshooting infrastructure.

Adrci can interact with the ADR through the operating system prompt.

Use Adrci to view diagnostic data in an automated diagnostic repository.

Use Adrci to:
--View diagnostic data in the Automated Diagnostic Data Archive (ADR)
--Package unexpected events and problem information into a ZIP file transfer to Oracle technical support

The Adrci has a rich set of commands that can be used in interactive mode or in scripts. In addition, Adrci can also execute adrci command scripts in the same way that Sql*plus executes SQL scripts and PL/SQL commands.

$ adrci

Adrci:release 11.1.0.5.0-on Sat 7 08:01:40 2007

Copyright (c) 1982, Oracle. All rights reserved.

ADR base = "/u01/app/oracle"

Adrci> Show incident

ADR Home =/U01/APP/ORACLE/PRODUCT/11.1.0/DB_1/LOG/DIAG/RDBMS/ORCL/ORCL:

**************************************************************************
incident_id Problem_key Create_time

----------- ------------------------------------ ------------------------

1681 ora-600_dbgris01:1,_addr=0xa9876541 17-jan-07 09.17.44.843125 ...

1682 ora-600_dbgris01:12,_addr=0xa9876542 18-jan-07 09.18.59.434775 ...

2 incident Info Records fetched

4.v$diag_info View

Sql> SELECT * from V$diag_info;

NAME VALUE
-------------------   -------------------------------------------------
Diag Enabled TRUE

ADR base/u01/app/oracle

ADR HOME/U01/APP/ORACLE/DIAG/RDBMS/ORCL/ORCL

Diag Trace/u01/app/oracle/diag/rdbms/orcl/orcl/trace

Diag Alert/u01/app/oracle/diag/rdbms/orcl/orcl/alert

Diag incident/u01/app/oracle/diag/rdbms/orcl/orcl/incident

Diag Cdump/u01/app/oracle/diag/rdbms/orcl/orcl/cdump

Health MONITOR/U01/APP/ORACLE/DIAG/RDBMS/ORCL/ORCL/HM

Default Trace FILE/U01/APP/ORACLE/DIAG/.../TRACE/ORCL_ORA_11424.TRC

Active Problem Count 3

Active Incident Count 8

The V$diag_info view lists the locations of all important ADR:

The path to the ADR base:adr base directory.

ADR home: The path to the ADR home directory for the current DB instance.

Diag Trace: The location of text alert logs and background/foreground process trace files.

Diag the location of the Alert:xml version of the alert log.
Diag Incident: The write location of the unexpected event log.

Diag Cdump: Writes the diagnostic core file in this directory.

Health Monitor: The location of the logs that are generated when you run healthy monitoring.

Default trace File: The path to the trace files for the session. The SQL trace file is written to this location.

Location of diagnostic traces for 5.Oracle 10g and Oracle 11g

Previous location of diagnostic data ADR location
Foreground process Trace User_dump_dest Adr_home/trace
Background process Trace Background_dump_dest Adr_home/trace
Alert log data background_dump_dest Adr_home/alert adr_home/trace
Core Dump Core_dump_dest Adr_home/cdump
Accidental Dump user| Background_dump_dest Adr_home/incident/incdir_n

Oracle Automated Diagnostics Data Archive (ADR), Automated diagnostics workflow, Adrci tools