Netezza Performance Server 11.2.1.4 release notes

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

Netezza Performance Server 11.2.1.4 provides a stability patch for critical issues and a new web console.

New features and improvements

Web console
Important: If you are on Cloud Pak for Data System 1.0.7.8, you must use a new version of the Netezza Performance Server web console. For more information, see Web console.
Upgrade
  1. Automated preupgrade steps that are related to the crond service to provide better upgrade experience.

    For Netezza Performance Server for Cloud Pak for Data System 1.0.X, see Upgrading to 11.2.X.X.

    For Netezza Performance Server for Cloud Pak for Data System 2.0.X, see Upgrading to 11.2.X.X.

Event management
  1. Added support for configuring threshold values for the hwDiskFull event through the system registry variable.

    For Netezza Performance Server for Cloud Pak for Data System 1.0.X, see Disk space threshold notification.

    For Netezza Performance Server for Cloud Pak for Data System 2.0.X, see Disk space threshold notification.

    For Netezza Performance Server for Cloud Pak for Data, see Disk space threshold notification.

    .

Known issues

  1. 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.

  2. 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.

Resolved issues

Postgres
  1. Fixed the issue with the system crashing that happened while inconsistent AND-OR expressions were processed.
  2. Fixed the postmaster crash that was caused by a deadlock in spinlock.
  3. Fixed the OOM problem that happened during execution of deeply nested complex subqueries with case expressions.
  4. Fixed the issue with Postgres crashing during plan cleanup that was caused by recursion. .
  5. Fixed the issue with vacuum on empty pages.
  6. Avoided segmentation fault for views that contain the varlena constant across 32-bit to 64-bit upgrades.
  7. Fixed the issue with Postgres core memory dump that was caused by duplicate actions in the MERGE query.
Backup and restore
  1. Fixed the issue with an error appearing after the nzrestore command was run. The error was caused by permission issues on the listed user.
Security
  1. Fixed the user-related issues in a multidomain setup with Kerberos enabled.