Pages

Sunday, August 20, 2017

expdp process generates trace file with error ORA-31673

=========================
General
=========================
Oracle expdp process completes successfully, but upon completion, <pid>_dw01*.trc trace file is generated.

=========================
Evidences
=========================
Trace file contains following text:

Trace file /software/oracle/diag/rdbms/igt/igt/trace/igt_dw01_32631.trc
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options
ORACLE_HOME = /software/oracle/111
System name:    Linux
Node name:      aut-mob-5-aps-1
Release:        2.6.18-194.el5
Version:        #1 SMP Tue Mar 16 21:52:39 EDT 2010
Machine:        x86_64
Instance name: igt
Redo thread mounted by this instance: 1
Oracle process number: 458
Unix process pid: 32631, image: oracle@aut-mob-5-aps-1 (DW01)


*** 2017-08-20 02:01:09.514
*** SESSION ID:(268.30456) 2017-08-20 02:01:09.514
*** CLIENT ID:() 2017-08-20 02:01:09.514
*** SERVICE NAME:(SYS$USERS) 2017-08-20 02:01:09.514
*** MODULE NAME:(Data Pump Worker) 2017-08-20 02:01:09.514
*** ACTION NAME:(SYS_EXPORT_FULL_01) 2017-08-20 02:01:09.514

DM-DBMS_DM_MODEL_EXP:schema_callout: schema=SYSTEM, pre_schema=NOOP for 11g

*** 2017-08-20 02:01:09.514
DM-DBMS_DM_MODEL_EXP:schema_callout: schema=OUTLN, pre_schema=NOOP for 11g

*** 2017-08-20 02:01:09.514
DM-DBMS_DM_MODEL_EXP:schema_callout: schema=TSMSYS, pre_schema=NOOP for 11g

*** 2017-08-20 02:01:09.515
DM-DBMS_DM_MODEL_EXP:schema_callout: schema=SHDAEMON, pre_schema=NOOP for 11g



*** 2017-08-20 02:14:43.329
DM-DBMS_DM_MODEL_EXP:schema_callout: schema=HRV_VIPNE_OVMDQ, pre_schema=NOOP for
 11g

*** 2017-08-20 02:18:53.785
KUPP: Error 31673 detected in worker process DW01, worker id=1
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-31673: worker process interrupt for normal exit by master process
ORA-06512: at "SYS.KUPF$FILE_INT", line 972
ORA-06512: at "SYS.KUPF$FILE", line 7126
ORA-06512: at "SYS.KUPW$WORKER", line 4661
ORA-06512: at "SYS.KUPW$WORKER", line 8624
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_SQL", line 1575
ORA-06512: at "SYS.KUPW$WORKER", line 8342
ORA-06512: at "SYS.KUPW$WORKER", line 1545
ORA-06512: at line 2


=========================
Solution
=========================


This is a known issue, documented in Oracle technote:
 Data Pump Export Completed Successfully With Errors ORA-447 & ORA-31673 (Doc ID 1323792.1)

CAUSE
This is discussed in 
Bug 9962464 - ORA-447 AND ORA-31673 OCCURS IN THE WORKER PROCESS WHEN EXPDP IS EXECUTED.
which has been closed with status 33 - Suspended, Req'd Info not Avail

SOLUTION
Ignore the error as the export has already completed and so this is just an unnecessary trace file being generated on exit of the Data Pump Worker process and so has no impact on the database or export. 

In case you would run into the same issue, you could provide a working test case to restart to bug investigation.

=========================
Workaround
=========================

To avoid trace file occupied space, delete *.trc files with below crontab task


delete_expdp_trace_files.sh
#!/bin/bash

HOME_DIR=/software/oracle/diag/rdbms/igt/igt/trace
WORK_DIR=`pwd`
cd ${HOME_DIR}
ls -lt ${HOME_DIR} | grep dw01 | grep trc | awk '{print $9}' | xargs grep -l 00447 | xargs rm -f
cd $WORK_DIR

crontab -l

0 6 * * * /software/oracle/oracle/scripts/delete_expdp_trace_files.sh


=========================
A Similar Issue:

=========================
1956899.1
Lots of Trace Files Reporting "Kcbzib: Dump Suspect Buffer, Err2=1410" 

As a temporary workaround, you can simply delete the files as these should not have been generated for the non-user-visible errors in the first place.

No comments:

Post a Comment