Upgrading Db2 Big SQL via CLI

This topic provides detailed steps on how to perform a Db2® Big SQL upgrade.

Before you begin

If Kerberos client authentication is enabled, disable it.

If Ranger security support is enabled, you must disable the Db2 Big SQL Ranger plugin and remove the Db2 Big SQL plugin definition from Ranger. For more information, see Ranger requirements when upgrading Db2 Big SQL.

About this task

This task provides an overview of the full process for you to upgrade Db2 Big SQL 5.0.4.0 and 6.0.0.0 on Hortonworks Data Platform (HDP) to Db2 Big SQL 7.1.0.0 on Cloudera Data Platform (CDP) Private Cloud Base. You must upgrade Db2 Big SQL to version 7.1.0.0 if you want full, functional support with the most recent version of CDP Private Cloud Base.

Important: Db2 Big SQL 7.1.0.0 is supported on CDP Private Cloud Base 7.1.3, 7.1.4, and 7.1.6. To upgrade to Db2 Big SQL 7.1.0.0, you must also upgrade to one of these CDP Private Cloud Base versions.

The following HDP to CDP Private Cloud Base upgrade paths are supported.

HDP 2.6.5.x to CDP Private Cloud Base 7.1.3, 7.1.4, or 7.1.6.
Recommendation: Upgrade to CDP Private Cloud Base 7.1.6.
HDP 3.1.x to CDP Private Cloud Base 7.1.6.
Note: In-place upgrade from HDP 3.1.x to CDP 7.1.6 on IBM® POWER® System is not supported.

For additional compatibility details, see System requirements for IBM Big SQL and IBM BigInsights®.

Starting with Db2 Big SQL 6.0.0.0, Data Server Manager (DSM) is replaced by the Db2 Big SQL console. One of the upgrade steps when you upgrade Db2 Big SQL 5.0.4.0 is removing DSM.

You must do the upgrade as the root user. The upgrade process does not support CDP Single User Mode.

Procedure

To migrate from HDP 2.6.x to CDP Private Cloud Base 7.1.3, 7.1.4, or 7.1.6 and back up Db2 Big SQL 5.0.4.0, do the following steps:
1. Back up and remove the DSM service from your environment.
  For more information, see Backing up and removing Data Server Manager.
2. Back up Db2 Big SQL.
  For more information, see Backing up Db2 Big SQL metadata.
3. Do an in-place upgrade of HDP 2.6.x to CDP Private Cloud Base.
  For more information, see the Cloudera documentation HDP2 to CDP Private Cloud Base.
  Note: In the transition to Cloudera Manager stage, when you have completed the steps in the Cloudera Manager Installation and Setup page, in Cloudera Manager, set the Java Home Directory field in Hosts > Hosts Configuration.
4. Proceed to step 3 to upgrade and finalize your Db2 Big SQL installation.
To migrate from HDP 3.1.x to CDP Private Cloud Base 7.1.6 and back up Db2 Big SQL 6.0.0, do the following steps:
1. Back up and remove the Db2 Big SQL console service from your environment.
  For more information, see Backing up and removing the Db2 Big SQL console.
2. Back up Db2 Big SQL.
  For more information, see Backing up Db2 Big SQL metadata.
3. Do an in-place upgrade of HDP 3.1.x to CDP Private Cloud Base.
  For more information, see the Cloudera documentation HDP3 to CDP Private Cloud Base.
  Note: In the transition to Cloudera Manager stage, when you have completed the steps in the Cloudera Manager Installation and Setup page, in Cloudera Manager, set the Java Home Directory field in Hosts > Hosts Configuration.
Upgrade Db2 Big SQL.
1. If you are installing Db2 Big SQL on a cluster that does not have access to the internet, manually install the Cloudera Manager python client.
  For more information, see Installing the Cloudera Manager python client.
2. Upgrade and finalize your Db2 Big SQL installation.
  For more information, see Upgrading and finalizing Db2 Big SQL.
If Kerberos client authentication was disabled before the upgrade, re-enable it.
If Ranger security support for Db2 Big SQL was enabled, do the following steps after the Db2 Big SQL upgrade is completed:
1. Enable Ranger. For more information, see Enabling and disabling Ranger security support for Db2 Big SQL.
2. Manually import policies back into Ranger. For more information, see Migrating Db2 Big SQL Ranger policies.