ORA-22312: must specify either CASCADE or INVALIDATE option
Answer Posted / guest
Cause: An attempt was made to alter a type which has a
dependent type or table without specifying the CASCADE or
INVALIDATE option.
Action: Resubmit the statement with either the CASCADE or
INVALIDATE option. Specify CASCADE if you want to cascade
the type change to dependent types and tables; otherwise,
specify INVALIDATE to invalidate all dependents.
Please add more information about this Error
| Is This Answer Correct ? | 2 Yes | 1 No |
Post New Answer View All Answers
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.
RMAN-05017: no copy of datafile number found to recover
ORA-26076: cannot set or reset value after direct path structure is allocated
IMG-02003: 2FF03 - incorrect color histogram feature specification
ORA-16516: The current state is invalid for the attempted operation.
ORA-26079: file "string" is not part of table string.string
ORA-26084: direct path context already finished
ORA-26030: index string.string had string partitions made unusable due to:
ORA-26095: unprocessed stream data exists
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?
NZE-28890: Entrust Login Failed
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
IMP-00064: Definition of LOB was truncated by export
ORA-26027: unique index string.string partition string initially in unusable state