External control is required to start up and shut down Source and Receiver Servers. At shutdown, a Source Server in the active mode performs the following:
Flushes the dirty database cache buffers of all replicated regions
Transmits as many pending updates as possible to the Receiver Server within the specified time limit
Deletes the Journal Pool
Breaks the connection with the Receiver Server
Exits
An active Source Server becomes passive when deactivated. It flushes the database cache buffers of all the replicated regions and then "goes to sleep." At shutdown, a Source Server in passive mode flushes the database cache buffers of all the replicated regions and exits.
|
|
|
Under normal operation, the Source Server should be shut down only after all M processes accessing the replicated regions have terminated. |
At shutdown, the Receiver Server sets a flag in the Receive Pool that signals the Update Process to shut down. When this flag is set, the Update Process flushes the database cache buffers of all replicated regions, sets a flag in the Receive Pool to inform the Receiver Server that the task is complete, and exits. Next, the Receiver Server confirms that the Update Process has exited, deletes the Receive Pool, breaks the connection with the Source Server, and exits.
An optional time-out parameter can specify the time to wait before signaling the Source or the Receiver Server to shutdown. An interface allows you to stop or start the Update Process independently of the Receiver Server. Refer to "Starting the Source Server." In case of a normal shutdown, the Update Process notifies the Receiver Server, which distinguishes this type of shutdown from a forced termination.