IMPDP 11g Aborts After Errors ORA-942 ORA-39120 When Using Parameters CONTENT=DATA_ONLY And TABLE_EXISTS_ACTION=TRUNCATE
(Doc ID 971983.1)
Last updated on MAY 13, 2021
Applies to:Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.5 to 18.104.22.168 [Release 10.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 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
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.
When using IMPDP with TABLE_EXISTS_ACTION=TRUNCATE and CONTENT=DATA_ONLY, the import process of Oracle11g aborts when the table doesn't exist. In Oracle10g the import process continued with importing the rest of the dump file and only skipped the data of the missing table.
In the following scenario a TEST schema exists with the TEST1 and TEST2 tables. An export is made of this schema:
In this case tne ORA-39120 error is detected, but IMPDP aborts with an import failure and the other tables (in this case TEST1) contained in the dump file are not imported.
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