impdp的一个case

[oracle@host101] /oracle/dmp 997>impdp system/oracle  DIRECTORY=EXPDP_DIR  dumpfile=exp111.dmp logfile=imp.log  remap_schema=business:bustest TABLE_EXISTS_ACTION = REPLACE PARALLEL=4;

Import: Release 10.2.0.4.0 - 64bit Production on Friday, 06 January, 2012 17:24:56

Copyright (c) 2003, 2007, Oracle.  All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYSTEM"."SYS_IMPORT_FULL_02" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_FULL_02":  system/******** DIRECTORY=EXPDP_DIR dumpfile=exp111.dmp logfile=imp.log remap_schema=business:bustest TABLE_EXISTS_ACTION = REPLACE PARALLEL=4
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "BUSTEST"."FHEXITEMKIND"                    1.835 MB   31849 rows
. . imported "BUSTEST"."FHFINALREINS"                    32.19 KB     409 rows
. . imported "BUSTEST"."FHPRIORITY"                      12.28 KB     162 rows
. . imported "BUSTEST"."FHREINS"                         15.57 KB     226 rows
. . imported "BUSTEST"."FHRISK"                          16.63 KB     553 rows
. . imported "BUSTEST"."FHSECTION"                       15.14 KB     105 rows
. . imported "BUSTEST"."FHTREATY"                        47.01 KB     114 rows
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
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 "HIST_GRAM_LIST_ITEM" does not match start-element tag "EPVALUE"

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6307

----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
0x18b2e8f88     15032  package body SYS.KUPW$WORKER
0x18b2e8f88      6372  package body SYS.KUPW$WORKER
0x18b2e8f88     12391  package body SYS.KUPW$WORKER
0x18b2e8f88      3346  package body SYS.KUPW$WORKER
0x18b2e8f88      6972  package body SYS.KUPW$WORKER
0x18b2e8f88      1314  package body SYS.KUPW$WORKER
0x1f4550410         2  anonymous block

Job "SYSTEM"."SYS_IMPORT_FULL_02" stopped due to fatal error at 17:25:10

 

SQL> host oerr ora 39125
39125, 00000, "Worker unexpected fatal error in %s while calling %s [%s]"
// *Cause:  An unhandled exception was detected internally within the worker
//          process for the Data Pump job while calling the specified external
//          routine.  This is an internal error.  Additional information may be
//          supplied.
// *Action: If problem persists, contact Oracle Customer Support.

---alert.log-----------------------------
Thread 1 advanced to log sequence 13813 (LGWR switch)
  Current log# 1 seq# 13813 mem# 0: /oracle/oradata/tdb01/redo01.log
Fri Jan  6 17:24:57 2012
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=252, OS id=26156
         to execute - SYS.KUPM$MCP.MAIN('SYS_IMPORT_FULL_02', 'SYSTEM', 'KUPC$C_1_20120106172457', 'KUPC$S_1_20120106172457', 0);
kupprdp: worker process DW01 started with worker id=1, pid=254, OS id=26158
         to execute - SYS.KUPW$WORKER.MAIN('SYS_IMPORT_FULL_02', 'SYSTEM');
kupprdp: worker process DW02 started with worker id=2, pid=259, OS id=26201
         to execute - SYS.KUPW$WORKER.MAIN('SYS_IMPORT_FULL_02', 'SYSTEM');

-----------support said---------------------------------------------

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

Solution
Check for the availability of one-off Patch 4352110 or apply patchsets:

10.1.0.5 if running 10.1.0.x
10.2.0.4 or above if running 10.2.0.x

After installation on the source database, re-run the export DataPump job and then the import job.

The fix is not directly required on the target database for DataPump import, only if you intend to run a new DataPump export job in target database and existing triggers have trailing null in WHEN clause.

 

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/713360/viewspace-714551/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/713360/viewspace-714551/