ORA-16623: stale DRC UID sequence number detected
- 1 Answers
- 4099 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-19204: Non-scalar value 'string' is marked as XML attribute
ORA-27044: unable to write the header block of file
ORA-16131: An error occurred during a Terminal Recovery of the standby.
RMAN-10023: RPC attempted to unrecognized package
PCC-02390: No EXEC SQL CONTEXT USE statement encountered
ORA-01639: instance string has no thread assigned to it
NNO-00629: warning: invalid forwarder list, no default forwarders loaded
TNS-00545: parameter retrieval failure
SQL*Loader-00267: Control file must be first data file.
ORA-25299: Cannot add buffered subscriber for a non-buffered queue
ORA-30161: A system error occurred during the OCIFile function call
ORA-31457: maximum length of description field exceeded
Oracle Errors 
