dbstop Options

@filename

Read in options from the specified environment variable or configuration file.

server-name

Server name of a running server to stop. If you supply a server name, do not supply connection parameters as well.

-c "keyword=value; ..."

To stop a network server, supply a connection string with a user ID that has permissions to stop the server. By default, the SERVER OPERATOR system privilege is required on the network server, and all users can shut down a personal server; you can use the -gk server command-line option to change the default behavior.

See Administration: Database > Connection and Communication Parameters.

To stop a multiplex server, you need permissions to stop the server in the logical server context in which you connect to it. By default, dbstop logs in with SERVER context, so you would need permission to log into the SERVER logical server.

If there are active connections, dbstop prompts whether you want to shut down the server. If you specify unconditional=true on the command line, the server shuts down without prompting, even if there are active connections.

Avoid overriding the logical server in the connection string; if login redirection is enabled in the overriding user's login policy, the server may shut down as a connection is redirected.

-d

Does not stop the database server. Instead, only stops the database specified in the connection string.

-o filename

Logs output messages to the named file.

-q

Quiet mode—does not print messages.

-x

Does not stop if there are active connections. Including this option prevents dbstop from prompting for confirmation if there are active connections.

-y

Stops without prompting even if there are active connections.