$ id
uid=204(oracle) gid=203(dba) groups=1(staff)
$ impdp cruiser/cruiser directory=backup_expdp dumpfile=expdp_ultracruiser.dump TABLES=BUSINESS_TABLE REMAP_TABLESPACE=ULTRACRUISER:CRUISER_DEFAULT parallel=1 job_name=impdp_ultracruiser logfile=impdp_ultracruiser.log;
Import: Release 10.2.0.4.0 - 64bit Production on Tuesday, 22 May, 2012 11:16:37
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 "CRUISER"."IMPDP_ULTRACRUISER" successfully loaded/unloaded
Starting "CRUISER"."IMPDP_ULTRACRUISER": cruiser/******** directory=backup_expdp dumpfile=expdp_ultracruiser.dump TABLES=BUSINESS_TABLE REMAP_TABLESPACE=ULTRACRUISER:CRUISER_DEFAULT parallel=1 job_name=impdp_ultracruiser logfile=impdp_ultracruiser.log
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39151: Table "ULTRACRUISER"."BUSINESS_TABLE" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling DBMS_METADATA.CONVERT []
ORA-04030: out of process memory when trying to allocate 112048 bytes (session heap,kuxLpxAlloc)
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
7000000976b9c88 15032 package body SYS.KUPW$WORKER
7000000976b9c88 6372 package body SYS.KUPW$WORKER
7000000976b9c88 12391 package body SYS.KUPW$WORKER
7000000976b9c88 3346 package body SYS.KUPW$WORKER
7000000976b9c88 6972 package body SYS.KUPW$WORKER
7000000976b9c88 1314 package body SYS.KUPW$WORKER
7000000ab8028f8 2 anonymous block
Job "CRUISER"."IMPDP_ULTRACRUISER" stopped due to fatal error at 11:16:43
The error is due to the unpublished Bug 6051734. The root problem is
the way that indexes are loaded through XML. In earlier versions of the
database experiencing this problem, excessive memory could be used to
perform the index loads.
This bug is fixed in 10.2.0.5 and is backportable for earlier releases.
阅读(1026) | 评论(0) | 转发(0) |
