Upgrading the Db2 server to Db2 version 11.5.x

Edit online

After the Cloud APM server is installed, you can upgrade your local or remote Db2® server from Db2 version 10.5 or version 11.1 to version 11.5.x.

For the list of supported Db2 fix packs, open the Software Product Compatibility Report for your offering and click the Prerequisites tab to view the database requirements:

Before you begin

Make sure that the IBM® Cloud Application Performance Management, Private V8.1.4.0 interim fix 12 or a later interim fix is applied to the Cloud APM server. Interim fixes for the Cloud APM server V8.1.4 are available to download from IBM Fix Central.

About this task

To upgrade the Db2 server version 10.5 or 11.1.x to version 11.5.x, follow the Db2 server upgrade instructions in the IBM® Db2 Version 11.5 Knowledge Center. Then complete additional steps to update the Db2 server to use Cloud APM server jars and to upgrade the Db2 client on the Cloud APM server.

Procedure

Complete the procedure on the Cloud APM server and on remote Db2 server if the Db2 server is remote.

On the system where the Cloud APM server is installed, stop all server components by running the following command in the /usr/bin directory:
```
apm stop_all
```
On the system where the Db2 server is installed, upgrade the Db2 server by following the upgrade instructions in the IBM® Db2 Version 11.5 Knowledge Center.
On the system where the Db2 server is installed, configure the new version of Db2 to use the Cloud APM server jars by completing the following steps:
1. Login as the Db2 instance owner.
2. If the database name is changed, correct the database name in the following property files:
  1. Change to one of the following directories:
    - Local Db2 server:
      cd install_dir/db2/tbsmdb/sql
    - Remote Db2 server:
      cd path-specified-during-setup-db-config/sql
    where, path-specified-during-setup-db-config is the path that you specified for the Db2 instance when you ran the Cloud APM setup-dbconfg program. The default path is /opt/IBM/tivoli/tbsmdb.
  2. Run vi tbsm_db.properties and set TBSM.DatabaseName= to the correct database name. Save the change.
  3. Run vi tbsmudf_db.properties and set TBSM.UDF.DatabaseName= to the correct database name. Save the change.
3. Change to one of the following directories:
  - Local Db2 server:
```
cd install_dir/db2/tbsmdb/sql
```
  - Remote Db2 server:
```
cd path-specified-during-setup-db-config/sql
```
  where, path-specified-during-setup-db-config is the path that you specified for the Db2 instance when you ran the Cloud APM setup-dbconfg program. The default path is /opt/IBM/tivoli/tbsmdb.
4. Run the following command:
```
./tbsm_db.sh -s sc -U db2-instance-user -f j
```
On the system where the Cloud APM server is installed, upgrade the IBM Data Server Client component from the Db2 installation package to match the version of the Db2 server.
Follow the instructions in the IBM® Db2 Version 11.5 Knowledge Center.
On the system where the Cloud APM server is installed, ensure that the KQZ_JDBC_JAR_PATHS variable is set to the path where the upgraded Db2 client JDBC driver is located. To update the KQZ_JDBC_JAR_PATHS variable, complete the following steps:
1. Go to the install_dir/serveragents/config directory.
2. Back up the hostname_te.cfg file, where hostname is the Cloud APM server host name.
3. Open the hostname_te.cfg file and locate the following line that starts with KQZ_JDBC_JAR_PATHS=.
4. Set the KQZ_JDBC_JAR_PATHS value to the path where your Db2 11.1 JDBC driver jars are located.
  
  For example, if you are using Db2 V11.5, and your IBM Data Server Client is installed in the default /opt/ibm directory, the KQZ_JDBC_JAR_PATHS path looks like: KQZ_JDBC_JAR_PATHS=/opt/ibm/db2/V11.5/java.
5. Save and close the file.
Start all server components by running the following command in the /usr/bin directory:
```
apm start_all
```

Results

Your Db2 server that the Cloud APM server is connected to is upgraded.

Remember: If you complete a backup and restore for a disaster recovery, remember to upgrade the Db2 server to match the version used by the source server before completing the restore into the target server.