How To Use The New 11g Events++ Syntax For Easier SQL Tracing Of Datapump Operations?
(Doc ID 813737.1)
Last updated on MAY 13, 2021
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database 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 22-Oct-2013***
As of Oracle11g, a new event syntax has been introduced, which makes it easier to perform tracing of processes. This can be used especially for environments such as Datapump, where multiple processes are started and the lifetime of these processes is volatile.
Up to now, in order to e.g. enable 10046 level 12 tracing for the Datapump processes, one had to obtain the session IDs or OS process IDs of the various Datapump processes, and then use methods like ORADEBUG or DBMS_SYSTEM.SET_EV() to enable the tracing for each process individually.
With the new Events++ syntax, you no longer need to know the session or process ID's of the individual processes, but can quickly and easily enable e.g. 10046 level 12 trace for the processes based on their short names.
The trace files generated are located in the Advanced Diagnostics Repository (ADR).
Next command shows the location of the tracefile(s):
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