It is estimated that the Checkpoint Lag calculation method of the rep process on the Oracle GoldenGate (OGG) destination end is called oraclelag.
This article is original. For more information, see the source.
It is estimated that the Checkpoint Lag calculation method of the rep process on the target end of Oracle GoldenGate (OGG) OGG
Background: The following shows the rep process at the OGG target end. At that time, the transmission process at the OGG source experienced a sharp decrease in transmission speed by 1.5 Mb/s due to network congestion. At this time, the source has a large backlog of trail files.
That is to say, the target rep process is in the "not full" state-the transmission speed of the transmission process cannot meet the application speed of the rep process.
GGSCI (hostb) 5> info repbinfo repbREPLICAT REPB Last Started 2014-08-01 14:43 Status RUNNINGCheckpoint Lag 00:00:00 (updated 00:00:12 ago)Log Read Checkpoint File /u02/ggs/dirdat/tb001541 2014-08-01 05:26:32.766558 RBA 32744080GGSCI (hostb) 6> !info repbREPLICAT REPB Last Started 2014-08-01 14:43 Status RUNNINGCheckpoint Lag 09:21:35 (updated 00:00:00 ago)Log Read Checkpoint File /u02/ggs/dirdat/tb001541 2014-08-01 05:26:34.768028 RBA 33105784
Observe the differences between Checkpoint Lag:
The first is Checkpoint Lag 00:00:00. The first is Checkpoint Lag 09:21:35.
The current time is fifteen o'clock P.M,
We can infer the calculation method of Checkpoint Lag Based on the reduction of the file transmission speed of trail:
When a new trail file is transferred to the target end (this trail has not yet been applied), OGG reads the timestamp in the trail file and compares it with the current OS time, so that the Checkpoint Lag is 09:21:35.
When all the trail files are applied, the Checkpoint Lag is 00:00:00
Oracle GoldenGate start stop mgr Error
Kill mgr, or directly kill mgr processes.
PS: this type of problem does not mean the OGG version is a bad habit.
Error Message