Extract Process Hung after new code installed or extract crash or bounce
(Doc ID 1287969.1)
Last updated on FEBRUARY 27, 2019
Oracle GoldenGate - Version 18.104.22.168.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 (<server_name>) 1> info all
Program Status Group Lag Time Since Chkpt
EXTRACT RUNNING <extract_name> 00:00:01 11:15:02
Note the long lag.
GGSCI (<server_name>) 2> info <extract_name>,showch
EXTRACT <extract_name> 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 xxxx, RBA xxxx
Investigation shows that the redo logs are available.
Information from the extract report shows (sample):
INFO OGG-01639 BOUNDED RECOVERY: ACTIVE: for object pool 1:xxxx_Redo Thread 1.
INFO OGG-01640 BOUNDED RECOVERY: recovery start XID: xxxxxx.
INFO OGG-01641 BOUNDED RECOVERY: recovery start position: SeqNo: xxxx, RBA: xxxx, SCN: xxxx, Timestamp: 2011-01-24 21:33:10.000000.
INFO OGG-01642 BOUNDED RECOVERY: recovery end position: SeqNo: xxxx, RBA: xxxx, SCN: xxxx, Timestamp: 2011-01-25 01:44:48.000000.
INFO OGG-01643 BOUNDED RECOVERY: CANCELED: for object pool 1: xxxx_Redo Thread 1.
This has been seen after extract has been stopped and started, after extract crashes and after code upgrades.
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
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.