ORA-12824: INSTANCES DEFAULT may not be specified here
- 1 Answers
- 2300 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: INSTANCES DEFAULT was specified in the PARALLEL
clause of an ALTER DATABASE RECOVER command
Action: respecify with an explicit value for INSTANCES or
omit the INSTANCES option if single instance recovery is
desired.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-26028: index string.string initially in unusable state
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-26030: index string.string had string partitions made unusable due to:
ORA-16626: failed to enable specified object
IMP-00070: Lob definitions in dump file are inconsistent with database.
if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?
ORA-26027: unique index string.string partition string initially in unusable state
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-16627: No standby databases support the overall protection mode.
ORA-26032: index string.string loading aborted after string keys
ORA-26076: cannot set or reset value after direct path structure is allocated
IMP-00064: Definition of LOB was truncated by export
ORA-26095: unprocessed stream data exists
ORA-26082: load of overlapping segments on table string.string is not allowed
