Wrong ordering records audit with DML Time (using INSERTALLRECORDS)
edited Jul 2, 2020 4:37AM in GoldenGate, Streams and Distributed Database (MOSC) 4 commentsAnswered ✓
Hi guys,
We're facing the problem while ordering records audit from Source table with INSERTALLRECORDS option. In source system, many actions will apply for each ID, and we can to get the last action for each ID, but we have a wrong case in an example:
We'are add Token in Extract with following configure:
TABLE mbk.DOC, SQLEXEC (id lookup, query "select cast(systimestamp as timestamp) dml_time from dual", NOPARAMS), TOKENS (TK_OP_TIME_EX = @GETVAL(lookup.dml_time));
In Replicat, we added the column: OP_TIME_EX = @TOKEN ('TK_OP_TIME_EX')
The result has some records have wrong ordering in example bellow. It means the row with INSERT action has TK_OP_TIME_EX later than rows with UPDATE action.
Tagged:
0