Quick Beginnings

Migrating from Previous Versions of DB2

If you are migrating from Version 5.0 or Version 5.2 to DB2 Version 7, you must prepare your databases and instances before installing DB2 Version 7. If you are upgrading from Version 6, there is nothing you have to do prior to installing Version 7.

The migration of pre-Version 5.0 databases and instances is not supported in DB2 Version 7.

If you are migrating a DB2 installation on a workstation that is running on a supported Linux distribution, you should be aware of the following:

The migration of DB2 Version 5.2 Beta is not supported.
DB2 Version 7 can only run with glibc version 2.1.2 or higher, as mentioned in Software Requirements. If your Linux distribution has a previous version of this library, you will not be able to use your DB2 product.
To prepare your workstation for installation, you have to upgrade your existing Linux distribution to a more recent level that includes the required (or later) version of the glibc library. You also have the option to update only the local version of the glibc library. We recommend that you update your distribution's installation to a more recent version that includes the required level for the glibc library. Updating just the glibc library without updating your distribution's installation version is not recommended as errors during this process can affect your operating system.

Preparing Databases and Instances for Migration

This section describes how to prepare existing DB2 Version 5.x databases and instances for migration to a format usable by DB2 Version 7. If you want to migrate more than one instance, you must repeat these steps for each instance.

If there are several DB2 instances using previous versions of DB2, you do not need to migrate all of these instances at this time. Instances that are not migrated will continue to use previous versions of DB2.

You must be logged in as the instance owner to complete these steps.

To prepare your databases for migration:

Ensure that there are no applications using any databases owned by the DB2 instance you are preparing to migrate. To get a list of all applications owned by the instance, enter the db2 list applications command. If all applications are disconnected, this command will return the following message:
```
   SQL1611W No data was returned by the Database System Monitor.
   SQLSTATE=00000
```
You can end a session by entering the db2 terminate command.
Ensure that all databases are cataloged. To view a list of all the cataloged databases in the current instance, enter the following command:
```
   db2 list database directory
```
Make a backup copy of all Version 5.x databases. You do not have to back up Version 6 databases. Refer to the Administration Guide for your DB2 product for information on making a backup copy of a database and to the Command Reference for the syntax of the backup command.
When all applications are complete and you have backed up your databases, stop all database server processes owned by the DB2 instance by entering the db2stop command.
Stop the DB2 license daemon by entering the db2licd -end command.
Stop all command line processor sessions by entering the db2 terminate command in each session that was running the command line processor.
Ensure that the db2profile (bash, Bourne, or Korn shells) or db2cshrc (C shell) instance environment setup script, under the instance's INSTHOME/sqllib/ directory, is of the proper shell syntax.
If necessary, ensure that each export statement is separated into different lines. For example:
```
   DB2INSTANCE=db2inst1       //bash, Bourne, or Korn shells
   export DB2INSTANCE
 
   set DB2INSTANCE=db2inst1   //C shell
```

[ Top of Page | Previous Page | Next Page ]