quiesce database

Description

Suspends and resumes updates to a specified list of databases.

Syntax

quiesce database tag_name hold database_list [for external dump] 
	[to manifest_file [with override]]

or:

quiesce database tag_name release

Parameters

tag_name

is a user-defined name that designates the list of databases to hold or release. The tag_name must conform to the rules for identifiers.

hold

when used with to manifest_file clause, holds the database and creates a manifest file.

WARNING! Since the manifest file is binary, operations that perform character translations of the file contents (such as ftp) corrupt the file unless performed in binary mode.

database_list

is the list of the databases included in the quiesce database hold command.

for external dump

specifies that while updates to the databases in the list are suspended, you will physically copy all affected database devices, using some facility external to Adaptive Server. The copy operation serves as a replacement for the combination of dump database and load database.

manifest_file

the binary file that describes the databases that are present on a set of database devices. It can be created only if the set of databases that occupy those devices are isolated, self-contained on those devices.

Since the manifest file is a binary file, operations that can perform character translations of the file contents (such as ftp) will corrupt the file unless performed in binary mode.

with override

overrides any restrictions that prevent you from successfully executing quiesce database on a database.

Examples

Example 1

Suspends update activity on salesdb and ordersdb:

quiesce database report_dbs hold salesdb, ordersdb 

Example 2

Resumes update activity on the databases labeled report_dbs:

quiesce database report_dbs release

Example 3

Suspends update activity to the pubs2 database and signifies your intent to make an external copy of this database:

quiesce database pubs_tag hold pubs2 for external dump

Example 4

Places the database in a hold status and builds the manifest file for a database to be copied to another Adaptive Server:

quiesce database pubs_tag hold pubs2 for external dump to 
    "/work2/sybase1/mpubs_file with override

Once the command completes, control returns to the user.

Example 5

Copies the database devices, using the mount database with listonly to list all of the devices to be copied to view:

1> mount database all from "/data/sybase2/mfile1" with listonly
2> go
"/data/sybase1/d0.dbs" = "1dev1"

You cannot create a manifest file if the set of databases that are quiesced contain references to databases outside of the set. Use with override option to bypass this restriction:

quiesce database pubs2_tag release for external dump to Mpubs_file

Example 6

These succeed where key_db contains the encryption key used to encrypt columns in col_db:

quiesce database key_tag hold key_db for external
         dump to "/tmp/keydb.dat"

quiesce database encr_tag hold col_db for external dump       to "/tmp/col.dat" with override

quiesce database col_tag hold key_db, col_db for 
    external dump to "/tmp/col.dat"

Usage


Encrypted columns and quiesce database


quiesce database in a clustered environment

Permissions

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

Granular permissions enabled

With granular permissions enabled, you must be a user with quiesce any database privilege.

Granular permissions disabled

With granular permissions disabled, you must be a user with sa_role.

Auditing

Values in event and extrainfo columns of sysaudits are:

Event

Audit option

Command or access audited

Information in extrainfo

96

quiesce

quiesce database

  • Roles – current active roles

  • Keywords or options – NULL

  • Previous value – NULL

  • Current value – NULL

  • Other information – NULL

  • Proxy information – original login name, if a set proxy is in effect

See also

Commands dump database, dump transaction, mount, unmount

System procedures sp_helpdb, sp_who