Return
-
Title
[KEEPER] Update with CASE statement causing out of sync -
Description
When updating source table with CASE statement in such a way that one of the unique key column values are swapped between two existing rows, target table goes out of sync with unique constraint violation.
On source, oracle does not raise unique constraint violation as it is one update that changes both rows. On target, SharePlex post executes update statement for each row separately based on how it is written in redo log and it raises unique constraint violation.
Sign In Required
You need to be signed in and under a current maintenance contract to view premium knowledge articles.