Oracle Keep Writing To Old Diag_dest After Changing Diagnostic_dest Parameter in 11g
(Doc ID 1476463.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.3 [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.
Symptoms
In 11g,
Changing of diagnostic_dest has no effect on some background processes like diag/diag0. The files get written to both old and new location.
Changes
Changed the diagnostic_dest parameter to different location with scope=both and sid='*'
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |