OCP 1Z0 053 122

122.Which statements are true regarding the concept of problems and incidents in the fault diagnosability 
infrastructure for Oracle Database 11g? (Choose all that apply.) 
A. Only the incident metadata and dumps are stored in the Automatic Diagnostic Repository (ADR). 
B. The problem key is the same as the incident number. 
C. The database sends an incident alert to the Oracle Enterprise Manager Database Home page. 
D. Every problem has a problem key, which is a text string that describes the problem. 
E. The database makes an entry into the alert log file when problems and incidents occur. 
Answer: CDE 

Automatic Diagnostic Repository (ADR)

The ADR is a file-based repository for database diagnostic data such as traces, dumps, the alert log, health monitor reports, and more. It has a unified directory structure across multiple instances and multiple products. Beginning with Release 11g, the database, Oracle Automatic Storage Management (Oracle ASM), the listener, and other Oracle products or components store all diagnostic data in the ADR. Each instance of each product stores diagnostic data underneath its own home directory within the ADR. For example, in an Oracle Real Application Clusters environment with shared storage and Oracle ASM, each database instance and each Oracle ASM instance has an ADR home directory. ADR's unified directory structure, consistent diagnostic data formats across products and instances, and a unified set of tools enable customers and Oracle Support to correlate and analyze diagnostic data across multiple instances.

Note:

Beginning with Release 11 g of Oracle Database, because all diagnostic data, including the alert log, are stored in the ADR, the initialization parameters  BACKGROUND_DUMP_DEST and  USER_DUMP_DEST are deprecated. They are replaced by the initialization parameter  DIAGNOSTIC_DEST, which identifies the location of the ADR.

About Incidents and Problems

To facilitate diagnosis and resolution of critical errors, the fault diagnosability infrastructure introduces two concepts for Oracle Database: problems and incidents.

A problem is a critical error in a database instance, Oracle Automatic Storage Management (Oracle ASM) instance, or other Oracle product or component. Critical errors manifest as internal errors, such as ORA-00600, or other severe errors, such as ORA-07445 (operating system exception) or ORA-04031 (out of memory in the shared pool). Problems are tracked in the ADR. Each problem has a problem key, which is a text string that describes the problem. It includes an error code (such as ORA 600) and in some cases, one or more error parameters.

An incident is a single occurrence of a problem. When a problem (critical error) occurs multiple times, an incident is created for each occurrence. Incidents are timestamped and tracked in the Automatic Diagnostic Repository (ADR). Each incident is identified by a numeric incident ID, which is unique within the ADR. When an incident occurs, the database:

• Makes an entry in the alert log.

• Sends an incident alert to Oracle Enterprise Manager (Enterprise Manager).

• Gathers first-failure diagnostic data about the incident in the form of dump files (incident dumps).

• Tags the incident dumps with the incident ID.

• Stores the incident dumps in an ADR subdirectory created for that incident.

Diagnosis and resolution of a critical error usually starts with an incident alert. Incident alerts are displayed on the Enterprise Manager Database Home page or Oracle Automatic Storage Management Home page. The Database Home page also displays in its Related Alerts section any critical alerts in the Oracle ASM instance or other Oracle products or components. After viewing an alert, you can then view the problem and its associated incidents with Enterprise Manager or with the ADRCI command-line utility.