shutdown

Syntax

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

Syntax for clusters:

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

Parameters

srvname – is the logical name by which the Backup Server is known in the SAP ASE sysservers system table. This parameter is not required when shutting down the local SAP ASE server.
with wait – is the default. This shuts down the SAP ASE server or Backup Server gracefully.
hh:mm:ss – is an optional setting that specifies the maximum time the server waits for all running or sleeping processes to finish their job.
with nowait – shuts down the SAP ASE server or Backup Server immediately, without waiting for currently executing statements to finish.
Warning! Use shutdown with nowait only in extreme circumstances. In the SAP ASE server, issue a checkpoint command before executing a shutdown with nowait. Use of shutdown with nowait can lead to gaps in IDENTITY column values.
cluster – (shared disk clusters only) specifies that all instances in the cluster are to shut down.
instance_name – (shared disk clusters only) is the name of a specific instance to shut down.

Examples

Example 1 – Shuts down the SAP ASE server from which the shutdown command is issued:
```
shutdown
```
Example 2 – Shuts down the SAP ASE 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 the SAP ASE 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
Note: 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 are be atomic transactions that 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.

You should 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.

Note: 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 SAP ASE server with shutdown; you cannot halt a remote SAP ASE 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 SAP ASE server where you execute the command.

Use sp_helpserver to determine the name by which a Backup Server is known to the SAP ASE 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

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

shutdown
go

See also sp_addserver, sp_helpserver in Reference Manual: Procedures.

Standards

ANSI SQL – Compliance level: Transact-SQL extension.

Permissions

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

Setting	Description
Enabled	With granular permissions enabled: To shutdown a SMP server, a cluster instance, or a backup server, you must be a user with `shutdown` privilege. To shutdown a cluster, you must be a user with `shutdown` privilege and `manage cluster` privilege.
Disabled	With granular permissions disabled, you must be a user with sa_role.

Auditing

Values in event and extrainfo columns of sysaudits are:

Information	Values
Event	51
Audit option	security
Command or access audited	Server shutdown
Information in `extrainfo`	Roles – current active roles Keywords or options – shutdown Previous value – NULL Current value – NULL Other information – NULL Proxy information – original login name, if set proxy is in effect