DataPump Import (IMPDP) Reports ORA-31684 When Parameter EXCLUDE Is Specified (Doc ID 1109103.1)

Last updated on APRIL 18, 2013

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 18-APR-2013***

Symptoms

DataPump import (IMPDP) fails with error ORA-31684, if the parameter EXCLUDE=USER:"=<USER_NAME>" is specified.

#> impdp / DUMPFILE=DB2P.DMP EXCLUDE=USER:\"=\'DBP2_TOO\'\" REMAP_SCHEMA=DB2P:DBP2_TOO DIRECTORY=DATA_PUMP_DIR LOGFILE=IMP_DBP2_TOO_3.LOG

Import: Release 11.2.0.1.0 - Production on Tue Apr 27 15:43:49 2010

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Master table "OPS$ORASBP01"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "OPS$ORASBP01"."SYS_IMPORT_FULL_01": /******** dumpfile=db2p.dmp exclude=USER:"='DBP2_TOO'" remap_schema=db2p:dbp2_too directory=data_pump_dir logfile=imp_dbp2_too_3.log
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"DBP2_TOO" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
...

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms