Trigger and replication
Posted in 2008
Topics: Server Administration, Triggers, Constraints & Referential Integrity, Platform-Specific Issues, Versions, Editions & End-of-Life
Hi !
Are using IDS 10.00.FC8 on HP-UX.
I have the following scenario:
On server A a table is replicated using ER to server B
On server B there is a trigger on the table that updates a table on
server C.
An update of the table on server A is replicated to the table on
server B, and the update is done on server C using the trigger (and a
synonym), this works fine.
The problem is that there is another replicate on server C to server
D, this replication does not work. Replication between A and B works
fine and C and D also.
If the change on the table in server B is done using dbaccess it works
fine, the trigger fires and the table on B,C and D are updated. If the
update is done on server A it does not.
(--firetrigger is declared on both replicates.)
It seems that an update caused by a trigger fired by an replicate
cannot be replicated.
Anybody have a solution to this problem ?
Regards
Ulf
In article <a8fa7d45-1484-4d8f-a2c2-e06ffd95314f@k30g2000hse.googlegroups.com>, Ulf says... > > >Hi ! > >Are using IDS 10.00.FC8 on HP-UX. > >I have the following scenario: > >On server A a table is replicated using ER to server B ... snipped. I believe ER determines whether the change to the table has come from the user or via trigger and does not replicate if the change has come via trigger. The assumption is that on both source and target machines, if the user wants, the same trigger should be defined to take care of trigger updates locally. Of course Madison can give a better explanation.