Mounting a Database

Use the mount command to attach the database to the destination or secondary SAP ASE.

The mount command decodes the information in the manifest file and makes the set of databases available online. All the required supporting activities are executed, including adding database devices, if necessary, and activating them, creating the catalog entries for the new databases, recovering them, and putting them online.

The mount command limits the number of databases to eight in a single command.

Graphic showing a server connected to one device. After you run a mount command, the server is connected to two devices, and there is an entry in the manifest file describing the event.

See mount in the Reference Manual: Commands.

Note: mount allows you to identify more than one database for a move operation. However, if a device is used for more than one database, then all of the databases must be moved in one operation. You specify the set of databases being transported. The devices used by these databases cannot be shared with any extraneous database besides the ones specified in the command.

You can use the mount command in different ways:

Use the mount command at the destination SAP ASE. For example:
```
mount database all from "/data/new_user2/mfile1" 
using "/data/new_user1/d0.dbs" = "1dev1"
```
The databases and their devices appear at the destination SAP ASE, marked as in-mount. The system is populated with updates to system catalogs and appropriate information about the databases, but the databases themselves are unrecovered. They do, however, survive a system failure.

The destination SAP ASE then recovers the databases one at a time. The databases remain offline after recovery.

If a recovery fails on a database, it affects only that database. The recovery continues for the other databases.

Use the command database online to bring the databases online.

You need not restart the destination server.
Use the mount command with listonly to display the path names in the manifest file from the source SAP ASE without mounting the database.
Before mounting the databases, use listonly parameter to list the device path names at the destination SAP ASE. For example:
```
mount database all from "/data/new_user2/mfile1" with listonly

/data/new_user1/d0.dbs = ldev1
```
Then use mount to actually mount the databases. Once you have the path names, verify or modify them to meet your criteria at the destination SAP ASE.

When you mount databases onto an SAP ASE:

You cannot mount a subset of the databases described in the manifest. All the databases and devices present in the manifest must be mounted together.
The databases being mounted must have the same page size as the previous SAP ASE.
There must be enough devices configured on the secondary SAP ASE for the successful addition of all the devices belonging to the mounted databases.
The configuration parameter number of devices must be set appropriately.
Database names and devices with the same names as the mounted database must not already exist.
SAP ASE must have the same version as the mounted database.
The mounted database must be from the same platform as the SAP ASE.

To create a mountable version of a database:

Use the quiesce database command with the manifest clause and quiesce the database. This command creates a manifest file describing the database.
Use the mount command with listonly to display the list of devices to be copied.
Use external copy utilities, such as cp, dd, split mirror, and so on, to copy the database devices to another SAP ASE.The copy of the devices and the manifest file is a mountable copy of the database.