You use the quiesce database hold command with the manifest clause to hold the database and create a manifest file.
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.
quiesce database < tag_name > hold < dbname list > [for external dump] [ to <manifest_file> [with override]]
For example:
Place the database in a hold status and build the manifest file:
quiesce database pubs2_tag hold pubs2 for external dump to "/work2/Devices/Mpubs_file"
This stops transactions against the database and creates the manifest file. To verify the devices within the manifest file, you can execute the mount with listonly:
mount database all from “/work2/Devices/Mpubs_file” with listonly “/work2/Devices/pubsdat.dat” = “pubs2dat”
You execute the quiesce database hold and then copy the database devices.
A manifest file cannot be created if the set of databases that are quiesced contain references to databases outside of the set. You may use the override option to bypass this restriction.
