EXPDP Error ORA-39029

Source: Internet
Author: User
Source end Hp-unix+oracle10g-r204-rac, Target end redhat+oracle10g.
Using Network_link export on the target side, the error is as follows:
Rm/opt/oradir/expdp.dmp
EXPDP \ "Sys/oracle as Sysdba\" Directory=oradir network_link=portal95 schemas=rbt dumpfile=expdp.dmp logfile=expdp.log Exclude=statistic

Ora-39014:one or more workers have prematurely exited.
Ora-39029:worker 2 with process name "DW02" prematurely terminated
Ora-31671:worker process DW02 had an unhandled exception.
Ora-12801:error signaled in parallel query server
Ora-29913:error in executing odciexttablepopulate callout
Ora-29400:data Cartridge Error
Kup-04038:internal error:kupax-meta1
Ora-06512:at "SYS. Oracle_datapump ", line 78
Ora-06512:at "SYS. Kupw$worker ", line 1345
Ora-06512:at Line 2

Job "SYS". Sys_export_schema_05 "stopped due to fatal error at 13:53:52

Alert.log
The first error to see is:
Thu May 24 13:51:34 2012
The value of Maxtrans parameter ignored.
Kupprdp:master process DM00 started with pid=38, OS id=5089
To Execute-sys. KUPM$MCP. MAIN (' sys_export_schema_05 ', ' SYS ', ' kupc$c_1_20120524135135 ', ' kupc$s_1_20120524135135 ', 0);
Kupprdp:worker process DW01 started with worker id=1, pid=39, OS id=5091
To Execute-sys. Kupw$worker. MAIN (' sys_export_schema_05 ', ' SYS ');
Kupprdp:worker process DW02 started with worker id=2, pid=40, OS id=5096
To Execute-sys. Kupw$worker. MAIN (' sys_export_schema_05 ', ' SYS ');
Kupprdp:worker process DW03 started with worker id=3, pid=42, OS id=5098
To Execute-sys. Kupw$worker. MAIN (' sys_export_schema_05 ', ' SYS ');
Kupprdp:worker process DW04 started with worker id=4, pid=43, OS id=5100
To Execute-sys. Kupw$worker. MAIN (' sys_export_schema_05 ', ' SYS ');
Kupprdp:worker process DW05 started with worker id=5, pid=44, OS id=5102
To Execute-sys. Kupw$worker. MAIN (' sys_export_schema_05 ', ' SYS ');
Kupprdp:worker process DW06 started with worker id=6, pid=45, OS id=5104
To Execute-sys. Kupw$worker. MAIN (' sys_export_schema_05 ', ' SYS ');
Kupprdp:worker process DW07 started with worker id=7, pid=46, OS id=5106
To Execute-sys. Kupw$worker. MAIN (' sys_export_schema_05 ', ' SYS ');
Kupprdp:worker process DW08 started with worker id=8, pid=47, OS id=5108
To Execute-sys. Kupw$worker. MAIN (' sys_export_schema_05 ', ' SYS ');
Thu May 24 13:52:15 2012

It was checked that the error was generated by creating a backup primary table (master) at the time of the backup (use similar to create TABLE <table_name> (<columns_list>) Initrans Maxtrans 30 statement creation, the hint parameter Maxtrans has been discarded, is a bug, skip.
Keep looking down:
Memory notification:library Cache Object loaded into SGA
Heap size 2048K exceeds notification threshold (2048K)
KGL Object Name:sys. kupc$c_1_20120524135135

Hey, this problem has been dealt with before, but also a bug, the implied parameter _kgl_large_heap_warning_threshold the default value is 2M, which controls the size of the object loaded into memory, when the loaded object is greater than 2M, Will be prompted in the alert warning file. The default value for this parameter is adjusted to 50M at the 10.2.0.2 start. This library is a test library, before it can be upgraded, ready to advance the advanced testing work and then upgrade.
Processed as follows:
Sql> Select A.KSPPINM name,b.ksppstvl value,a.ksppdesc description from X$ksppi A,X$KSPPCV b where a.indx = B.indx D a.ksppinm = ' _kgl_large_heap_warning_threshold ';

NAME
--------------------------------------------------------------------------------
VALUE
--------------------------------------------------------------------------------
DESCRIPTION
--------------------------------------------------------------------------------
_kgl_large_heap_warning_threshold
2097152
Maximum heap size before KGL writes warnings to the alert log


Sql> Select 2097152/1024/1024 MB from dual;

MB
----------
2

Sql> alter system set "_kgl_large_heap_warning_threshold" =52428800 scope=spfile;

System altered.

sql> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
Sql> Startup
ORACLE instance started.

Total System Global Area 2147483648 bytes
Fixed Size 1220432 bytes
Variable Size 419430576 bytes
Database buffers 1711276032 bytes
Redo buffers 15556608 bytes
Database mounted.
Database opened.
Sql> Select A.KSPPINM name,b.ksppstvl value,a.ksppdesc description from X$ksppi A,X$KSPPCV b where a.indx = B.indx D a.ksppinm = ' _kgl_large_heap_warning_threshold ';

NAME
--------------------------------------------------------------------------------
VALUE
--------------------------------------------------------------------------------
DESCRIPTION
--------------------------------------------------------------------------------
_kgl_large_heap_warning_threshold
52428800
Maximum heap size before KGL writes warnings to the alert log

OK, the error message in the alarm log has been checked and processed, and now look back at the error that EXPDP throws:
Ora-39014:one or more workers have prematurely exited.
Ora-39029:worker 2 with process name "DW02" prematurely terminated
Ora-31671:worker process DW02 had an unhandled exception.
Ora-12801:error signaled in parallel query server
Ora-29913:error in executing odciexttablepopulate callout
Ora-29400:data Cartridge Error
Kup-04038:internal error:kupax-meta1
Ora-06512:at "SYS. Oracle_datapump ", line 78
Ora-06512:at "SYS. Kupw$worker ", line 1345
Ora-06512:at Line 2

Search the next, seemingly a lot of people have encountered, remove parallelism can also be a version of the problem.
Afterwards, after upgrading to 10.2.0.5, the problem does not exist, and parallel exports continue to be used.
-the end-

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.