ORA-39130: Object type string not imported. Base object name
conflicts with the master table
- 1 Answers
- 2875 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: The object being imported from the remote instance is
dependent on an object that has the same name as the master
table running this Data Pump job.
Action: Rerun the Data Pump job with a nonconflicting name.
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
ORA-16516: The current state is invalid for the attempted operation.
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
ORA-26079: file "string" is not part of table string.string
ORA-26027: unique index string.string partition string initially in unusable state
ORA-26094: stream format error: input column overflow
IMG-02003: 2FF03 - incorrect color histogram feature specification
NZE-28890: Entrust Login Failed
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
IMP-00064: Definition of LOB was truncated by export
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-26084: direct path context already finished
NZE-28868: Peer certificate chain check failed.
ORA-26032: index string.string loading aborted after string keys
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
