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 |
what does the rman-08147 warning signify when your environment has a goldengate capture processes configured?
I have configured oracle goldengate integrated capture process using the default values. As the data load increases I see that extract starts lagging behind by an hour (or more) and database performance degrades. How you will resolve this performance issue?
how do you retrieve information from the oracle credential store?
with integrated delivery, where can we look for the performance stats?
how do you create a csv file from the extracted data?
why should I upgrade my goldengate extract processes to integrated extract?
what are some of the key features of goldengate 12c?
I am migrating my oracle database from non-exadata to exadata but my source ogg software and target ogg software versions are different (say source is running ogg 11.1 and target is running ogg 11.2). How can I configure my ogg process to work in such configuration?
why is supplemental logging required for replication?
list the minimum parameters that can be used to create the extract process?
I want to configure multiple extracts to write to the same exttrail file? Is this possible?
what parameters can be used to configure oracle goldengate to extract data from archived redo log files only?