Migrating from IBM DB2 ESE to IBM DB2 WSE

On Linux 32–bit operating system running on Intel platforms, IBM® DB2® Enterprise Server Edition (ESE) version 9.7 is not supported. On these platforms, Tivoli® Directory Server version 6.3 supports IBM DB2 Workgroup Server Edition (WSE) version 9.7. For users who want to migrate from previous versions of supported Tivoli Directory Server with DB2 8 ESE or 9.1 ESE to Tivoli Directory Server version 6.3 with DB2 WSE v9.7, do the following:

1. Install Tivoli Directory Server version 6.3 with DB2 WSE v9.7 on the system from which you want to migrate the previous Tivoli Directory Server instances.
2. Stop the directory server instance that you want to migrate.
3. Run the Tivoli Directory Serve v6.3's migbkup utility and take backup of the instance to be migrated. For example, run the migbkup utility with the following format:

   migbkup <instance_directory>/idsslapd-<instance_name>/<instance backup directory>

   To know more about migbkup, see IBM Tivoli Directory Server Version 6.3 Command Reference.
4. Backup the database of the directory server instance that is to be migrated using the DB2 commands. For example, if the directory instance to be migrated is inst1 and the database instance is inst1, then do the following:
   1. su - inst1
   2. sqllib/db2profile
   3. db2 backup database inst1 to <database backup directory>
   4. exit
   Note:
   If the change log database is configured for the directory server instance, the change log database also must be backed up.

   db2 backup db ldapclog to <changelog backup directory>

5. Drop the directory server instance, DB2 instance, and the database of inst1.
6. Run the Tivoli Directory Server v6.3's idsimigr command, and perform the migration using the instance backup directory. For example, run the idsimigr command of the following format:

   idsimigr -I inst1 -u <instance backup directory> -l <instance home directory> -n

   Note:
   Since the migration is being performed using the instance backup directory, it will take the remote migration path.
7. Configure the migrated instance. For example, run the idscfgdb command of the following format:

   idscfgdb -I inst1 -a inst1 -w inst1 -t inst1 -l <instance home directory> -n

   Note:
   If the change log database is configured previously for the migrated instance, you need to configure the change log database for the directory server instance :

   idscfgchglg -I inst1 -n

8. Restore the database that was backed up using the DB2 commands. Run the following commands:
   1. su - inst1
   2. db2 restore database inst1 from <database backup directory> replace existing
   3. exit
   Note:
   If the change log database was backed up, restore the change log database for the instance using the DB2 commands.

   db2 restore db ldapclog  from <changelog backup directory>

9. Catalog the restored database using the DB2 commands. Run the following commands:
   1. su - inst1
   2. db2 uncatalog database inst1
   3. db2 catalog database inst1 as inst1 authentication server
   4. exit
   Note:
   Catalog the restored change log database using the DB2 commands.

   1. su - inst1
   2. db2 uncatalog database ldapclog
   3. db2 catalog database ldapclog as ldapclog authentication server
   4. exit
10. Start the directory server instance.

    ibmslapd -I inst1 -n -t

[ Top of Page | Previous Page | Next Page ]