During the analysis of the Orachk report on one of the Oracle 12c environments, I had found out that there are logs being written to the $ORACLE_HOME/rdbms/log directory.

Let’s check how the USER_DUMP_DEST is set in my specific database:

SQL> show parameter user_dum 
user_dump_dest string /u01/app/oracle/product/12.1.0/dbhome_1/rdbms/log 


But the Oracle 12.1 documentation states
“The USER_DUMP_DEST initialization parameter is deprecated. This parameter is ignored by the diagnosability infrastructure introduced in Oracle Database 11g Release 1 (11.1), which places trace and core files in a location controlled by the DIAGNOSTIC_DEST initialization parameter.”

As I understand Diagnosibility infrastructure should use diagnostic_dest parameter. My diagnostic destination is as follows:

SQL> show parameter diagn 

diagnostic_dest string /u01/app/oracle 

There were some bugs registered for this issue (BUG 17991901, BUG 20511952) but they were eventually closed. Oracle concluded that some traces are written before the Diagnosability Framework has been initialized, and before the value of DIAGNOSTIC_DEST has been checked, they still have to go somewhere, and that’s the default location.

Don’t be surprised if you are getting some traces into the $ORACLE_HOME/rdbms/log directory instead of DIAGNOSTIC_DEST/diag/rdbms/$dbname/$SID/traces.

This is feature, not a bug :)

About the author

maciej tokar
Maciej Tokar

An Oracle technology geek and crazy long distance runner, DBA24 Owner
Senior Oracle DBA / Consultant / [OCP10g, OCP12c, OCE RAC 10g] / [experience: 9y+]
Currently working for Bluegarden (Oslo Norway) by Miratech Group
Past: Mastercard / Trevica by Britenet, Citi International PLC, PZU

View Maciej Tokar's profile on LinkedIn         logoDB4
LinkedIn Auto Publish Powered By :