Oracle Keep Writing To Old Diag_dest After Changing Diagnostic_dest Parameter in 11g
(Doc ID 1476463.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 25-Dec-2016***
Changing of diagnostic_dest has no effect on some background processes like diag/diag0. The files get written to both old and new location.
Changed the diagnostic_dest parameter to different location with scope=both and sid='*'
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document