IMPDP gives failed messages in oracle 19c [message #677056] |
Tue, 13 August 2019 06:30 |
|
sreekanth3y
Messages: 2 Registered: August 2019
|
Junior Member |
|
|
Migrated DB from 12c and 19c with IMPDP utility , while importing I have seen some error, below is the trace for the same
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/STATISTICS/MARKER
VM247_RCDB_121GA.PK_TXI : sqlerrm = ORA-20000: Unable to set values for index PK _TXI: does not exist or insufficient privileges
VM247_RCDB_121GA.PK_ARRE : sqlerrm = ORA-20000: Unable to set values for index P K_ARRE: does not exist or insufficient privileges
VM247_RCDB_121GA.PK_ARA : sqlerrm = ORA-20000: Unable to set values for index PK _ARA: does not exist or insufficient privileges
VM247_RCDB_121GA.SYS_C0034921 : sqlerrm = ORA-20000: Unable to set values for in dex SYS_C0034921: does not exist or insufficient privileges
VM247_RCDB_121GA.PK_TXA : sqlerrm = ORA-20000: Unable to set values for index PK _TXA: does not exist or insufficient privileges
Importing statistics failed for 20 object(s);
Processing object type SCHEMA_EXPORT/MATERIALIZED_VIEW Job "SYSTEM"."SYS_IMPORT_SCHEMA_01" completed with 22 error(s) at Wed Aug 7 08:2 8:32 2019 elapsed 0 00:05:25
and utilites are: (expdp from 12c and impdp from 19c)
expdp system/admin@orcl schemas=VM247_RCDB_121GA directory=DATA_PUMP_DIR dumpfile=VM247_RCDB_121V10.dmp logfile=VM247_RCDB_121V10.log
impdp system/admin@orcl19c schemas=VM247_RCDB_121GA directory=DATA_PUMP_DIR dumpfile=VM247_RCDB_121V10.DMP logfile=VM247_RCDB_121V10_imp.log
|
|
|
|
|
Re: IMPDP gives failed messages in oracle 19c [message #677062 is a reply to message #677060] |
Wed, 14 August 2019 05:19 |
John Watson
Messages: 8960 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
I can't see why there is any action needed (other than that I already suggested). That CONSTRAINT_INDEX column isn't documented but all it does (I think) is tell you whether the index will be dropped if you drop the constraint. Perhaps the indexes were created implicitly and then renamed, something like that might cause this sort of confusion.
You could raise a TAR to check with Support.
|
|
|