Advanced Replication Guide : Synchronization events : Sequence of events
  
Sequence of events
The table below shows the sequence of events posted as the replica and master process a message that is sent from the replica to the master.
Note that some events do not always occur. For example, this sequence shows some places that the event SYNC_MASTER_MESSAGE_ERROR_OCCURRED may occur; however, the event does not always occur there.
Note also that in some cases the order of events may vary slightly. For example, the time that a master deletes an old message is partly independent of the activities of the replica (and vice-versa), and therefore may not always be done in exactly the order shown here.
Note Applications cannot monitor sync events unless they have administrator’s rights.
A separate section later gives more information about the parameters used in each of these synchronization-related events.
Action, command, or situation on Replica
EVENT Posted on Replica
Action or situation on Master
EVENT Posted on Master
Message Begin
 
 
 
Message Append
 
 
 
Message end / commit
When message is persistent (i.e. assembled and committed): SYNC_REPLICA_MESSAGE_ASSEMBLED
 
 
Message forward
When replica starts sending the message: SYNC_REPLICA_MESSAGE_FORWARD_BEGIN
When replica has finished sending the message to the master: SYNC_REPLICA_MESSAGE_FORWARD_END
 
 
 
 
Master starts receiving a message
When master starts receiving the message: SYNC_MASTER_MESSAGE_RECEIVE_BEGIN
 
 
Master has received a message
When master has received and made message persistent:
SYNC_MASTER_MESSAGE_RECEIVE_END
 
 
Master starts processing the message
SYNC_MASTER_MESSAGE_REPLY_BEGIN
 
 
Master processed the message
SYNC_MASTER_MESSAGE_REPLY_END
 
 
If an error occurred while processing the message.
SYNC_MASTER_MESSAGE_ERROR_OCCURRED
Message get reply
When replica sends get-reply request to master: SYNC_REPLICA_MESSAGE_GETREPLY
 
 
 
 
Master receives “get reply” request from replica
SYNC_MASTER_MESSAGE_GETREPLY_REQUEST
If “get reply” request timed out.
SYNC_REPLICA_MESSAGE_GETREPLY_TIMEDOUT
 
 
 
 
Master starts sending reply message
SYNC_MASTER_MESSAGE_SENDREPLY_BEGIN
Replica starts receiving the reply from the master.
SYNC_REPLICA_MESSAGE_REPLY_BEGIN
 
 
 
 
Master finishes sending reply.
SYNC_MASTER_MESSAGE_SENDREPLY_END
Reply received and made persistent
SYNC_REPLICA_MESSAGE_REPLY_END
 
 
 
 
Message is deleted
SYNC_MASTER_MESSAGE_DELETED. Note that the message also can be deleted explicitly using the MESSAGE DELETE statement.
Replica starts processing the reply.
SYNC_REPLICA_MESSAGE_PROCESS_BEGIN
 
 
If an error occurred while processing
SYNC_REPLICA_MESSAGE_ERROR_OCCURRED
 
 
Reply is processed
SYNC_REPLICA_MESSAGE_PROCESS_END
 
 
Message is deleted
SYNC_REPLICA_MESSAGE_DELETED. Note that the message also can be deleted explicitly using the MESSAGE DELETE statement.
 
 
See also
Synchronization events