I keep finding nasty bugs in DB2 DataJoiner Replication Administration. (DJRA, which does not require any part of DataJoiner which isn't included in UDB, for DB2 to DB2 replication at least. See http://www-4.ibm.com/software/data/dpropr/downloads.html for the latest version.) When I add multiple tables to a subscription set DJRA misidentifies the primary key on tables that have unique fields outside of the primary key. To check this, try (on the control server) select count(*) from asn.ibmsnap_subs_cols as A, syscat.columns as S where A.target_table = S.tabname and A.target_owner = S.tabschema and A.target_name = S.colname and A.is_key = 'Y' and (S.keyseq = 0 or S.keyseq is null) And if that total is greater than zero, I'd suggest trying: update asn.ibmsnap_subs_cols as A set is_key = 'N' where is_key ='Y' and exists ( select * from syscat.columns as S where A.target_table = S.tabname and A.target_owner = S.tabschema and A.target_name = S.colname and (S.keyseq = 0 or S.keyseq is null) ) -HJC P.S. Yes, I know exists(select *) sucks big time on UDB, so sue me. P.P.S.: Now if only I could get it to transverse the foreign keys in the correct order so it didn't run into quite so many relational bombs... ===== To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
