Master Note for Diagnosibility

Guest Author

Master Note for Diagnosibility (Oracle Database)

This Master 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 Master 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.

Getting started

<<Note 1292665.1>> - Oracle Database Support Newsletter - February, 2011


1. Package types

Packages can be categorized as following:

Description base type DB version  file format upload target
standard OS package



tar, gz, zip

RDA (Remote Diagnostic Agent)




ADR Repository
IPS (11g Incident Packaging Service)


and higher


ADR Repository
IPS + RDA (bundle)

and higher


ADR Repository
OCM (Oracle Configuration Manager)


and higher


Configuration repository
OCM + RDA (bundle)


and higher


Configuration Repository &
ADR Repository

2. Incident Packaging Services (IPS)  

There are 2 options to create IPS packages:

2.1 Commandline Interface (ADRCI)

For IPS package creation in general and use of command line utility (ADRCI) refer to:

<<Note 443529.1>> - 11g Quick Steps to Package and Send Critical Error Diagnostic Information to Support [Video]

2.2. GUI (SWB)

For use of Support Workbench - the graphical user interface refer to:

<<Note 1091653.1>> - 11g Quick Steps - How to create an IPS package using Support Workbench [Video]

Upload Diagnostic Data

Diagnostic files and packages can be uploaded to ORACLE using My ORACLE Support (MOS) the graphical customer user interface. This requires a Service Request (SR). The upload should not be interrupted or stopped. Once completed you will receive a completion message and SR becomes automatically updated with different upload status details. These messages can be used by support or customers to check upload status.

Verify Uploads in MOS

In order to examine upload messages, open your SR in MOS and verify following settings:

set [Filter By] to <-- Show all Entries -->
uncheck [Hide System Messages] checkbox

Package Processing - Step 1 (virus scan)

Each incoming package or file will be processed by virus scan first. After completion you will see a message like:

Virus Scan successfully completed for RDA.RDA_dwhprod.zip.
If you see this message, this will indicate that your file was successfully uploaded and received by ORACLE.

Package Processing - Step 2 (package specific actions)

After Virus Scan package and file processing depends on package type. Different types have different processing. The following will summarize processing of base package types. Package bundles will be splited into base components and processed accordingly.

a) Standalone RDA packages will be moved and extracted to Global ADR Repository. Completion tag:

Auto generated message by RDA FUP :RDA.RDA_BBDD1.zip has been uploaded to the ADR Repository.

b) Standalone IPS packages will be moved to Global ADR Repository, extracted and processed by ADRCI. Completion tag:

Diagnostic file ORA600_20100526101903_COM_1.zip was successfully processed at Oracle by 11g Diagnostics

c) Configurations will be moved to Configuration Repository. Completion tag:

 Auto generated message by RDA-OCM FUP :ocmconfig.jar has been uploaded to Configuration repository.

d) Anything else - different from RDA, IPS or configurations - goes to Global Testcase Repository (GTCR)

Health Monitor

<<Note 466920.1>> - 11g New Feature: Health monitor
<<Note 951022.1 >> - How To Purge or Delete Health Monitor Checks After DBMS_HM.RUN_CHECK ?

Diagnostic Internals

<<Note 422893.1>> - 11g Understanding Automatic Diagnostic Repository
<<Note 750982.1>> - TRM Trace Files Getting Generated in 11g Database


<<Note: Note 453125.1>> - 11g Diagnosability Frequently Asked Questions


ADR - Purging and Retension

<<Note 564269.1>> - Retention Policy for ADR
<<Note 751082.1>> - Adrci Purge Does Not Clear the Text-formatted Alert.Log located in the Trace Folder

Tips and Tricks

1. How to create an incident for testing?
Attention: Don't use this in production systems !

<<Note 390293.1>> - Introduction to 600/7445 Internal Error Analysis

Diagnostic Tools

<<Note 559339.1>> - Diagnostic Tools Catalog
<<Note 153788.1>>  - ORA-600/ORA-7445 Error Look-up Tool

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.