[CR# 424459] An update operation to a table with more than one unique index fails in Replication Server because the where clause contains no value. This problem is related to Oracle behavior as well as to supplemental data that is written to the Oracle redo logs. If a table has no primary key column defined but contains more than one unique constraint that is defined, Oracle records only one of the constraint column values in the redo log. The selection of which column will be logged is determined arbitrarily by Oracle.
Workaround: Mirror Replication Agent requires you to turn on supplemental logging in Oracle to ensure that primary key and unique index information is logged to the redo logs. To enable supplemental logging, enter this Oracle command:
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;
You can read about supplemental logging in Oracle documentationhttp://download-west.oracle.com/docs/cd/B10501_01/server.920/a96521/logminer.htm#25840
