Problem Diagnosis - Expert Oracle RAC Performance Diagnostics and Tuning - page 612

Problem Key
Every problem identified and created by the ADR has a problem key. The problem key is a text string that includes an
error code (such as ORA 600 ) and in some cases, one or more error parameters. Whereas PROBLEM IDs are unique to
the database, problem keys are not. There could be many occurrences of the similar problem and they may have the
same problem key.
V$DIAG_PROBLEM
This view lists all the problem keys associated with incidents for a database instance. Please note the incident
count column for PROBLEM_ID=4 . The incident count is 11, indicating that there are several incidents of the exact
same error and Oracle creates one problem entry that relates back to all 11 incidents created. The problem key
(for example, PROBLEM_ID=9 ) is a text string that includes an error code (such as ORA 600 ) and in some cases, one
or more error parameters:
Script Name:MVRACPDnTap_adrproblemlist.sql
Inc
P-id PROBLEM_KEY Cnt
----- ------------------------------------------------------------ ----
1 ORA 600 [kjbmprlst:shadow] 1
2 ORA 600 [rwoirw: check ret val] 2
3 ORA 600 [kksfbc-wrong-kkscsflgs] 1
4 ORA 600 [4193] 11
5 ORA 1578 2
6 ORA 600 [kewrose_1] 1
7 ORA 600 [2023] 4
8 ORA 600 [4136] 4
9 ORA 600 [ORA-00600: internal error code, arguments: [2023], 4
[0], [0], [], [], [], [], [], [], [], [], []
10 ORA 600 [kcratr_scan_lastbwr] 1
Incident Package
All incidents that are critical in nature have to be reported to Oracle support for resolution. Before sending incident
data to Oracle Support, it must be collected into a package using the Incident Packaging Service (IPS).
When an incident occurs, the database server makes an entry in the alert log, gathers diagnostic data about the
incident, tags the diagnostic data with the incident ID, and stores the data in an ADR subdirectory created for that
incident. As mentioned previously, each incident has a problem key and is mapped to a single problem. Incidents that
have the same problem keys have the same root cause or identical PROBLEM_KEY .
In certain cases, there could be a large number of errors being generated (when a specific feature causing the
problem is repeatedly being used). This could indicate a large number of incidents that belong to the same root cause
and could cause flooding of the ADR. To avoid this, Oracle controls the number of dumps that could be generated for
a given problem to five.