Collection Contents Previous Next PDF

ASA Database Administration Guide

Database Administration Utilities

The Stop utility

Stopping a database server using the dbstop command-line utility


Syntax 

dbstop [ options ]

Option Description
server-name Name of a local database server to stop.
–c "keyword=value; ..." Connection parameters
–d Stop specified database only.
–o filename Log output messages to a file
–q Quiet mode—do not print messages
–x Do not stop if there are active connections
–y Stop without prompting even if there are active connections
Description 

Options let you control whether a server is stopped, even if there are active connections, and whether to stop a server or only a database.

Exit codes are 0 (success) or non-zero (failure).

The Stop [dbstop] utility is not available on NetWare.

For more information about the Stop utility options, see Stop utility options.

This utility accepts @filename parameters.

For more information, see @filename server option.

Stop utility options 

Server-name    The name of a database server running on the current machine. The database server must be started so that no permissions are required to shut it down. The personal database server starts in this mode by default. For the network database server, you must supply the –gk all option.

If you supply a server name, do not supply connection parameters as well.

For more information, see -gk server option.

Connection parameters (–c)    When stopping a network server, you must supply a connection string with a user ID that has permissions to stop the server. By default, DBA permission is required on the network server, and all users can shut down a personal server, but the –gk server option can be used to change this.

The behavior of dbstop can be controlled if there are active connections on a server. If there are active connections, dbstop provides a prompt asking if you wish to shut down the server. If you specify unconditional=true, the server is shut down without prompting, even if there are active connections.

If you supply connection parameters, do not supply a server name as well.

For more information, see Connection parameters, Unconditional connection parameter [UNC], and -gk server option.

Stop database only (–d)    Do not stop the database server. Instead, only stop the database specified in the connection string.

Log output messages to file (–o)    Write output messages to the named file.

Operate quietly (–q)    Do not print a message if the database was not running.

Do not stop if there are active connections (–x)    Do not stop the server if there are still active connections to the server.

Stop without prompting (–y)    Stop the server even if there are still active connections to the server.

Examples 

Collection Contents Previous Next PDF