Netezza Performance Server 11.2.2.0 release notes

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

Important:

Netezza Performance Server 11.2.2.0 is available only on Cloud Pak for Data System 2.0.1 or later. For deployment steps, see Installing Netezza Performance Server.
If you are migrating from Cloud Pak for Data System 1.0.X to Cloud Pak for Data System 2.0.X, you must install the latest version of Netezza Performance Server Analytics. For more information, see Installing and upgrading Netezza Performance Server Analytics.
Netezza Performance Server clients older than 11.2.2.0 do not work with Netezza Performance Server 11.2.2.0. Make sure that you have the latest client versions installed.
Java version must be 1.7 or later for Netezza Performance Server 11.2.2.0 to work. For reference, see Installing and configuring JDBC.
Netezza Go driver version must be 1.15 or later. For reference, see Installing and validating the Go driver.
Starting from Netezza Performance Server 11.2.2.X, 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

You can back up data into different storage sources, such as NFS, SAN, iSCSI, and local (OCS-based storage), and deploy different backup and restore setups when you are deploying a new instance, on a currently running instance, or during upgrade. For more information, see Deploying backup and restore setups.
A technology preview of multiple Netezza Performance Server tenants is supported within a single Cloud Pak for Data System. For more information, see Multi-tenancy.
You can use the AutoMaint feature, which automates select maintenance activities. For more information, see Maintaining Netezza Performance Server 11.2.2.X with AutoMaint.
A technology preview of a time travel (temporal tables) feature is introduced, which you can use to track and analyze the history of changes in your data. For more information, see Temporal tables.
Netezza Replication Services is introduced. For more information, see Netezza Performance Server Replication Services.
New cron jobs usage is introduced.
Instead of editing files in /etc/cron*, you must edit files in /data/os/etc/cron*.

User cron jobs

As the root or nz user, you can create and edit Cron jobs by running the crontab command. The cron jobs are preserved when the container restarts or is upgraded.

System cron jobs

System-wide cron jobs are either placed in a large file in /etc/crontab, or as individual files in /etc/cron.d. On Netezza Performance Server 11.2.2.0, you must edit the ones in /data/os/etc/crontab and /data/os/etc/cron.d. The changes are preserved across container restarts and upgrades.

cron.hourly, cron.daily, cron.weekly, cron.monthly

The system runs cron jobs that are placed in /data/os/etc/cron.<hourly/daily/weekly/monthly> on a specified schedule.
For external table load and unload operations, a remote source Azure region (AZREGION, REGION) is a mandatory argument now. For more information, see Loading data, Unloading data and Examples.

Known issues

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 on Cloud Pak for Data System 2.0.1, 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 Server 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.1 that were created on PureData System for Analytics and Netezza Performance Server on Cloud Pak for Data System 1.X.

WORKAROUND:

You must change backup files permissions (644) before you can proceed with the nzrestore command.

As the nz user, go to the directory where backup is taken:
```
cd /bnr_nfs/pda_backup/Netezza
```
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.

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.