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 the quiesce database release.
quiesce database < tag_name > hold < dbname list > [for external dump] [to <manifest_file> [with override]]
Where:
tag_name
is a user-defined name that designates the list of databases to hold or release. tag_name must conform to the rules for identifiers.
dbname list
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
is the binary file that describes the databases included in the command. It can be created only if those databases are isolated and self-contained on their devices.
