ORA-16170: Terminal recovery may have left the database in
an inconsistent state
- 1 Answers
- 2299 Views
- I also Faced
- E-Mail Answers
Answer Posted / 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 |
Post New Answer View All Answers
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-26079: file "string" is not part of table string.string
ORA-26028: index string.string initially in unusable state
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
IMP-00070: Lob definitions in dump file are inconsistent with database.
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
ORA-26094: stream format error: input column overflow
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
ORA-26032: index string.string loading aborted after string keys
ORA-26030: index string.string had string partitions made unusable due to:
ORA-16627: No standby databases support the overall protection mode.
ORA-16626: failed to enable specified object
ORA-26082: load of overlapping segments on table string.string is not allowed
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
NZE-28868: Peer certificate chain check failed.
