Each HotStandby operation generates an event. To monitor these events you can use an application, such as a watchdog application.
Events are objects with a name that signal that a specific action occurred in the server. Special statements in stored procedures are required to receive events. HotStandby events are no different from other events created and supported by solidDB. They are sent to those users who are registered to receive the event in a stored procedure. For details on posting, registering, and waiting for events, see Events.
The is a list of the events that are currently available for HotStandby. Most events include five parameters, but not all of those parameters are necessarily used.
Unless otherwise specified, the system events have the same five parameters, see SQL: System events.
SYS_EVENT_HSBCONNECTSTATUS
Change in connect status between the primary and secondary server.
For TEXTDATA, the possible valid values are:
▪ CONNECTED
▪ CONNECTING
▪ CATCHUP
▪ BROKEN
SYS_EVENT_HSBSTATESWITCH
Each state switch sends a state switch event.
For TEXTDATA, the possible valid values are:
▪ PRIMARY ACTIVE
▪ PRIMARY ALONE
▪ PRIMARY UNCERTAIN
▪ SECONDARY ACTIVE
▪ SECONDARY ALONE
▪ STANDALONE
SYS_EVENT_NETCOPYEND
HotStandby NETCOPY operation ended.
This event can be caught by the user only if the user is using Shared Memory Access (SMA) or Linked Library Access (LLA).
None of the parameters are used.
SYS_EVENT_NETCOPYREQ
A HotStandby NETCOPY was requested.
If the user application callback function returns non-zero, then netcopy is not performed.
This event can be caught by the user only if the user is using SMA or LLA.