Skip to main content
Documentation
Feature Requests Trust Center Status Page

Community

Connector Improvement: Record current LSN position for DB2 as source

Tushar Sharma User

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 .

Thanks

 

Tushar

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Mark Van de Wiel Fivetranner

    Tushar,

    HVR's capture state is in the capture state file in $HVR_CONFIG/hubs/<hub name>/channels/<channel name>/locs/<source location>/router.

    Note that the LSN is the commit moment. HVR will need to go further back into the logs in order to fully capture in flight transactions.

    Also note that include in the destination integrate state table rewind information to go back to the log stream and recapture all transactions.

    I don't know that it is easy to decipher what logs you can purge from this information but please do verify.

    Thanks,
    Mark.

  • Mark Van de Wiel Fivetranner

    Also note that we plan to build support for capture rewind on DB2 LUW by 1HCY2024. We do not currently have this capability on the DB2 LUW platform.

    Thanks,
    Mark.