Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16170: Terminal recovery may have left the database in
an inconsistent state
- 1 Answers
- 3064 Views
- I also Faced
- E-Mail Answers
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 |
ORA-12913: Cannot create dictionary managed tablespace
ORA-27479: Cannot string "string.string" because other objects depend on it
ORA-14631: the partition bounds do not match the subpartition bounds of the partition
Recent I have migrated oracle9i to oracle10g(10.2.0.3). I have nested table that table used user define datatype. at a column. when i want to input the valoue at this column ,i cann't the input value.following the error messasge i have got: ORA-24328 illegal attribute value
ORA-02036: too many variables to describe with automatic cursor open
PCC-00027: Redeclared SQL Identifier "string" at line number in file string
ORA-32404: snapshot log uses Change Data Capture which is not enabled for this database
ORA-13374: SDO_MBR not supported for geodetic data
ORA-00701: object necessary for warmstarting database cannot be altered
PROT-00012: Oracle Cluster Registry to be upgraded has an unsupported version
NNO-00054: invalid domain name "string"
DRG-50943: query token too long on line string on column string
Oracle Errors 
