DataPump Import Reports ORA-39082: Object type TRIGGER:"BIN$Vy2CjWh6HoPgVLSZumR3MA==$0" Created With Compilation Warnings And Index Creation Shows Different Name

(Doc ID 2303765.1)

Last updated on SEPTEMBER 18, 2017

Applies to:

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

Symptoms

There is no issue with the export, but during the import an error is reported during the trigger creation phase. The import log shows the following errors when loading the trigger definition:

...
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"GISADMIN"."BIN$Vy2CjWzpHoPgVLSZumR3MA==$0" created with compilation warnings
ORA-39082: Object type TRIGGER:"GISADMIN"."BIN$Vy2CjWzpHoPgVLSZumR3MA==$0" created with compilation warnings
ORA-39082: Object type TRIGGER:"GISADMIN"."BIN$Vy2CjXJoHoPgVLSZumR3MA==$0" created with compilation warnings
ORA-39082: Object type TRIGGER:"GISADMIN"."BIN$Vy2CjXJoHoPgVLSZumR3MA==$0" created with compilation warnings
ORA-39082: Object type TRIGGER:"GISADMIN"."BIN$Vy2CjWlxHoPgVLSZumR3MA==$0" created with compilation warnings

As one can be seen below, after the import, the indexes from the target schema are displayed with recycle bin names, but they are in the regular schema.

 

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