Required steps before upgrading the Data Gate instance

Complete the following steps before you upgrade a Data Gate instance.

Upgrade order

It is recommended that you upgrade your Db2 or Db2 Warehouse target database before you upgrade Data Gate itself.

Required steps before upgrading the target database

These steps affect the configuration of your Db2 or (Db2 Warehouse) target database. You must complete these steps before you upgrade the target database service itself. Otherwise, important configuration changes for Data Gate get lost when you upgrade the target database service.

Changing the target database configuration
In general, you apply changes to the configuration of the target database by following the steps in Changing Data Gate configuration settings.
Disabling archive logging
To guarantee a smooth operation of Data Gate on your target database, disable archive logging. To this end, set LOGARCHMETH1 to OFF. For more information, see step 3 in Changes to the target database.
Increasing the log file size
For the best performance of Data Gate operations on the target database, increase the log file size. To this end, set LOGFILSZ and LOGPRIMARY to higher values. For more information, see 2 in Installing a Db2 instance for Data Gate on Cloud Pak for Data.

Known issues

The following issues might occur after a Data Gate product upgrade. Check for and fix these issues before you upgrade your service instances:

Ensuring the deletion of the upgrade flag
Sometimes, when you upgrade Data Gate from version 4.7, the process that removes the upgrade flag is not completed due to a timeout. You can remove the flag file and the corresponding job manually. For more information, see Upgrade flag not deleted after upgrade.
Fixing an incomplete upgrade
If your Data Gate instance is unavailable after the upgrade, upgrade processes might not have run to completion. The upgrade process automatically starts two jobs, one for a data backup and another one for the code migration. A missing container and the failure of the instance indicate that one or both of the jobs could not be completed successfully. For more information, see Data Gate instance failed after upgrade.
Fixing a Db2 connection not released issue
There is a known issue in version 4.8.4 of the Db2 service (s390x only) where the auto_rotate_cert.sh in the Db2 container might hang and not release the Db2 connection. Run the following command in the Db2 container to disable it:
db2 -v "CALL SYSPROC.ADMIN_TASK_REMOVE('ROTATE_DB2_SSL_CERTS', NULL)"