Logdump is installed in the Oracle GoldenGate Installation home directory. You can start Logdump using the following commands:
- GGSCI>sh ./logdump
| || |
A Demonstration Video of Logdump
2.1 Example 1: Skipping transactions in replicat
The first example (op000000) shows how to use logdump to skip transactions on the replicat side. This happens when some wrong transactions are executed on the source database while the replication is running. In this example, while replicating only the MEMBER tables from the PANU schema, there are some transactions updating on the WORLD_REGION table. Because there is no WORLD_REGION table on the target, the replicat will abend. The solution is to find the transactions for the WORLD_REGION table and skip them. Let's look at how we can find this using logdump.
First, we start the logdump and enable ggstoken detail display shown as follows:
You can also use logdump to discovery some mysterous transactions in your replication. In this example, after I enabled the automatic heartbeat table feature, I found the size of the trail file keeps increasing even there is no transaction on the source database. I stop the extract and perform and ETROLLOVER to create a new trail file.
- Oracle A-Team Paper: Oracle GoldenGate: Logdump
- Oracle® GoldenGate Logdump Reference for Oracle GoldenGate
- 6/28/2016: Added the example to reposition reposition replication process.
- 12/8/2016: Added the example analyizing heartbeat seed records in the trail file with automatic heartbeat table feature enabled.