ORA-16170: Terminal recovery may have left the database in
an inconsistent state
Answer / guest
Cause: When terminal recovery is invoked in a standby
database without synchronous log shipping, in the rare case
of the recovery session being in an unrecoverable state,
terminal recovery cannot bring the standby database to a
consistent SCN boundary if the primary database continues to
have redo thread(s) open.
Action: Continue standby recovery with additional log
shipping from primary.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
SQL-02119: Invalid HSTDEF argument
ORA-01654: unable to extend index string.string by string in tablespace string
NID-00508: HELP Displays these messages NO
ORA-36995: (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.
ORA-01084: invalid argument in OCI call
PCB-00633: Invalid host variable and attribute pairing
ORA-03240: User's temporary tablespace same as tablespace being migrated
ORA-25103: NOPARALLEL option can only be used with ALTER INDEX REBUILD
PCB-00501: Runtime context variable "string" not of correct type
ORA-19706: invalid SCN
ORA-13017: unrecognized line partition shape
ORA-12566: TNS:protocol error