ORA-39120: Table string can't be truncated, data will be
skipped. Failing error is: string
Answer Posted / guest
Cause: Table data was about to be loaded into a table that
already existed and the table_exists_action parameter is
truncate, but the table could not be truncated.
Action: Determine actual cause by looking at base error.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
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-26028: index string.string initially in unusable state
IMP-00064: Definition of LOB was truncated by export
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
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-26030: index string.string had string partitions made unusable due to:
IMG-02003: 2FF03 - incorrect color histogram feature specification
ORA-26079: file "string" is not part of table string.string
ORA-26084: direct path context already finished
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
ORA-26076: cannot set or reset value after direct path structure is allocated
IMP-00070: Lob definitions in dump file are inconsistent with database.
ORA-26082: load of overlapping segments on table string.string is not allowed
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.