ORA-16623: stale DRC UID sequence number detected
- 1 Answers
- 3977 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The Data Guard broker detected a stale sequence value
during its bootstrap or health check operations. The
sequence value is changed each time a role change occurs. A
database that is unavailable to participate in the role
change operation will end up with a stale sequence number.
Should the broker for that database attempt to re-join the
broker configuration, the broker will determine that it
missed a role change and will disable its management of that
database. The broker permanently disables the database since
it may no longer be a viable standby for the new primary.
Action: Examine the broker configuration for databases that
were permanently disabled and which may require reinstantiation.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-00312: online log string thread string: 'string'
ORA-27126: unable to lock shared memory segment in core
ORA-00229: operation disallowed: already hold snapshot controlfile enqueue
ORA-28510: heterogeneous database link initialization failed
ORA-00260: cannot find online log sequence string for thread string
PCC-02431: Expecting an expression of type external LOB (BFILE)
ORA-23348: cannot replicate procedure string; only IN parameters supported
ORA-19652: cannot apply offline-range record to datafile string: file is fuzzy
ORA-29903: error in executing ODCIIndexFetch() routine
PCC-00087: EXEC SQL TYPE statement not allowed for this host language
PCC-02447: Cannot specify destination offset in a LOB WRITE APPEND
ORA-02216: tablespace name expected
Oracle Errors 
