Database Mount and Unmount

Use the mount and unmount commands to perform a number of tasks.

More easily package proprietary databases; for example, as data files instead of as SQL scripts. The associated actions necessary for running these SQL scripts, such as device and database setup, are eliminated.
Move a database – when you move a set of databases from a source SAP ASE to a destination SAP ASE, you are physically moving the underlying devices.
Copy databases without a shutting down SAP ASE. When you copy a database from the command line, you must operate outside of SAP ASE, and use commands like the UNIX dd or ftp to create a byte-for-byte copy of all pages in a set of one or more databases.

Run mount and unmount from the isql prompt: the primary SAP ASE is the source, and the secondary SAP ASE is the destination. quiesce database also allows a single secondary SAP ASE to act as standby for databases from multiple primaries, since databases from multiple sources can be copied to a single destination.

Note: mount database and unmount database are supported in the Cluster Edition. These commands may be aborted if an instance failover recovery takes place while you are using these commands. In this case, the user must re-issue the command when the instance failover recovery is complete.

Use unmount to remove a database and its devices from a server. A manifest file is created for the database at a location you specify in the command clauses. The manifest file contains information pertinent to the database at the source SAP ASE, such as database devices, server information, and database information.
Copy or move the database onto the destination SAP ASE.
Use mount to add the devices, attributes, and so on for the database.
Use database online to bring the database up on the destination SAP ASE without restarting the server.

See the Reference Manual: Commands for complete documentation of mount and unmount database.

Warning! For every login that is allowed access to a database on the original SAP ASE, a corresponding login for the same suid must exist at the destination SAP ASE.

For permissions to remain unchanged, the login maps at the destination SAP ASE must be identical to those on the source SAP ASE.

Manifest File
The manifest file is a binary file that contains information about the database, such as database devices, server information, and database information.
Operations That Copy and Move Databases
Moving or copying operations occur at the database level, and require activity external to SAP ASE. To move or copy devices and databases, be sure that they are set up on the source SAP ASE using units that support a physical transportation.
Performance Considerations
Database IDs for the transported databases must be the same on the destination SAP ASE unless you are mounting the database for temporary usage, in which case you must run checkalloc to fix the database ID.
Device Verification
The destination SAP ASE verifies the devices in the manifest file by scanning the device allocation boundaries for each database.
Mounting and Unmounting Databases
The quiesce database command includes a clause that facilitates the mount and unmount commands.

Related concepts

Manifest File