Tracing processes to find wait events
If you have worked with Oracle software, particularly in the performance tuning space, you will be familiar with tracing. Tracing enables additional information to be gathered from a given process or function to diagnose performance problems or even bugs. One example is the SQL trace that can be enabled at a database session or the system level to provide key information, such as; wait events, parse, fetch, and execute times.
Oracle GoldenGate 12c offers a similar tracing mechanism through its trace
and trace2
options of the SEND
GGSCI command. This is like the session-level SQL trace. Also, in a similar fashion to performing a database system trace, tracing can be enabled in the GoldenGate process parameter files that make it permanent until the Extract or Replicat is stopped.
trace
provides processing information, whereas trace2
identifies the processes with wait events.
The following commands show tracing being dynamically enabled for 2 minutes on a...