DataPump Export (EXPDP) Creates Excessive Traces Even If It Runs Successfully (Doc ID 1154963.1)

DataPump Export (EXPDP) Creates Excessive Traces Even If It Runs Successfully (Doc ID 1154963.1) To BottomTo Bottom


APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.

SYMPTOMS
A simple 11.2 DataPump export (EXPDP) at SCHEMA level (e.g. on SCOTT schema) can be shown to generate a number of DWxx (and also seen from P00x and ORAxx processes) traces in /diag/trace directory. The traces are of the following nature: *** MODULE NAME:(Data Pump Worker) *** ACTION NAME:(SYS_EXPORT_FULL_02) KUPC: Setting remote flag for this process to FALSE prvtaqis - Enter *** 2010-07-15 23:00:23.133 prvtaqis subtab_name upd prvtaqis sys table upd *** 2010-07-15 23:00:23.831 kwqberlst !retval block kwqberlst rqan->lagno_kwqiia 5 kwqberlst rqan->lascn_kwqiia > 0 block


Traces are typically < 100K in length. If the EXPDP run was successful the traces contain no error messages, if EXPDP raises an internal 600/7445 or other errors the traces might contain some equivalent information.


SOLUTION
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The first messages come from package body DBMS_PRVTAQIS which is called during EXPDP/IMPDP. ORACLE Support can confirm that in 11.2 source code the call to DBMS_PRVTAQIS is not considered to be debugging code so there is no option (event/parameter) to disable these traces. The traces will just need to be periodically deleted. It should be noted that EXPDP/IMPDP are not the only products to call DBMS_PRVTAQIS, any product that does can also create these traces and the MODULE NAME in the traces will clarify this. FIXED RELEASE ---- 11.2.0.4 PATCH FIX ---- Patch:12817425 is not available for 11.2.0.1. WORKAROUND ---- None. To purge trace files manually you could execute: adrci> purge -age {minutes} -type TRACE