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, execute mount with listonly:
mount database all from "/work2/Devices/Mpubs_file" with listonly "/work2/Devices/pubsdat.dat" = "pubs2dat"
Execute the quiesce database hold, then copy the database devices.
You cannot create a manifest file 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.
