By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,610 Members | 1,677 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,610 IT Pros & Developers. It's quick & easy.

Triggers-Replication-unique key

P: n/a
I'm looking into triggers as a potential fix to a problem I'm having at
work. The basic situation is that we are using db2 replication, and if
something goes wrong, there is the chance that a unique key that lies
outside of the primary key. Anyhow to make a long story short, every
time this happens replication breaks and is then down and the problem
compounds until it is fixed. I'm currently looking at several
solutions, one that I think might work is triggers. I would write a
before insert trigger that looks at the database and sees if it is
going to violate the unique key constraint and if it is, write out a
log, send an email and then drop it on the floor. This is the part that
I'm not sure I can do. Is there a way for a DB2 to not process an
insert while not throwing an error as to break replication? Any help
will be greatly appreciated.


Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.