Hi Justice, Please refer below in-line comments for your raised concerns. 1. for sequences, if the sequece has been created manually on the subscriber,does it stay in sync with the sequence on the publisher during synchronization? ie if the sequence's next value increment on the publisher will the sequence on the subscriber next value also change on the subscriber after synchronization? Do i have to create the sequence using the same name as >> Sequences (database objects created by the CREATE SEQUENCE statement) are not replicated from the publication database to the subscription databases in a single-master replication system. >> Sequence's next value increment on the publisher will not change on subscriber after synchronization. 2. I have noticed triggers to do not get copied across too, do I need to create the triggers manually as well.what happens to the triggers during synchronization? will the fire? my understanding is that they should not fire. >> Any change you want to see on the subscriber needs to be done on the publisher. All the changes made by triggers on the publisher will get replicated over to the subscriber. >> If triggers are created on subscriber and changes are made due to them, they are not propagated back to the publication. If changes are made to the subscription table rows, it is fairly likely that the rows will no longer match their publication counterparts. 3. Foreign keys do not get copied accross too? what must happen to the foreign keys ? When do i create them on the subscriber? >> Foreign key constraints are not replicated by the publication or subscription server in a single-master replication system. Go through 'Restrictions on Replicated Database Objects' for more details.
... View more
Hi Sushmita, Thanks for the update. Regarding the bind port and admin port, the bind port (7800) is for cluster, so other agents can communicate with each other on it. And the admin port (7809) is usedto communicate with local agent for commands like cluster-status . so, there is no need to open it for other nodes. Please let us know in case any further queries/issues. Regards, Sudhir
... View more