Path of the trace file under the ADR Management in 11g

Path of the trace file under the ADR Management in 11g

A 11G development library, intends to open the trace of sqlplus, check the connection information of sqlplus login, but configure sqlnet. ora did not find the trace file, and one day it was found that the disk space was insufficient. After the query, it was found that there were thousands of files in the following path, occupying G space:

/u01/app/oracle/11.2.0.4/diag/clients/user_oracle/host_1347578259_80/trace

What are these files? Open one and you will find that it is listening for sqlpuls login information, that is, the trace file:

So why is this trace file in this path?

@ Yong Huang reminded me that this problem was related to the 11g ADR settings. below is the official introduction of ADR:

The Automatic Diagnostic Repository (ADR) is a file-based repository for database
diagnostic data such as traces, dumps, the alert log, health monitor reports, and more.
It has a unified directory structure across multiple instances and multiple products.
Beginning with release 11g, the database, Oracle Automatic Storage Management (Oracle
ASM), and other Oracle products or components store all diagnostic data in the ADR. Each
instance of each product stores diagnostic data underneath its own ADR home directory
(see “ADR Home”). For example, in an Oracle Real Application Clusters (Oracle RAC)
environment with shared storage and Oracle ASM, each database instance and each Oracle
ASM instance has a home directory within the ADR. The ADR’s unified directory structure
enables customers and Oracle Support to correlate and analyze diagnostic data across
multiple instances and multiple products.

The Automatic Diagnostic database (ADR) is a file-based database diagnostic data storage database that stores trace, dump, alert log, health monitoring reports, and so on. There is a unified directory structure for multiple instances and products. Starting from 11g, diagnostic data for Oracle ASM and other Oracle products or components will be stored in ADR. Each product instance stores diagnostic data under its own ADR root directory. The unified directory structure of ADR allows customers and Oracle to associate diagnostic data of different instances and products for analysis.

This article on MOS explains how to store trace files after sqlnet. ora Configuration:

NET Client Traces Generated In $ ADR_BASE/oradiag _/diag/clients/Directory (Document ID 1545533.1)

If you configure

ADR_BASE=ADR base location

The trace file is automatically stored in the following path:

$ADR_BASE/oradiag_OS user/diag/clients/..

Otherwise it will be stored in:

$ADR_BASE/diag/clients/...

Lab:
1. database version


2. Configure sqlnet. ora to open the client trace


3. I didn't configure ADR_BASE here, just in listener. Z listener? Http://www.bkjia.com/kf/ware/vc/ "target =" _ blank "class =" keylink "> vcmhw0mxk1spby0feul9cqvnfx0xju1rftkvsidxicj4kpgltzybzcm9" http://www.2cto.com/uploadfile/Collfiles/20151214/201512140955137.png "alt =" here write picture description "title =" \ ">

4. Execute an incorrect connection to generate a trace file.


5. Because ADR_BASE is not set, there should be no oradiag_OSuser path, but there will be a diag path.
System. We recommend that you enable it when using it. You need to disable it immediately after use.