DataPump Export (EXPDP) Creates Excessive Traces Even If It Runs Successfully
(Doc ID 1154963.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 29-Jul-2013***
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data .Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
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:
*** 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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document