OGG Extract RBA Not Moving And LAG Increasing And Appears Hung (Doc ID 964705.1)
Typically, when Goldengate is performing recovery:
In recovery[1] – Extract is recovering to its checkpoint in the transaction log. In recovery[2] – Extract is recovering from its checkpoint to the end of the trail. Recovery complete – The recovery is finished, and normal processing will resume. Example: Current status: In recovery[1]: Reading from data source
First time I have seen Processing data with empty data queue and is essentially the same process.
send e* status
Current status: In recovery[1]: Processing data with empty data queue
send e* status
Current status: Recovery complete: Processing data with empty data queue
The scary part is current redo vs Goldengate Checkpoint.
To prevent this, make sure there is no lag, no long running transactions before stopping extract.
select thread#,sequence# from v$log where status='CURRENT' order by 1; THREAD# SEQUENCE# ---------- ---------- 1 1198566 2 1291021 info e* Log Read Checkpoint Oracle Redo Logs 2017-06-07 14:44:53 Thread 1, Seqno 1198492, RBA 112396 Log Read Checkpoint Oracle Redo Logs 2017-06-07 14:45:33 Thread 2, Seqno 1290939, RBA 1060244424
What if integrated extract is used? Where’s my Seqno?
info e* Log Read Checkpoint Oracle Integrated Redo Logs 2017-02-12 18:36:06 SCN 0.4928929 (4928929)
Read more about at Log sequence# and rba# of integrated extract checkpoint
