We are facing issue when capture become down for extended period of time.
For DB2 as source our transaction log get archived and then purged after some time. Once transaction log get purged we need to reactivate replication fresh as pointer to last LSN get lost.
We are codding / enhancing our tran log archive / purge script not to do purge of tran log if replication is not catched up.
To meet this requirement, we want to know how from HVR we can know the current LSN position upto its read the data so that only prior to this LSN marker.
For High volume system we need to dynamic control transaction log purging depend upon replication LSN marker.
to record and fetch some LSN position, may not be upto point but periodic update and that we can use as reference .