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

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

• quiesce database used with the hold keyword suspends all updates to the specified database. Transactions cannot update data in suspended databases, and background tasks such as the checkpoint process and housekeeper process skip all databases that are in the suspended state.

• quiesce database used with the release keyword allows updates to resume on databases that were previously suspended.

• quiesce database used with the for external dump clause signifies that you intend to make an external copy of the database.

• Recovery for this database may fail or the database may not be consistent If you:

  • Quiesce a reduced-durability database (including tempdb)

  • Copy the device

  • Mount this database on another Adaptive Server

  Change a database’s durability with alter database before you issue a quiesce database command.

• The quiesce database hold and release commands need not be executed from the same user session.

• If the databases specified in the quiesce database hold command contain distributed or multidatabase transactions that are in the prepared state, Adaptive Server waits during a timeout period for those transactions to complete. If the transactions do not complete during the timeout period, quiesce database hold fails.

• If Adaptive Server is executing a dump database or dump transaction command on a database specified in quiesce database hold, the database is suspended only after the dump command completes.

• If you execute a dump database or dump transaction command on a database while updates to the database are suspended, Adaptive Server blocks those commands until the database is released with quiesce database release.

• If you attempt to run a query against a database that is quisced, Adaptive Server issues error message 880:

  Your query is blocked because it tried to write and
  database '%.*s' is in quiesce state. Your query will
  proceed after the DBA performs QUIESCE DATABASE
  RELEASE
  

  The query is run once the database is no longer in a quiescent state.

• To duplicate or copy databases, use quiesce database with the extension for creating the manifest file. The quiesce database effects the quiesce hold by blocking writes in the database, and then creates the manifest file. The command then returns control of the database to the user. You can now use a utility to copy the database to another Adaptive Server. These rules for quiesce database hold must be followed for the copy operation:

  • The copy operation cannot begin until the quiesce database hold process has completed.

  • Every device for every database in the quiesce database command must be copied.

  • The copy process must complete before you invoke quiesce database release.

• You can use quiesce database when the database contains an encryption key.

• You must use with override to quiesce a database whose columns are encrypted with keys stored in other databases.

• quiesce database key_db, col_db is allowed where key_db is the database with the encryption key and col_db is the database with a table that has a column encrypted with the key in key_db.

• If you issue shutdown instance or shutdown cluster, the cluster aborts all quiesce database commands.

• The cluster rejects all quiescedb commands issued by a user if shutdown instance or shutdown cluster commands are in progress.

• The cluster aborts all quiesce database commands if instance failover recovery is in progress.

• The cluster rejects all quiesce database commands issued by a user if instance failover recovery is in progress.

• You cannot add a new instance to the cluster while the master database is part of an ongoing quiesce database hold command.

Permissions

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

Auditing

Values in event and extrainfo columns of sysaudits are:

See also