ORA-39021: Database compatibility version string is not
supported.
Answer Posted / guest
Cause: User selected COMPATIBLE as the version on an
DBMS_DATAPUMP.OPEN API, but the current database
compatibility version is not supported by the Data Pump API.
Database versions before 9.2 are not supported by the Data Pump.
Action: Specify a supported version and recreate the job.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
RMAN-05017: no copy of datafile number found to recover
ORA-26095: unprocessed stream data exists
IMP-00070: Lob definitions in dump file are inconsistent with database.
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
ORA-26076: cannot set or reset value after direct path structure is allocated
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
ORA-16516: The current state is invalid for the attempted operation.
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-26082: load of overlapping segments on table string.string is not allowed
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-28868: Peer certificate chain check failed.
ORA-26028: index string.string initially in unusable state
ORA-26027: unique index string.string partition string initially in unusable state