Table Partition Import with DataPump Generates ORA-39151
(Doc ID 2396615.1)
Last updated on MAY 13, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
You performed an export of a table partition with DataPump export (EXPDP)
For Example:
Then during the import of the table_partition_2, you encounter an ORA-39151 error.
For Example:
Master table "TEST"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "TEST"."SYS_IMPORT_FULL_01": test/******** directory=data_pump_dir dumpfile=test.dmp logfile=imp_test.log tables=test.table_a:table_partition_2
Processing object type TABLE_EXPORT/TABLE/TABLE
ORA-39151: Table "TEST"."INVOICES" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER
Job "TEST"."SYS_IMPORT_FULL_01" completed with 1 error(s) at Wed May 9 13:25:23 2018 elapsed 0 00:00:02
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |