Netezza Performance Server release notes

Netezza Performance Server for Cloud Pak for Data System

Version provides a number of fixes (Postmaster, Postgres) and enhancements, such as Guardium support.

  1. If you are using custom SSL certificates, learn how to preserve them across Netezza Performance Server upgrade. For more information, see Preserving custom SSL certificates.
  2. Learn about the preferred cipher suites, how to enable, disable the TLS 1.2 ciphers, and create and enable certificates if you are on, 11.2.15, or later. For more information, see TLS 1.2 ciphers.

New features and enhancements


Guardium support is introduced. You can enable query and result sharing for auditing and policy enforcement purposes. For more information, see Enabling query and result sharing with Guardium.

Added support for Kerberos authentication over SSL for the ODBC, JDBC, and OLEDB drivers.

Resolved issues

  1. Fixed the issue with Postmaster crashing when a non-Boolean field was compared to a list of Boolean values.
  2. Fixed the issue with Postmaster crashing when an SQL referring fence UDF got abort signal.
  3. Fixed the issue with Postmaster memory growing when user query with exist clause accessed multiple catalog tables, including _t_pg_locks.
  4. Fixed the issue with Postgres crashing for CTE queries with a column alias that starts with an underscore.
  5. Fixed the issue with Netezza Performance Server replica crashing when the role was being changed to primary.
  6. Fixed the issue with the .NET driver being unable to cast object of type 'System.Byte[]' to type 'System.String'.
  7. Fixed the issue with functions not being accessible after the system case was changed to lowercase.

Known issues

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 :'.
Check the backup command and verify whether BUCKET_URL is having slashes as shown in the following example:
Modify BUCKET_URL and UNIQUE_ID as shown:
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.