Gopalan Venkatramani

I found the way to replicate the tables having secondary
indexes. Just drop the unique index on the target (apply) database.
Stop and start the q-replication program. Its working now
:)

I found it from pdf "Understanding and Using Q Replication for
High Availability Solutions on the IBM z/OS Platform"

Page : 157

"Unique key violation retries
Section 2.3.2, “The Q Apply oldest committed transaction time
for a queue” on
page 33 describes how secondary unique indexes can create unique
key
violations when Q Apply attempts to update a row in the target
table that contains
the same data for the (secondary) unique key columns.
The only meaningful method to avoid unique key violations is to
restrain from
adding more than one unique constraint on Q Replication maintained
(target)
tables. This is however not always possible, especially in
bidirectional replication
where the (target) site is also the (source) site where user
transactions rely on
the secondary unique indexes to enforce application logic."