Alternative to dump and load for Adaptive Server 12.5.1

If you are upgrading from Adaptive Server 12.5.1 or later and plan to build a new server instead of upgrading an existing server, the following steps are faster alternative to dumping and loading the database. This method is fastest if you are using storage area network (SAN) technology, even if you are migrating to new hardware at the same time. The server you are building must have access to (or copies of) the physical devices of the old server, and the databases must be aligned with the devices. If a device contains fragments of more than one database, you may have to move or upgrade all the databases at the same time.

  1. Either quiesce the 12.5.x database to a manifest file during testing, or unmount the database from the server.

  2. If the 15.0 Adaptive Server is on another host, unmount the disk devices from the current host and mount them to the new host machine or copy the devices using SAN utilities.

  3. Copy the manifest file to the new Adaptive Server 15.0 location.

  4. Mount the 12.5.x database to the Adaptive Server 15.0 server using the manifest file. You may need to rewrite the new device paths for the server location.

  5. Issue the online database command. The database upgrade begins when you bring the database online.

Example

The following example assumes that you are upgrading the testdb database using a manifest file named testdb_manifest.mfst.

  1. Quiesce the 12.5.x database:

    quiesce database for_upgrd hold testdb
    for external dump
    to "/opt/sybase/testdb_manifest.mfst"
    with override
    
  2. Copy the devices using disk copy commands (for example, dd), SAN utilities, or standard file system command.

  3. When the device copy is finished, release the quiesce:

    quiesce database for_upgrd release
    
  4. If this is the final upgrade for this server (as opposed to a server for testing), shut down the server to prevent further changes.

  5. Move the device copies to the new host machine and mount them as appropriate.

  6. In the 15.0 server, issue the following to list the physical-to-logical device mappings:

    mount database all from "/opt/sybase/testdb_manifest.mfst" with listonly
    
  7. Use the results from step 6 to determine the new physical device mappings that correspond to the logical devices and mount the database in the 15.0 Adaptive Server:

    mount database all from "/opt/sybase/testdb_manifest.mfst" using
    	"/opt/sybase/syb15/data/GALAXY/test_data.dat" = "test_data",
    	"/opt/sybase/syb15/data/GALAXY/test_log.dat" = "test_log"
    
  8. Bring the database online and start the upgrade process:

    online database testdb