This Master Note is intended to provide a summary, index and references on topics around diagnosibility.
- 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.
<<Note 1292665.1>> - Oracle Database Support Newsletter - February, 2011
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)|| |
|IPS (11g Incident Packaging Service)|| |
|IPS + RDA (bundle)|| |
|OCM (Oracle Configuration Manager)|| |
|OCM + RDA (bundle)|| |
|Configuration Repository & |
There are 2 options to create IPS packages:
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]
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]
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.
In order to examine upload messages, open your SR in MOS and verify following settings:
Each incoming package or file will be processed by virus scan first. After completion you will see a message like:
After Virus Scan package and file processing depen
ds 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)
<<Note 466920.1>> - 11g New Feature: Health monitor
<<Note 951022.1 >> - How To Purge or Delete Health Monitor Checks After DBMS_HM.RUN_CHECK ?
<<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
<<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
<<Note 975448.1>> - WHICH FILES ARE PART OF SHORTP_POLICY AND LONGP_POLICY IN ADR?
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