Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16623: stale DRC UID sequence number detected
- 1 Answers
- 4387 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 |
RMAN-00579: SCRIPT cannot be used with CMDFILE
NID-00420: Change of database name and ID failed during validation - database is intact.
ORA-27210: syntax error in device PARMS
ORA-24146: rule string.string already exists
SQL*Loader-00259: Could not escalate DDL share lock to exclusive on table string
TNS-00070: INTCTL usage: [intctl] <command> <process_name> [argument]
SQL*Loader-00279: Only APPEND mode allowed when parallel load specified.
ORA-27006: sbtremove returned error
ORA-13860: Invalid service name
ORA-01900: LOGFILE keyword expected
TNS-12651: Encryption or data integrity algorithm unacceptable
PLS-00135: Pragma string expects 3rd argument to be an identifier, string or numeric literal
Oracle Errors 
