Import Datapump Job fails with ORA-39125

Import Datapump Job fails with ORA-39125 KUPW$WORKER.PUT_DDLS while calling DBMS_METADATA.CONVERT [ID 453918.1]

--------------------------------------------------------------------------------
 
  修改時間 15-SEP-2009     型別 PROBLEM     狀態 MODERATED  

In this Document
  Symptoms
  Cause
  Solution
  References

Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.4 to 10.2.0.3
This problem can occur on any platform.

Symptoms
During IMPDP process , following errors can be reported ::

ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling
DBMS_METADATA.CONVERT []
ORA-06502: PL/SQL: numeric or value error
LPX-00225: end-element tag "BODY" does not match start-element tag "WHENCLAUSE"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6228
----- PL/SQL Call Stack -----
object line object
handle number name
0xed3816d8 14916 package body SYS.KUPW$WORKER
0xed3816d8 6293 package body SYS.KUPW$WORKER
0xed3816d8 12280 package body SYS.KUPW$WORKER
0xed3816d8 3278 package body SYS.KUPW$WORKER
0xed3816d8 6882 package body SYS.KUPW$WORKER
0xed3816d8 1259 package body SYS.KUPW$WORKER
0xd58fc808 2 anonymous block

Cause
Datapump Import  may fail to import with ORA-39125 errors if trigger text on the source database has trailing null characters in the WHEN clause.

Solution
Check for the availability of One Off Patch for Patch 4352110 in Metalink or
Apply patchsets:
10.1.0.5 if running 10.1.0.x
10.2.0.4 if running 10.2.0.x (when it becomes available).

Download and install Patch 4352110  on your source database . After installation on the source database, re-run the export datapump job and then the import datapump job.

The fix is not directly required on the target database for import datapump to work, only if the intention is to run a new export datapump job on that target database and existing triggers have trailing null in WHEN clause.. then you will need to apply the patch on the target database home also.