This content has been marked as final. Show 3 replies
When the DIAG_ADR_ENABLED parameter is set to OFF, non-ADR file tracing is used.
1- If you don’t find Oracle Net flies in the directories where you expect those just set DIAG_ADR_ENABLED=OFF parameter in the relative sqlnet.ora file.
Oracle will create the trace files depending on type Client/Server in the following directories:
Client – OS Home dir/oradiag_os username/diag/clients/user_oradb/host_number/trace/
RDBMS – ORACLE_BASE/diag/rdbms/db_name/instance_name/trace/
2.Controlling ADR Creation and Disabling Fault Diagnosability Using sqlnet.ora
When I saw this link then here bit confusion regarding DIAG_ADR_ENABLED=FALSE or DIAG_ADR_ENABLED=off.
Anyway, but I think there should not be any impact my database. They are just trace, dump files which an incident (an occurrence of a problem) on the OCI client is captured without user intervention in the form of diagnostic data: dump files or core dump files.
Thanks for your answers:
Does setting these parameters to false changes the directory structure of my trace files? If yes: that is mean it changes the directory structure only on the client side? or as well as the database server side? (I did not modify sqlnet.ora on the server side)
Edited by: NB on Nov 17, 2012 5:05 PM
Does setting these parameters to false changes the directory structure of my trace files?No, I don't think that setting these parameter to false may change the directory structure, because Automatic Diagnostic Repository (ADR) is a directory structure that is stored outside of the database. Setting these parameter to false just stops to create trace and dump files which are required to send the Oracle support. When the DIAG_ADR_ENABLED parameter is set to OFF, non-ADR file tracing is used.
See Structure, Contents, and Location of the Automatic Diagnostic Repository :