shutdown

Description

Shuts down the Adaptive Server from which the command is issued, its local Backup Server, or a remote Backup Server.

Syntax

shutdown [srvname] [with {wait [="hh:mm:ss"] | nowait}]]

Syntax for clusters:

shutdown {cluster | [instance_name]} [with {wait | nowait}]

Parameters

Examples

Example 1

Shuts down the Adaptive Server from which the shutdown command is issued:

shutdown

Example 2

Shuts down the Adaptive Server immediately:

shutdown with nowait

Example 3

Shuts down the local Backup Server:

shutdown SYB_BACKUP

Example 4

Shuts down the remote Backup Server REM_BACKUP:

shutdown REM_BACKUP

Example 5

Shuts down the current cluster:

shutdown cluster

Example 6

Shuts down the instance “ase1”, but leaves the cluster running:

shutdown ase1

Usage

• Unless you use the nowait option, shutdown attempts to bring Adaptive Server down gracefully by:

  • Disabling logins (except for the system administrator)

  • Performing a checkpoint in every database

  • Waiting for currently executing SQL statements or stored procedures to finish

  Attempting a normal shutdown on a dataserver does not terminate batches of SQL that include infinite looping and Transact-SQL that include waitfor delay commands.

  Shutting down the server without the nowait option minimizes the amount of work that must be done by the automatic recovery process.

  A graceful shutdown waits for the currently executing statement to complete, under the assumption that many statements will be atomic transactions that will commit on completion. However, a graceful shutdown does not wait for a longer transaction to commit if the session would go into “awaiting command” state within a transaction. Instead, shutdown commences and the transaction rolls back on recovery.

  Sybase recommends that you check the master..syslogshold table for any long-running open transaction and deal with it before you issue a shutdown. You may deal with such transactions by contacting the users running them to see they can commit the transactions, or kill them and wait for a rollback. Rolling back an active transaction is faster before a shutdown rather than after recovery, as many pages may still be in cache, and there is less scanning of the log involved. If there are multiple long-running transaction, check syslogshold repeatedly until you see no very old transactions.

  Shutting down with a long-running open transaction on the server can result in a lengthy recovery time.

• Unless you use the nowait option, shutdown backup_server waits for active dumps and loads to complete. Once you issue a shutdown command to a Backup Server, no new dumps or loads that use this Backup Server can start.

• You can halt only the local Adaptive Server with shutdown; you cannot halt a remote Adaptive Server.

• You can halt a Backup Server only if:

  • It is listed in your sysservers table. Use sp_addserver to add entries to sysservers.

  • It is listed in the interfaces file for the Adaptive Server where you execute the command.

• Use sp_helpserver to determine the name by which a Backup Server is known to the Adaptive Server. Specify the Backup Server’s name— not its network_name—as the srvname parameter. For example:

  sp_helpserver
  

  name        network_name   status                             id 
  ----------  -------------  ------------------------------------ --
  REM_BACKUP  WHALE_BACKUP   timeouts, no net password encryption 3
  SYB_BACKUP  SLUG_BACKUP    timeouts, net password encryption    1 
  eel         eel                                                 0 
  whale       whale          timeouts, no net password encryption 2 
  
  

  To shut down the remote Backup Server named WHALE_BACKUP, use:

  shutdown REM_BACKUP
  

When the server prepares to down, it:

• The shutdown command with no options is invalid in a clustered environment, as for example:

shutdown
go

Standards

ANSI SQL – Compliance level: Transact-SQL extension.

Permissions

The permission checks for shutdown differ based on your granular permissions settings.

Auditing

Values in event and extrainfo columns of sysaudits are:

See also