GoldenGate Fails To Get New Transactions After The Daylight Savings Time Change.
(Doc ID 2209526.1)
Last updated on NOVEMBER 14, 2019
Applies to:Oracle GoldenGate - Version 220.127.116.11.1 to 18.104.22.168.0 [Release 11.2 to 12.2]
IBM i on POWER Systems
Check for relevancy 12/12/2018
We noticed that several processes were, though running, not applying any new transactions.
This afternoon - well after the time switch - the current checkpoint was still 11-06-2016 01:52 because no new trails were coming over.
No alerts to the true lag time came were made because essentially, the replicat was caught up.
At this time we are not sure what has caused this.
Source database is DB2 for i Series - 7.1 TR10
Target database is Oracle 22.214.171.124
I have altered the extract pump on source to start at extrba 0 of the last trailfile received on the target system. I verified that the pump could communicate with the target system, and it continued to process trails in the sequence. However, transactions stop at the time of the time switch. The last transaction applied has a timestamp of 2016/11/06 01:00:00.591.936 RBA 92656175. All processes are shown to be running.
It really seems like the extract is unable to get any transactions from the journals as no transactions are seen from the STATS EXTRACT command.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document