Suggest an Idea

[CAH123]

HI Team, 

We are facing data mismatch issue in our replication tasks.  We want to make sure correct data is replicating from source to target and that's why we are focusing on commit timestamp for record at source & target end. 

If we get this information from API call then we will use such API call in our python script and use it to match records in source and target without going into database. 

Thank you

CAH

[bobvecchione]

Currently reviewing.

[Shelley_Brennan]

Could you share the type of source systems?  We are planning on adding a header column for the commit timestamp in the source database system - would this satisfy your need if it was available?

[Shelley_Brennan]

Could you share the type of source systems?  We are planning on adding a header column for the commit timestamp in the source database system - would this satisfy your need if it was available?

[cah_admin]

Hi Shelly,

Is this Head column for the source system  only?  

What about in Target system , We want to know when last change has been applied in Target system as well. 

We are currently using below Source systems:

SAP HANA

ORACLE 

SQL SERVER 

DB2 LUW

DB2 iSeries 

MY SQL 

Please let me know if you have any questions.

Regards,

Venkata

[Shelley_Brennan]

Thank you for the additional details here.  We will let you know when we have any updates to share for the sources you listed. 

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.