Shareplex picks up wrong column as the key.
For Example
The object cache shows that key columns are COL1, COL2 and COL3
"XXXX"."ABCD"
340604
Type: TABLE
Key Type: Primary key Number of key columns: 3
Number of columns: 185
Status: In Replication
--------------------------------------------------------------------------------
Col |Length| Type | Name | Column info
1 23 VARCHAR2 COL1 Key
2 5 VARCHAR2 COL2 Key
3 20 VARCHAR2 COL3 Key
4 1 VARCHAR2 COL4
5 20 VARCHAR2 COL5
..........
Whereas the primary key has only two columns:
SQL> select column_name, position from dba_cons_columns where constraint_name='ABCD_PK' and table_name='ABCD';
COLUMN_NAME POSITION
----------------------- ----------------
COL1 1
COL2 2
SharePlex internal queries return incorrect values.
WORKROUND:
Edit the config file and specify the keys that should be used for that table, this will force shareplex to use the columns in the config file as the key columns.
The general syntax for key definition is:
< owner>.<source_table_name> !key (col_name1, col_name2) < owner>.<target_table_name> <target_host>@o.<target_sid>
Waiting for fix in a future release. ETA has not been determined of Q1 2012.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy