My Oracle Support Banner

DataPump Import Doesn't Load Dependent Objects If "NOT IN" Operator is Used (Doc ID 2134743.1)

Last updated on NOVEMBER 05, 2020

Applies to:

Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version and later
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
Information in this document applies to any platform.


NOTE: The document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Trying to import only some tables from a dump file generated by a schema level export using 'NOT IN' clause in exclude parameter:

impdp <User>/<Password> Parfile = < Par file with below content >
================Par file=================
directory= < Directory >
dumpfile= < Dumpfile >
logfile= < Logfile >
TABLES=SCOTT.% or Schemas=SCOTT -- Use any one of these
exclude=table:"not in ('DEPT','EMP')" -- "not in" operator used

the tables are imported, but their dependent objects are not.





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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.