How to Kill Long Running Transactions In The Goldengate Extract

How Problems with Oracle GoldenGate

You can’t close an extract that is a long running transaction with Golden gate. Let’s find out how it’s done.

./ggsci

You can check extract

GGSCI (dev) 21> info all

GGSCI (dev) 21> send extract name showtrans tabular

GGSCI (dev) 21> stop extractname

STOP request pending. There are open, long-running transactions.
Before you stop Extract, make the archives containing data for those transactions available for when Extract restarts.
To force Extract to stop, use the SEND EXTRACT GREPORA_EXT, FORCESTOP command.
Oldest redo log file necessary to restart Extract is:

You can copy extract number range

1189.7.4196989

XIDUSN=1189.XIDSLOT=7.XIDSQN=4196989

select * from gv$transaction;

select b.inst_id,b.sid,b.serial#, b.username,wait_class, state,SECONDS_IN_WAIT,

XIDUSN||’.’||XIDSLOT||’.’||XIDSQN “XID”, (START_SCNW * 4294967296) + START_SCNB “Start SCN” ,SES_ADDR

from gv$transaction a, gv$session b where a.SES_ADDR=b.saddr and a.XIDUSN=1189 and a.XIDSLOT=7 and a.XIDSQN=4196989 

You can detect and kill session address

Have a nice day.

Comments