Primary Note for Diagnosibility (Oracle Database)
(Doc ID 1323828.1)
Last updated on SEPTEMBER 11, 2023
Oracle Database - Standard Edition Oracle Database - Personal Edition Oracle Database - Enterprise Edition Oracle Database Cloud Schema Service - Version N/A and later Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later Information in this document applies to any platform.
all Oracle Databases
This Primary Note is intended to provide a summary, index and references on topics around diagnosibility. This includes: - What is diagnosibility ? - What's new with the 11g diagnosibility concept? - How to gather diagnostic data for different releases? - How to upload diagnostic files to Oracle support? - How to verify uploads? - Known Problems
This Primary Note is subdivided into categories to allow for easy access and reference to notes that are applicable to your area of interest, within diagnosibility.
What is Diagnosibilty?
Actually diagnosibility has different meanings: Fault diagnosibility captures diagnostic data, such as dump files or core dump files, on the OCCI client when a problem occurs.
In pre 11g databases diagnosibilty based on single files like alert.log and process tracefiles.
With 11g 'Diagnosibility' was introduced as a feature that simplifies collecting the diagnostic information and sending this infornation to support. Diagnosibilty covers the whole process from data collection, package creation, package upload to ORACLE and package investigation at ORACLE support. The overall view is called Diagnosibilty Framework (DFW) RDBMS diagnostic data has been reorganized and are stored in a common directory structure named ADR (Automatic Directory Repository) ADR contains different diagnostic files of xml format in a database-like structure.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!