Extract Process Hung after new code installed or extract crash or bounce
(Doc ID 1287969.1)
Last updated on JANUARY 22, 2018
Oracle GoldenGate - Version 126.96.36.199.8 and later
Information in this document applies to any platform.
***Checked for relevance on 16-Dec-2013***
After a code upgrade or after extract has been stopped and started, extract appears to hang.
There are sometimes indications that the extract is in Bounded Recovery (BR) mode.
Information from GGSCI shows (sample)
GGSCI (scdb1eqab.ultradns.net) 1> info all
Program Status Group Lag Time Since Chkpt
EXTRACT RUNNING EC1AB 00:00:01 11:15:02
Note the long lag.
GGSCI (scdb1eqab.ultradns.net) 2> info ec1ab,showch
EXTRACT EC1AB Last Started 2011-01-18 19:57 Status RUNNING
Checkpoint Lag 00:00:01 (updated 11:16:15 ago)
Log Read Checkpoint Oracle Redo Logs
2011-01-25 04:12:15 Thread 1, Seqno 7062, RBA 368656672
Investigation shows that the redo logs are available.
Information from the extract report shows (sample):
2011-01-25 04:40:01 INFO OGG-01639 BOUNDED RECOVERY: ACTIVE: for object pool 1: p1610_Redo Thread 1.
2011-01-25 04:40:01 INFO OGG-01640 BOUNDED RECOVERY: recovery start XID: 11.32.84675.
2011-01-25 04:40:01 INFO OGG-01641 BOUNDED RECOVERY: recovery start position: SeqNo: 7042, RBA: 58813968, SCN: 0.324377792 (324377792), Timestamp: 2011-01-24 21:33:10.000000.
2011-01-25 04:40:01 INFO OGG-01642 BOUNDED RECOVERY: recovery end position: SeqNo: 7055, RBA: 36072976, SCN: 0.328047043 (328047043), Timestamp: 2011-01-25 01:44:48.000000.
2011-01-25 04:40:01 INFO OGG-01643 BOUNDED RECOVERY: CANCELED: for object pool 1: p1610_Redo Thread 1.
This has been seen after extract has been stopped and started, after extract crashes and after code upgrades.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms