Quick Beginnings

Migrating Instances

This procedure describes how to migrate DB2 instances that were created using a previous version of a DB2 product.

Before you can migrate an instance to use the latest version of DB2, you must install DB2 Version 5 on your system.

If there are several DB2 instances using previous versions of DB2 products, 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 products.

Each DB2 instance must be migrated separately. To successfully migrate a DB2 instance, you need to perform the following steps:

• Prepare the DB2 instance for migration.

• Verify that databases can be migrated. This step is optional. However, we recommend that you perform this step before migrating an instance.

• Migrate the DB2 instance.

Prepare the DB2 Instance for Migration

Before you can migrate a DB2 instance, all applications using any databases, owned by this instance, must be completed or terminated. To prepare a DB2 instance for migration, you need to perform the following steps:

1. Log in as the DB2 instance.

2. Ensure that there are no applications using any databases owned by this DB2 instance.

   • You can get the list of all applications using databases owned by the instance using the following command:

        db2 list applications
     

   • You can force termination of all applications using the following command:

        db2 force applications all
     

     Note:

     It is not recommended to force termination of applications. Some applications may have unexpected behavior when terminated using this command.

     For usage and details of this command, refer to your current release Command Reference.

   • Get a list of applications again to ensure that all applications have terminated, using the following command:

        db2 list applications
     

3. Stop all database server processes owned by the DB2 instance by issuing the db2stop command.

4. Stop the DB2 license daemon by issuing the db2licd end command.

5. Stop all command line processor sessions by issuing a db2 terminate command in each session that was running the command line processor.

   The DB2 instance is now ready for migration.

6. Log out as the DB2 instance.

Migration Considerations for the User Exit Program

Follow these instructions if you are using the user exit program, db2uexit, with previous versions of DB2.

DB2 Version 5 has changed the interface it uses to invoke the user exit program to archive and retrieve log files. These new interfaces are documented in the Administration Guide . The name for the user exit program has changed to db2uext2 in Version 5; in previous versions, it was called db2uexit.

The following should be considered before migrating instances:

• If the pre-version 5 db2uexit is installed in the INSTHOME/sqllib/adm directory before migration, it will remain in this directory after migration. The Version 5 db2uext2 program will be also installed in this directory. Its function is to invoke db2uexit using the pre-version 5 interface. This allows the old user exit program to be used on Version 5.

• If db2uexit is installed in a directory other than INSTHOME/sqllib/adm, it will not be installed after migration. For example, if db2uexit was in the INSTHOME/sqllib/bin directory, after migration the db2uexit file will not be in the INSTHOME/sqllib/bin directory. If you want to continue using the old user exit, following migration, you must copy db2uexit to INSTHOME/sqllib/adm directory. Then, you can do one of the following:

  • If you are migrating from DB2 Version 2 or DB2/6000 Version 1, copy db2uext2.v2 from DB2DIR/misc directory to INSTHOME/sqllib/adm directory and rename it to db2uext2. You can use the following command to copy the file:

       cp DB2DIR/misc/db2uext.v2 INSTHOME/sqllib/adm/db2uext2
    

    
    

    where	DB2DIR	= /usr/lpp/db2_05_00	on AIX
    		= /opt/IBMdb2/V5.0	on HP-UX or Solaris

  • If you are migrating from DB2 PE Version 1, copy db2uext2.pe from DB2DIR/misc to INSTHOME/sqllib/adm and rename it to db2uext2. You can use the following command to copy the file:

       cp DB2DIR/misc/db2uext.pe INSTHOME/sqllib/adm/db2uext2
    

    
    

    where	DB2DIR	= /usr/lpp/db2_05_00	on AIX
    		= /opt/IBMdb2/V5.0	on HP-UX or Solaris

  Note:

  You must ensure that db2uext2 is owned by the instance owner and is executable by the owner.

At a convenient time, you should modify your user exit program to use the new Version 5 interfaces. The new user exit program should replace db2uext2 in the INSTHOME/sqllib/bin orsqllib\bin directory, used to support the pre-version 5 user exit program, db2uexit, which should be removed.

Migrate the DB2 Instance

After an instance is ready for migration, use the db2imigr command to migrate the instance. You need to perform the following steps:

1. Log in as root.

2. Run the db2imigr command as follows:

      DB2DIR/instance/db2imigr [-d] [-a AuthType] [-u fencedID] InstName
   

   
   

   where	DB2DIR	= /usr/lpp/db2_05_00	on AIX
   		= /opt/IBMdb2/V5.0	on HP-UX or Solaris

   and where:

   -d

   Sets the debug mode that you can use for problem determination

   -a AuthType

   Is an optional parameter that specifies the authentication for the instance. Valid authentication types are SERVER, CLIENT, and DCS. If the -a parameter is not specified, the authentication type defaults to SERVER, if a server product is installed. Otherwise, the AuthType is set to CLIENT.

   Notes:

   1. The authentication type of the instance applies to all databases owned by the instance.

   2. Authentication type, DCE, is valid. However, it is not valid to choose DCE as an AuthType for this command. To enable DCE authentication for a DB2 instance, refer to the Administration Guide.

   -u fencedID

   Is the user under which the fenced user-defined functions (UDFs) and Stored Procedures will execute.

   InstName

   Is the login name of the instance owner.

[ DB2 List of Books | Search the DB2 Books ]