Goldengate - op_ts is not detailed enough

151 Views Asked by At

We have configured goldengate to generate avro files every 10 minutes, a single record with an X primary key can be inserted/updated within the same 10 minutes.

We've been receiving something like this (loading the data in snowflake into a timestamp_ntz column with length of 3 in miliseconds option):

optype      op_ts                         columnA
I           2023-07-31 16:15:59.015       "Hello"
U           2023-07-31 16:15:59.015       "Bye"

The update comes after the insert in the oracle database, when i make a select in snowflake with a rownumber ordering the op_ts in a descending order is returning the insert row and not the update,

You guys know any workaround? Maybe increasing the 3 miliseconds option in snowflake to 9 hoping to have a difference? Adding another parameter in the avro file of goldengate?

Thanks

0

There are 0 best solutions below