My Oracle Support Banner

Veridata showing incorrect out of sync for MSSQL data type datetime and datetime2 (Doc ID 2998667.1)

Last updated on JULY 20, 2024

Applies to:

Oracle GoldenGate Veridata - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

Veridata Server Microsoft Windows x64 (64-bit)

Source and target agent Microsoft Windows x64 (64-bit)

Java version: 1.8.0_251

Patch level-- 12.2.1.4.220831


Problem Description
-------------------



Veridata shows incorrect value as out of sync compared to the actual value stored in MSSQL database for the datatype datetime/datetime2.This incorrect value is an offset in the date time value from the actual value in database and the offset is consistent across all the out of sync rows for the same columns.

For example, for datetime2:

Actual Value in Database Veridata UI Offset
2016-03-13 02:11:57.056388 2016-03-13 03:11:57.056388 1 hour

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.