Import Reports ORA-39083 And ORA-38412 On DBMS_EXPFIL_UTL Actions When Additional Expression Filter Objects Are Loaded Into The DumpFile (Doc ID 2194114.1)

Last updated on OCTOBER 24, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 to 12.1.0.2 [Release 11.2 to 12.1]
Information in this document applies to any platform.

Symptoms

During a table level export, DataPump Utility can unload in the dump file the Expression Filter metadata.
For this case, when using Data Pump Import to import objects, even a single table import attempts to import additional objects. This causes errors similar to the following:

...
Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCACT_INSTANCE
ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
ORA-38412: Expression set column <table_name>.SQL_CONDITION does not exist.
Failing sql is:
BEGIN
/* POST_EXPTABLE_DUMP - Table name :<table_name> */
/* dump all associations for the table */
exfsys.dbms_expfil_utl.set_parameter('EXF$EXPDBVERSION','11.2.0.2.0');
exfsys.dbms_expfil_utl.set_parameter('EXF$EXPEXFVERSION','1');
begin
exfsys.dbms_expfil_utl.set_parameter('EXF$EXPIDXPARAMSTR', n
ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
ORA-38412: Expression set column xxxxx.xxxxx does not exist.
...


 where <table_name> is a table being imported and xxxxx.xxxxx could be any string.

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