The unmount command shuts down the database and drops it from the Adaptive Server. The devices are also deactivated and dropped. The database and its pages are not altered when they are unmounted. The database pages remain on the OS devices. Once the unmount command completes, you can disconnect and move the devices at the source Adaptive Server if necessary. Use the manifest_file extension to create the manifest file for use at the secondary Adaptive Server.
The unmount command limits the number of databases to eight in a single command.
WARNING! The unmount command removes a database and all its information from the Adaptive Server. Use the unmount command only when you want to remove the database from one Adaptive Server to another Adaptive Server.
unmount database <dbname list> to <manifest_file>
the database being unmounted. You can unmount more than one database.
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 and self-contained on those devices.
Since the manifest file is a binary file, operations that perform character translations of the file contents (such as ftp) will corrupt the file unless done in binary mode.
unmount databases from an Adaptive Server and create the manifest file for the database:
unmount database pubs2 to "/work2/Devices/Mpubs2_file"
You cannot:
Unmount system databases. However, you can unmount sybsystemprocs.
Unmount proxy databases or user created temporary databases.
Use the unmount command in a transaction.
Unmount a database on an HA-configured server.
ANSI SQL – Compliance level: Entry-level compliant.
Commands mount, quiesce database
