Upgrading Netezza Performance Server

Deployment options: Netezza Performance Server for Cloud Pak for Data System

Learn how to upgrade Netezza Performance Server to 11.2.2.X if you are on Cloud Pak for Data System 2.0.X.

Note:
  1. Upgrading from 11.2.1.X or 11.2.0.X to 11.2.2.X is not supported. If you want to migrate to 11.2.2.X, contact IBM Support.
  2. Some of the custom changes that you applied to your instance are lost during the upgrade. You must apply your customizations after the upgrade. For more information, see What to do next.

Before you begin

  1. Download cpds-nps-tools for the version that you want to upgrade to on Cloud Pak for Data System.

    For example, cpds_nps_tools-2.0.1.2-x.x.x-icpds-release-2.0.1.2-noarch.rpm.

    1. Open Fix Central.
    2. In the Find product tab, in the Product selector field, type IBM Cloud Pak for Data System.
    3. In the Installed version field, select the Netezza Performance Server version that you want to upgrade to.
  2. On Cloud Pak for Data System, on e1n1, install Python scripts (including nzinstall) in /usr/lib/python3.6/site-packages/cpds_nps_tools.
    rpm -Uvf cpds-nps-tools.rpm
    Example:
    e1n1# rpm -Uvf cpds_nps_tools-2.0.1.2-20220519.143905-7-icpds-release-2.0.1.2-noarch.rpm

    Backup and restore configurations are not retained if you are upgrading from 11.2.2.0 or 11.2.2.1 to 11.2.2.3. For more information, see What to do next.

Procedure

  1. Download the following images from Fix Central.
    • bnr-server-image.tar
    • nps-host-ds.tar
    • nps-host-image.tar
    • nps-init-image.tar
    • nps-helm-image.tar
  2. Run the nzinstall update command:
    nzinstall update –-instance NPS INSTANCE –-imagedir IMAGE DIRECTORY
    Example: 
    nzinstall update –-instance nps-1 --imagedir /opt/ibm/appliance/storage/ips/nps-11.2.2.3/

    For more information about the nzinstall command, see The nzinstall command.

    The output for the nzinstall command displays oc commands that you can use to monitor the upgrade progress.

    • To follow the update job pod progress, run: 
      oc logs -f update-pod-20220609183239 -n nz-repo
    • To check the deployment status, run: 
      1. oc get pod update-pod-20220609183239 -n nz-repo
      2. oc get all -n nps-3
    Note: The default timeout for the update pod, which is created during upgrade, is 2 hours. If you have larger catalogs and Netezza Performance Server takes more time to upgrade, the update pod might report failure due to timeout.

    The upgrade procedure continues and the Netezza Performance Server pod is running. Netezza Performance Server will come online after the upgrade.

    You can monitor the nzupgrade file in the /data/catalog/var/log/ directory inside the container for upgrade progress.

What to do next

  1. Reapply the following custom changes:
    • Custom images for backup and restore third-party configurations.

      After you update from 11.2.2.0 or 11.2.2.1 to 11.2.2.3, you must modify your instance with the nzinstall modify command. For more information, see Deploying backup and restore setups on running instances.

    • Other custom changes that are not under /data or/nzscratch.
    • Cached passwords.

    LDAP, INZA, SQL Extensions and IFQ customizations are retained during upgrade.

  2. Upgrade the web console.

    For more information, see Upgrading the web console.