Netezza Performance Server 11.2.2.1 release notes

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

Important:
  1. Version 11.2.2.1 is available only on Cloud Pak for Data System 2.0.X and Cloud Pak for Data as a Service (Netezza Performance Server SaaS). For more information, see Installing Netezza Performance Server for Cloud Pak for Data System and Getting started with 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 Netezza Performance Server 11.2.2.1 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 from the Known issues section. The workaround uses 11.2.2.0 and prior cipher sets.
  3. You must have Java 1.7 or later for Netezza Performance Server 11.2.2.1 to work.

    For Netezza Performance Server for Cloud Pak for Data System 1.0.X, see Installing and configuring JDBC .

    For Netezza Performance Server for Cloud Pak for Data System 2.0.X, see Installing and configuring JDBC .

    For Netezza Performance Server for Cloud Pak for Data, see Installing and configuring JDBC .

  4. Netezza Performance Server Go driver version must be 1.15 or later.

    For Netezza Performance Server for Cloud Pak for Data System 1.0.X, see Installing and validating the Go Driver.

    For Netezza Performance Server for Cloud Pak for Data System 2.0.X, see Installing and validating the Go Driver.

    For Netezza Performance Server for Cloud Pak for Data, 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

Version 11.2.2.1 introduces Netezza Performance Server for Cloud Pak for Data as a Service.

Netezza Performance Server for Cloud Pak for Data as a Service is a fully managed, cloud native analytical data warehouse that is based on massively parallel processing [MPP] architecture. Netezza Performance Server for Cloud Pak for Data as a Service is used for analytical processing of historical data, and can process from 100 TB up to a few petabytes of data with best in the class performance. Its arrays of SPUs processes disjoint data set in parallel, which is then aggregated to come up with final result set.

Scaling

Scale your instances on demand or by following a schedule with the web console. You can choose from four workload contour profiles and allow for independent scaling of compute (performance) and storage with zero disruptions.

Migration
Do frictionless upgrades to the cloud with a simple lift and shift, and use blazing linearly scalable performance with a predictable cost profile with single command: nz_migrate or nzbackup.
Pause & Resume

Pause or resume the system from the web console. Auto pause and or resume is enabled by default and you can schedule auto pause and or resume to suit your specific business and workload requirements.

Note: See https://cloud.ibm.com/docs/netezza for Netezza Performance Server for Cloud Pak for Data as a Service documentation.

Resolved issues

11.2.2.1 contains stability fixes to support Cloud Pak for Data System 2.0.X, and a revised container architecture.

Known issues

Netezza Performance Server for Cloud Pak for Data System

Data loading

Fixed-format data files that contain numeric fields might be loaded incorrectly into the database. For more information, see https://www.ibm.com/support/pages/node/6583457.

nzrestore
Starting from Netezza Performance Server 11.2.2.0, the UID for the nz user is 1000 due to changes in reserved users for RHEL 7 and later. On PureData System for Analytics and Netezza Performance Serverthat is installed on Cloud Pak for Data System 1.X., the UID value was 500.
This change impacts restores of backups on Cloud Pak for Data System 2.0.X that were created on PureData System for Analytics and Netezza Performance Serverthat is installed on Cloud Pak for Data System 1.X.

WORKAROUND:

You must change backup files permissions (644) before you can proceed with the nzrestore command.
  1. As the nz user, go to the directory where backup is taken:
    cd /bnr_nfs/pda_backup/Netezza
  2. Change the permissions:
    find -type f | xargs chmod 644
    Note: You must change backup files permissions when you are doing differential backup and restore also.
SPU keys
Enabling SPU keys with Netezza Performance Server 11.2.2.0 and later is not supported.
PureData System for Analytics clients and the Netezza Performance Server 11.2.2.X host
You must apply the following workaround for the PureData System for Analytics clients to work with the Netezza Performance Server 11.2.2.X host.

WORKAROUND:

  1. Add the following line in /nz/data/postgresql.conf.
    ssl_cipher_list_append ='ECDHE-RSA-AES128-GCM-SHA256:!ECDHE-RSA-AES256-GCM-SHA384:!AES256-GCM-SHA384:!AES128-GCM-SHA256:!ECDHE-RSA-AES256-SHA384:TLSv1.2+HIGH:!AESGCM:!aNULL:!eNULL'
  2. Stop Netezza Performance Server.
    nzstop
  3. Verify that the system is stopped.
    nzstate
    Example:
    [nz@XX-node1-npshost ~]$ nzstate
System state is 'Stop'.
[nz@XX-node1-npshost ~]$
  4. Start the system.
    nzstart
  5. Verify that the system is back online.
    nzstate
    Example:
    [nz@XX-node1-npshost ~]$ nzstate
System state is 'Online'.
[nz@XX-node1-npshost ~]$
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.