Fault diagnosability Infrastructure Overview

Fault diagnosability Infrastructure Overview

The fault diagnosability infrastructure aids in preventing, detecting, diagnosing, and resolving problems. The problems that is targeted in particular is critical errors such as those caused by code bugs, metadata corruption, a ND customer data corruption. When a critical error occurs, it's assigned an incident number, and diagnostic data for the error (such as trace file s) is immediately captured and tagged with this number. The data is then stored in the Automatic Diagnostic Repository (ADR)--a file-based Repository outside the Database--where It can later is retrieved by incident number and analyzed.

About Incidents and problems

a problem are a critical error in a database instance, Oracle Automatic Storage Management (Oracle ASM) INS Tance, 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 Syst EM exception) or ORA-04031 (out of memory in the shared pool). Problems is tracked in the ADR. Each problem have a problem key, which is a text string that describes the problem. It includes an error code (such as ORA) and in some cases, one or more error parameters. An incident are a single occurrence of a problem. When a problem (critical error) Occurs multiple times, an incident are created for each occurrence. Incidents is timestamped and tracked in the Automatic Diagnostic Repository (ADR). Each incident are identified by a numeric incident ID and which is unique within the ADR.

When an incident occurs, the database makes a 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 the dump files (incident dumps).
Tags the incident dumps with the incident ID.
Stores the incident dumps in a ADR subdirectory created for that incident.

Fault diagnosability Infrastructure Overview