Netezza Performance Server 11.2.2.3 release notes

Deployment options: Netezza Performance Server for Cloud Pak for Data SystemNetezza Performance Server for Cloud Pak for Data as a Service

Version 11.2.2.3 provides backup and restore improvements, several fixes, and a stability patch for critical issues.

Important:
  1. 11.2.2.3 is compatible with Netezza Performance Server for Cloud Pak for Data System 2.0.X and Netezza Performance Server for Cloud Pak for Data as a Service.
  2. Netezza Performance Server clients older than 11.2.2.0 do not work with version 11.2.2.3 as a strict TLS 1.2 cipher set is used to conform to security standards. If you want to use clients older than 11.2.2 (including PureData System for Analytics clients), apply the workaround that is specified for PureData System for Analytics clients and the Netezza Performance Server 11.2.2.X host.
  3. Ensure that you have Java 1.7 or later.

    For more information, see Installing and configuring JDBC .

  4. Ensure that you have the Netezza Performance Server Go driver 1.15 or later.

    For more information, see Installing and validating the Go Driver.

  5. Starting from Netezza Performance Server 11.2.2.0, the name of the host container is ipshost-0. You can access the host container by running the oc command instead of the docker command.

New features

Netezza Performance Server for Cloud Pak for Data System
Backup and restore
  1. Added a nzinstall update command option to upgrade your Netezza Performance Server instance. For more information, see Upgrading to 11.2.2.3.
  2. Added a nzinstall delete --delete-bnr-storage STORAGE_TYPE command option that deletes specified type of storage from the backup and restore setup.
  3. Added customized tools for the backup and restore pod.
  4. New backup and restore deployment storage is added to the existing backup and restore storage deployment. For example, if you already have NFS storage and want to deploy SAN, you must modify and pass arguments for SAN with the nzinstall modify command. For more information, see Deploying backup and restore setups on running instances.

Resolved issues

  1. Fixed the issue with queries failing with error No such table exists on a second attempt.
  2. Fixed the issue with DBOS crashing while redumping modified plan to file.
  3. Fixed the issue with intermittent hangs.
  4. Fixed ERROR : unexpected error 12 that occurred when you ran merge query dynamically through a stored procedure.
  5. Fixed the issue with memory leaks with stored procedures that occurred after the ENABLE_SPROC_HIST_LOGGING variable was enabled.
  6. Fixed the issue with postmaster crashing by compiling librest with Go 1.18.

Known issues

Netezza Performance Server for Cloud Pak for Data SystemNetezza Performance Server for Cloud Pak for Data as a Service
Upgrade
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.
Backup and restore

If a large database backup to Azure Blob Storage with a single stream fails, update the number of streams to 16 and retry the backup.

nzrestore fails if backup is taken with BUCKET_URL having slashes.
Whenever the nzrestore failure happens with following error:
[Restore Server] : Starting the restore process
[Restore Server] : Operation aborted 
Error: Connector exited with error: 'The specified key does not exist. with address : xx.xxx.xx.xxx'.
Check the backup command and verify whether BUCKET_URL is having slashes as shown in the following example:
BUCKET_URL=bakcupbucket/subdir/
UNIQUE_ID=2024-01-12
WORKAROUND:
Modify BUCKET_URL and UNIQUE_ID as shown:
BUCKET_URL=bakcupbucket 
UNIQUE_ID=subdir/2024-01-12
Note: UNIQUE_ID is a combination of string that is taken from BUCKET_URL after the first slash and actual UNIQUE_ID. Pass these two arguments to the nzrestore command.