WARNING OGG-06439 when table have “enable novalidate” Primary KEY
If a table has a PK constraint or a Unique Constraint that is Non-Validated or Invalid, OGG will by default not use those keys to uniquely identify a row. It will use all columns to uniquely identify a row. This may become an issue due to the increased space required for both trails and redo logs. It will also force all updates to become PK Updates. This could become a performance issue on the target because it may not use an index to apply the data.
2022-04-02T11:56:36.778+0800 WARNING OGG-06439 Oracle GoldenGate Delivery for Oracle, rep_XXX.prm: No unique key is defined for table TAB_XXXXXXXXXX. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
# check indexes on table
SQL> @cons %.TAB_XXXXXXXXXX
Show constraints on table %.TAB_XXXXXXXXXX...
OWNER TABLE_NAME CONSTRAINT_NAME C POSITION STATUS VALIDATED
--------- ------------------- ------------------------------ - ---------- -------- -------------
WEEJAR TAB_XXXXXXXXXX SYS_C00207433 C ENABLED NOT VALIDATED
WEEJAR TAB_XXXXXXXXXX PK_TAB_XXXXXXXXXX P 1 ENABLED NOT VALIDATED
To force OGG to use those keys in Extract/Replicat/GGSCI , the GLOBALS parameter ALLOWNONVALIDATEDKEYS may be used. In order to use this approach the PK or Key must be ENABLED. If the PK or Key is not enabled, OGG will still use all columns to uniquely identify the row.
Solution
Either solution should allow you to resume normal functionality;
– Set constraint to ENABLE, VALIDATE or
– Add the ALLOWNOVALIDATEKEYS parameter to your globals and restart the manager.
GGSCI (system) 1> view params ./GLOBALS
MGRSERVNAME MGR_xxx
ALLOWNONVALIDATEDKEYS
对不起,这篇文章暂时关闭评论。