Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16623: stale DRC UID sequence number detected
- 1 Answers
- 4549 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 |
PLW-07203: parameter 'string' may benefit from use of the NOCOPY compiler hint
NCR-01008: NCRS: Failed to obtain transport parameters.
UDI-00051: unable to set NLS_NUMERIC_CHARACTERS to required defaults.
ORA-01478: array bind may not include any LONG columns
LFI-00120: Unable to parse root filename string.
NZE-29152: SHA-1 self-test failure
ORA-29257: host string unknown
ORA-14167: only one subpartition may be moved
ORA-16710: The resource guard is out of memory.
ORA-35280: (SNSYN165) The format of the AGGREGATE command is: AGGREGATE varname1 [varname2 varname3 ...] USING aggmap-name [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [THREADS #]
ORA-01666: controlfile is for a standby database
ORA-36612: (XSLMS01) An application attempted to retrieve a non-existent user message. (Product: value, Facility: value, Message Number: value)
Oracle Errors 
