Changes in source/target database
Submitted by admin on Fri, 2006-04-28 10:55.
Q: Suppose my replication works and when I change the Database definition,
e.g., I add a field in one table. This new field won't be replicated,
the reason is it's not defined in the replicator. What must I do to work
with the new field?
A: It depends what field are to be changed/added. If a primary key field is to be changed you should first replicate all pending records to be REPL$LOG/MAN empty not till then change primary key using a DML SQL command. Next recreate triggers using IBReplMan "Group (S)/Drop triggers" and "Group (S)/Create system objects". Changed foreign key field does not require empty REPL$LOG but trigger recreation is necessary. Common field change does not require trigger recreation. Stop working with database when triggers are dropped.
A: It depends what field are to be changed/added. If a primary key field is to be changed you should first replicate all pending records to be REPL$LOG/MAN empty not till then change primary key using a DML SQL command. Next recreate triggers using IBReplMan "Group (S)/Drop triggers" and "Group (S)/Create system objects". Changed foreign key field does not require empty REPL$LOG but trigger recreation is necessary. Common field change does not require trigger recreation. Stop working with database when triggers are dropped.
