Shuts down Historical Server.
specifies whether termination should occur immediately or wait for active connections to close. Valid values are:
no_wait – causes Historical Server to shut down immediately and terminates any connections (including those performing playback) and active recording sessions. The active recording sessions and playback sessions that are creating new sessions are shut down in a controlled manner, which prevents corruption of the control file or any historical data files.
wait (the default) – defers shutdown until all active recording sessions (including those performing playback) complete and any other active connections are closed. No new connections are accepted during this time.
This example shuts down Historical Server immediately and terminates any connections and active recording sessions.
If you use the hs_shutdown command without the no_wait option and then want to cancel the request, you can send an interrupt to Historical Server to cancel the shutdown request. A DB-Library application calls the dbcancel() function and a CT-Library application calls the ct_cancel() function to cause such an the interrupt. The isql command generates one of these calls when you send it an interrupt signal, which usually is done by entering Ctrl+C at the keyboard.
You can request an immediate shutdown of Historical Server at any time by sending one of the following four signals:
Reception of one of these signals at any time (including while waiting for the hs_shutdown command to complete) is equivalent to issuing the hs_shutdown no_wait command.
WARNING! Sybase strongly recommends that you do not use the kill signal (SIGKILL) to shut down Historical Server. The kill signal does not permit any controlled cleanup to be done and may result in data loss.
If any active sessions were terminated during the shutdown, Historical Server writes information about the sessions to its log file. Active sessions are recording sessions or playback sessions in the process of creating a new recording session.
If a superuser was specified in the Historical Server start-up command, the only user who can shut down Historical Server is the superuser. If a superuser was not specified, any user can shut down Historical Server.
See Chapter 3, “Starting and Stopping Historical Server” for more information about stopping Historical Server.