Starting Oracle GoldenGate 12.2, heartbeat table is provided within Oracle GoldenGate. Loren wrote an A-Team blog on this, I would not repeat. Please refer to his paper at:
- Oracle GoldenGate: Integrated Heartbeat by Loren Penton, 12/18/2017.
- You need to specify a schema (in GLOBALS file) both on the source and the target to store the heartbeat tables.
- You can enable or disable heartbeat table feature with ENALBEL_HEARTBEAT_TABLE | DISABLE_HEARTBEAT_TABLE in extract/replicat process or per instance using GLOBALS.
- The database user managing the heartbeat tables should have sufficient privileges to create tables, views, and scheduler jobs within this schema.
- You can add heartbeat table with GGSCI add heartbeat table command. You can specify the how often the heartbeat tables are updated (60 seconds by default), how long data retained in the heartbeat table (30 days by default) and how often the data is purged (1 day by default).
- GoldenGate processes have to restart to use the heartbeat feature.
- You can login to the Oracle GoldenGate schema and run the GGSCI lag rtpc command to check the end-to-end lag.
Resources
- Oracle GoldenGate 12.2 Documentation 12.2: 18.4 Using Automatic Heartbeat Tables to Monitor
RSS Feed