ORA-39139: Data Pump does not support XMLSchema objects.
string will be skipped.

Answer Posted / guest

Cause: Object has XMLSchema-based columns, which are
unsupported by Data Pump.

Action: Use the original exp and imp utilities to move this
object.

Please add more information about this Error

Is This Answer Correct ?    2 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created

1324


IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier

2401


IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier

2733


IMP-00064: Definition of LOB was truncated by export

6023


IMG-02003: 2FF03 - incorrect color histogram feature specification

1310






when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly

1840


ORA-26076: cannot set or reset value after direct path structure is allocated

1574


IMP-00070: Lob definitions in dump file are inconsistent with database.

1393


ORA-26028: index string.string initially in unusable state

3535


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?

2403


NZE-28868: Peer certificate chain check failed.

2366


RMAN-05017: no copy of datafile number found to recover

2000


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.

2438


ORA-26079: file "string" is not part of table string.string

1605


ORA-26082: load of overlapping segments on table string.string is not allowed

1449