Standby Database Got ORA-03170: Deadlocked; Pmon Not Able To Clean Up
(Doc ID 2134423.1)
Last updated on JANUARY 07, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The following errors reported on Active Data Guard physical standby over and over:
Errors in file /u01/oracle/diag/rdbms/<DB_NAME>/<INSTANCE_NAME>/trace/<INSTANCE_NAME>_pmon_41746880.trc:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)
And the pmon trace contains call stack: krdwtadv()<-ktuGetUsegDba()<-ktugin_cr()
NOTE! in some cases eg when converting to snapshot standby, dg broker might give a message of ORA-03170 in alert log, but it could be resolved automatically by dg broker and the error can be ignored in that case and not be applicable to this case.
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 |
| Cause |
| Solution |
| References |