header__timestamp in change tables off by 2 months

[Anonymous]

I have just started to type 2 data in our warehouse and am starting to interrogate the change tables and their values.   I notice that starting in about mid October 2021  the header__transaction date is about 2 months ahead of the varchar value stored in header__change_seq.   This is consistant across all our tasks that span different SQL Server Sources.   Prior to mid October 2021 the header__change_seq value and header__timestamp were the same.  So today (2/16/2022) I have change records being added to  change tables with a header__timestamp of "2022-04-07 hh:mi:ss.xxx".  Has anyone seen this and is this something with Postgres?

[shashi_holla · Accepted solution]

Hi Brian,

Are you on Replicate version 7.0 because this issue was reported earlier in Replicate version 7.0.0.514 or prior and was fixed in version 7.0.0.555. 

Thanks,

[Anonymous]

Thanks, we are on 7.0.0.470. so we will get up to date ASAP.

[Anonymous]

Upgrading solved the issue.