In-place TSLM database migration to Db2 V11.5, from Db2 V10.5

Edit online

The process for migrating a TSLM database on Db2® V10.5 to Db2 V11.5.

The TSLM database migration to Db2 V11.5 is done by preparing another Db2 instance for Db2 V11.5. The contents of the TSLM database are backed up from the Db2 V10.5 instance and restored to the Db2 V11.5 instance.

Supported operating systems

The following operating systems are supported:
  • AIX® Version 7.1 (TL5/SP3), or a subsequent technology level and service pack level.
  • AIX Version 7.2 (TL3/SP2), or a subsequent technology level and service pack level.
  • Red Hat® Enterprise Linux® (RHEL) 7.9 (min. kernel 3.10.0-1160) , or a subsequent 7.x release.
  • Red Hat Enterprise Linux (RHEL) 8.3 (min. kernel 4.18.0-240) or a subsequent 8.x release.
  • SUSE Linux Enterprise Server 12 (SLES 12) SP5 (min. kernel version 4.12.14-122) or a subsequent SPx release.

Required software

The following packages are required when you install Db2 V11.5 in Linux environment:
  • audit-libs (both of 32 bit and 64 bit)
  • cracklib (both of 32 bit and 64 bit)
  • db4 (both of 32 bit and 64 bit)
  • libselinux (both of 32 bit and 64 bit)
  • libstdc++ (both of 32 bit and 64 bit)
  • pam (both of 32 bit and 64 bit)

Summary of the migration process

The following steps summarize the migration process:
  1. Unmount all mounted volumes.
  2. Stop the TSLM server.
  3. Back up the TSLM database as Db2 V10.5
  4. Install Db2 V11.5 and TSLM.
  5. Generate a restore script for the TSLM database.
  6. Run the restore script to restore the TSLM database.
  7. Uninstall the current version of TSLM.
  8. Delete the ermm user.
  9. Install the new version of TSLM.
  10. Start the TSLM server.
  11. Restart the Host Drive Manager (HDM).
  12. Connect the TSLM clients to the new TSLM server.
As Db2 V11.5 is installed to the server where Db2 V10.5 is installed, a new instance name other than db2inst1 is used for Db2 V11.5. The following key values are set in the response file of the Db2 installation:
Table 1. Db2 installation key values
Name Key value
FILE /opt/IBM/db2/V11.5
LIC_AGREEMENT ACCEPT ** ACCEPT or DECLINE
INSTALL_TSAMP NO
DB2_INST.NAME db2inst3
DB2_INST.GROUP_NAME db2grp3
DB2_INST.HOME_DIRECTORY /home/db2inst3
DB2_INST.PASSWORD ncc1701d
DB2_INST.SVCENAME db2cdb2inst3
DB2_INST.PORT_NUMBER 50009
DB2_INST.AUTHENTICATION SERVER
DB2_INST.FENCED_USERNAME db2fenc3
DB2_INST.FENCED_GROUP_NAME db2fsdm3
DB2_INST.FENCED_HOME_DIRECTORY /home/db2fenc3
DB2_INST.FENCED_PASSWORD ncc1701d
DB2CODEPAGE 1208

In Table 1, db2inst3 and db2grp3 are the new instance name and group for the database on Db2 V11.5. The new fenced user and group are also assigned in the table.