The advanced replication or synchronization events enable programs to be notified when certain advanced replication related actions occur. You can use these events to monitor the progress of synchronization between master and replica databases.
These events follow most of the same rules as any other events. The main difference is that you cannot register to synchronization events, because the ADMIN EVENT 'wait' command is not able to return variable resultsets. Instead, you must use stored procedures to handle synchronization events.
For information about events in general, see the solidDB® SQL Guide, especially the sections on:
▪CREATE EVENT command
▪CREATE PROCEDURE command, which describes how to post events and wait on events
The synchronization events are predefined; you do not create them. Furthermore, you should not post any system event. You should only register for and wait on system events.
Most system events have the same five parameters:
▪ename: The event name.
▪postsrvtime: The time that the server posted the event.
▪uid: The user ID (if applicable).
▪numdatainfo: Miscellaneous numeric data — the exact meaning depends upon the event. For example, the event SYS_EVENT_BACKUP is posted both when a backup is started and when a backup is completed. The value in the numdatainfo parameter indicates which case applies — that is, whether the backup has just started or has just completed. This parameter can be NULL if there is no numeric data.
▪textdata: Miscellaneous text data — the exact meaning depends upon the event. This parameter can be NULL if there is no numeric data.