Changes in dump, trace, and log files of Oracle 11gR2 Databases

The log system of the Oracle 1gR2 database changes a lot. The following describes the changes in the parameter file and adr.
1. parameter file
After converting the spfile to pfile, we can see that the original bdump, adump, cdump, and udump settings only have the following settings:
Audit_file_dest = 'e: \ app \ admin \ orcl \ adump'

The show parameter dump command shows the location of other directories. This parameter must be set to store tracking files when AUDIT_TRAIL is set to OS, xml, or xml or extended. If this parameter is not set, the system cannot log on normally.
 
SQL> show parameter dump
NAME TYPE VALUE
-----------------------------------------------------------------------------
Background_core_dump string partial
Background_dump_dest string d: \ app \ diag \ rdbms \ orcl \ tr
Ace
Core_dump_dest string d: \ app \ diag \ rdbms \ orcl \ cd
Ump
Max_dump_file_size string unlimited
Shadow_core_dump string none
User_dump_dest string d: \ app \ diag \ rdbms \ orcl \ tr
Ace
The locations of bdump, cdump, and udump depend on the settings of the diagnostic_dest parameter and do not need to be set separately.
SQL> show parameter diag
NAME TYPE VALUE
--------------------------------------------------------------
Diagnostic_dest string d: \ app

This is the Automatic diagnosis database of adr (Automatic Diagnostic Repository) in 11G. Of course, the Automatic diagnosis database has an automation aspect. This aspect is not discussed in this article.

2. Automatic ADR diagnosis Database

 
It is the standard structure of ADR. Oracle database-related products and components comply with this standard structure. common structures include databases, listeners, clients, and ASM. As the log system is standardized, therefore, with the unified tool ADRCI, you can easily manage and view logs of all components.

The root node of ADR is the adr base. In actual work, we found that there can be multiple ADR bases. If you have installed the Grid Infrastructure product, the Grid and Database have their own adr base, but the set base command in the adrci tool can easily switch the adr base of the two products.

In addition to the product, different components of the same product can also be located in different ADR bases and configured separately for each component. For example, the original value of the database diagnostic_dest parameter is e: \ app. You can change this parameter to d: \ app dynamically, then the log files of the corresponding database are immediately stored in the corresponding directory structure of d: \ app.
 
E: \> adrci
ADRCI: Release 11.2.0.3.0-Production on Sunday August 19 11:52:20 2012
Copyright (c) 1982,201 1, Oracle and/or its affiliates. All rights reserved.
ADR base = "d: \ app" // The default ADRBASE is displayed after successful logon.
Adrci> show home // display the existing components under the current BASE (each component has a HOME)
ADR Homes:
Diag \ rdbms \ orcl // The database initialization parameter diagnostic_dest is dynamically modified. Other components, such as listeners, are not switched together.
Adrci> set base e: \ app // switch the ADR BASE
Adrci> show home // display the components in this adr base. You can view the listening logs.
ADR Homes:
Diag \ clients \ user_LIUBINGLIN \ host_56731_31_80
Diag \ rdbms \ orcl
Diag \ tnserver SNR \ LIUBINGLIN-PC \ listener

From the above example, we can see that the switching of the listening adr base is not associated with the database initialization parameter diagnostic_dest. Open the listener. ora configuration file and you can find the setting parameters of the adr:
ADR_BASE_LISTENER = e: \ app

You can modify ADR_BASE_LISTENER In the Listener Configuration File to adjust the listening component's adr base. After the adjustment, restart the listener to make the changes take effect.
-- End --