Thursday, October 11, 2018

Graceful Stop of Goldengate Extract

It's always a good idea to stop extracts after checking if there is any long running transaction in the database being captured. Failing to do so might later result in hung or unstable processes.

Use following command to check the extract:

GGSCI (test) 3> send e* status

Sending STATUS request to EXTRACT ext ...

EXTRACT ext (PID 16649)
  Current status: In recovery[1]: Processing data with empty data queue
testsrv:/u05/ggate> grep -i bound dirrpt/ext.rpt 
Bounded Recovery Parameter:
2017-06-07 15:48:18  INFO    OGG-01639  BOUNDED RECOVERY:  ACTIVE: for object pool 2: p2628_Redo_Thread_2.
2017-06-07 15:48:18  INFO    OGG-01640  BOUNDED RECOVERY: recovery start XID: 129.15.2953694.  

-- And then Check RBA is moving with following commands
info e*
lag e*

No comments: