OGG can insert duplicate rows when there is no unique index primary key UI PK defined [ID 1350948.1]

Applies to:

Oracle GoldenGate - Version: 9.5_EA and later [Release: 9.5.0 and later ]
Information in this document applies to any platform.

Symptoms

Target table with no UI or PK has duplicate rows after initial load.

Replicat is (may be) using HANDLECOLLISIONS and KEYCOLS

Changes

An initial load.

Cause

It is possible to get duplicate rows because there is no key / index constraint to prevent it. Keycols will not help.

Solution

Replicat relies on the database to return a constraint error when a duplicate row is inserted. In cases where there is no UI or PK, no error is returned. HC will not help because there is no error. KEYCOLS is used as a retrieval mechanism, not an index on a write.

The fact that replicat treats the whole row as a key when there is no defined key is no help.

Replicat has no way of knowing it should not insert a duplicate row if there is no constraint.

User must define a key or UI.[@more@]

ITPub博客

goldengate 的initial load 当目的表无pk或者ui时会产生重复记录

Applies to:

Symptoms

Changes

Cause

Solution

最新文章