This document is intended to help you implement the best practice for creating a heartbeat process that can be used to determine where and when lag is developing between a source and target system.
This document will walk you thru the step-by-step process of creating the necessary tables and added table mapping statements needed to keep track of processing times between a source and target database. Once the information is added into the data flow, the information is then stored into target tables that can be analyzed to determine when and when the lag is being introduced between the source and target systems.The heartbeat tables can be used to identify the following information:
- Where lag is developing in each of the processes
- When lag is developing by comparing the commit timestamp with the current time that the record pass thru each process.
These tables also allow you to:
- Create a history of lag to determine what time of day lag develops.
- Create a history to identify if lag is increasing over time.
- Identify if a upstream process is stopped for any reason.
- Monitor DML and DDL statistics
You can find the complete document on the Oracle Support site stored as Document ID:1299679.1
OGG Best Practice - heartbeat table using DBMS_SCHEDULER- V11_0 ID1299679.1