How can we report on long running transactions?
Answer / Brijendra Kumar
To report on long running transactions in Oracle GoldenGate, you can use the ggreport command. The following is an example of how to generate a report for long running transactions:
1. Run the ggextract command with the log_archive_dest parameter set to capture transaction logs.
2. Use the ggreport command to create a report based on the captured logs, specifying the 'lag' parameter to filter out transactions that took too long to complete.
| Is This Answer Correct ? | 0 Yes | 0 No |
we want to setup one-way data replication for my online transaction processing application. However there are compressed tables in the environment. Please suggest how I can achieve it?
how do you add credentials to the credential store?
what transaction types does goldengate support for replication?
if have created a replicate process in ogg 12c and forgot to specify discardfile parameter. What will happen?
what is the purpose of the defgen utility?
what does the goldengate csn equate to, in the oracle database?
what are the areas to monitor in goldengate replication?
what are the most common reasons of the replicate process slowing down?
what parameters can be used to configure oracle goldengate to extract data from archived redo log files only?
what command can be used to view the checkpoint information for the extract process?
is it possible to start ogg extract at a specific csn?
what are the different data encryption methods available in ogg 12c?