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

Figure 18-3. OEM run DB structure integrity check

Certain types of checks may require additional parameters. For example, as illustrated in Figure 18-4 , the
CF Block Integrity Check requires an additional parameter.

Figure 18-4. OEM CF block integrity check

The list of parameters required for the various check operations can be obtained from V$HM_CHECK_PARM.

5. Once the parameters have been entered, click Run, which confirms the parameter, and

then click Run again.

6. Once the check is complete, the report can be viewed: select View Report for the health

checks report.

Automatic Diagnostic Repository
In Oracle Database Release 9i, Oracle had introduced a new background process called DIAG for the RAC
environment. The function of the DIAG background process is to collect memory statistics when process state changes
happened within the Oracle memory structures or other RAC-related background processes. The DIAG process
collected trace into separate directories every time a state change occurred; however, the data saved in these files
could not be read by the DBAs. The output in these directories was only useful to Oracle support. When database
errors such as ORA-0600 occurred of the instance crashed, these directories along with other trace files were uploaded
to the support site for a service request.
In Oracle Database 11g Release 1, besides making the DIAG process available on both a single instance and
a RAC database, Oracle has enhanced the entire diagnostic process by storing all information for tracking and
analysis in a repository called Automatic Diagnostic Repository (ADR). The ADR contains all trace, dump, and other
information related to any incident or error encountered by the instance.