Usage Of Handletpkupdate Requires Specific Defer Settings On Table
(Doc ID 1303231.1)
Last updated on NOVEMBER 04, 2019
Applies to:Oracle GoldenGate - Version 220.127.116.11.0 to 18.104.22.168.1 [Release 11.1.1 to 22.214.171.124]
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
When a transaction as examined by Logdump, contains transient primary Key updates and compressed updates, various update error occur. Unique Key or Primary Key constraints violations are common errors seen in Replicat report file. The replicat is moving keys as it is updating them and may lose track of them if the table is not set up correctly.
The problem is limited to tables in which the key columns was updated by using transient update statement, such as "update <table name> set <keycol> = <keycol> +1 ". This will cause the key columns value to be increased to one higher for each row or a set of rows depends on the where clause.
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