Netezza Performance Server 11.2.1.9 release notes

Netezza Performance Server for Cloud Pak for Data System

Version 11.2.1.9 introduces new features and enhancements, such as support for base node expansion and managing events features, and several fixes.

Note: Netezza Performance Server 11.2.1.9 is compatible with Cloud Pak for Data System 1.0.8.0 and later.

New features and enhancements

Support for base node expansion
Added support for base node expansion. Starting with Cloud Pak for Data System 1.0.8.0, Cloud Pak for Data is no longer supported. Worker nodes are now unused. Instead, with Netezza Performance Server 11.2.1.9 or later, you can use worker nodes (e2n1, e2n2) and unset nodes (e2n3, e2n4) as Netezza Performance Server SPU nodes. You can add these SPU nodes (from enclosure E2) to the first existing Netezza Performance Server by following the expansion process.
The node expansion procedure must be done by IBM Support only. For more information, IBM Support might reference Expanding Netezza Performance Server with Cloud Pak for Data System base enclosure (E2).
Note: If base nodes are used, you cannot deploy Netezza Performance Server Replication Services 3.0.0.0.
Event rules
Managing events
Added a platform type to the notifyType option of the nzevent add command. If you enabled event rules and set notifyType to platform for specific event types, only those specific events are relayed back to Platform Manager.
With this feature, instead of receiving alerts for each event, you can receive alerts after a specified number of occurrences. For example, you can get SPU network port up/down alerts (the nwIfChanged event) only after 50 occurrences by running the following command:
nzevent add  -name 'PlatformRelayNwIfChanged' -on yes -eventType nwIfChanged -eventArgsExpr '' -notifyType platform -eventAggrCount 50

See also: Event rules, Event notifications, and Adding event rules.

Automatically added event rules
If you are upgrading to 11.2.1.9 or later, several event rules are added automatically. For the full list, see Automatically added or removed event rules.
Aggregated event rules
Starting from 11.2.1.9, the following two events are aggregated events by default.
  • nwIfChanged: Aggregate count 10
  • hwDiskFull: Aggregated count 50
A platform alert is raised for nwIfChanged and hwDiskFull when Netezza Performance Server raises the same number of events that is specified for the event by the aggregate count.
You can change the aggregate count by running the nzevent modify command and modifying the respective Platform Relay as described in Specifying event rule email aggregation.
Log collection
Added mechanism to disable log collection at Netezza Performance Server level to prevent /tmp from getting filled up with logcollect logs.

The automatic log collection must not be disabled. However, for critical reasons, log collection can disabled for any specific event by IBM Support. IBM Support might reference Disabling log collection.

Alternatively, you can disable an event rule as described in Disabling event rules.
Software packages compatibility
PureData System for Analytics 7.2.1.11-P1 or later clients are compatible with Netezza Performance Server 11.2.1.9.

Resolved issues

Postgres
  1. Fixed the issue with the Number of max connections has exceeded error. The default value for maximum connections (maxConnections) is changed from 500 to 1000.
  2. Fixed the issue with host and SPU fabric utilization growing beyond 100%.
  3. Fixed the issue with Postgres crashing and reporting an error when a list of values was compared to a single Boolean value.
  4. Fixed the issue with a Postgres crash for CTAS on global temporal tables. CTAS is not allowed on global temporal tables.
  5. Fixed the issue with the nzload -allowreplay command not working. You can now enable or disable load continuation on your system.
  6. Fixed the issue with the scope of the SET CATALOG query that was coming from a stored procedure.
  7. Fixed the issue with pln file is not getting saved in the $NZ_KIT_LOG/plans directory when queries crash.
  8. Fixed the issue with a Postgres crash for CTAS on global temporal tables. CREATE TABLE AS (CTAS) is not allowed on global temporal tables anymore.
DBOS
  1. Fixed the issue with cache files getting deleted after running nzstart.
  2. Fixed the issue with a memory leak in DBOS and nzrestore.
Upgrade

  1. Fixed the issue with the nz_internal_temp_user user not being able to connect to locked databases.

  2. Fixed the issue with upgrade. Before an authentication method row is restored from _t_systemdef, it is verified whether the authentication method is present in the catalog.
System management
  1. Fixed the issue with disks becoming unreachable after an incorrectly performed disk removal.
  2. Fixed the issue with the ldrDataRdr command returning a replication PTS error even though replication was not enabled.
  3. Fixed the SPU reboot issue that happened when the rate of respawn menu processes and the count of respawn menu processes both exceeded specified limits.
  4. Fixed the issue with the No bitmap found error. The following EOK error code was added Ignoring error while removing bitmap to prompt you to ignore the no bitmap found message.
Connector node
  1. Fixed the issue with Java bulk load inserting data row by row.

Known issues

nzrestore errors
When you back up and restore global objects and users, the nzrestore command returns errors in the following two scenarios. Ignore these errors as they do not impact the restore process and the restore completes successfully. .
Scenario 1
The backup is done on 11.2.1.9 or earlier versions.
The restore is done on versions later than 11.2.1.9.
Error: 
[Restore Server] : Error: DB SQL 'GRANT SELECT ON ALL.T_GROUP TO PUBLIC; 
' failed - DB error - ERROR:  resolveObjectNameRv: object "T_GROUP" not found. 
[Restore Server] : Error: DB SQL 'GRANT SELECT ON ALL.VT_CURRENT_TIME TO PUBLIC; 
' failed - DB error - ERROR:  resolveObjectNameRv: object "VT_CURRENT_TIME" not found. 
[Restore Server] : Error: DB SQL 'GRANT EXECUTE ON ALL.SCAN_DATA_SOURCE_SCHEMA TO PUBLIC; 
' failed - DB error - ERROR:  resolveObjectNameRv: object "SCAN_DATA_SOURCE_SCHEMA" not found.
Scenario 2
The backup is done on versions later than 11.2.1.9.
The restore is done on 11.2.1.9 or earlier.
Error:
[Restore Server] : Error: DB SQL 'GRANT SELECT ON ALL.VT_CURRENT_TIME TO PUBLIC;
' failed - DB error - ERROR:  ProcessObjectPrivileges: object "VT_CURRENT_TIME" not found.
[Restore Server] : Error: DB SQL 'GRANT SELECT ON ALL.T_GROUP TO PUBLIC;
' failed - DB error - ERROR:  ProcessObjectPrivileges: object "T_GROUP" not found.
[Restore Server] : Error: DB SQL 'GRANT LIST,SELECT ON ALL._V_ROLE_PRIV TO PUBLIC;
' failed - DB error - ERROR:  ProcessObjectPrivileges: object "_V_ROLE_PRIV" not found.
[Restore Server] : Error: DB SQL 'GRANT LIST,SELECT ON ALL._V_EXTERNAL_DATA_SOURCE TO PUBLIC;
' failed - DB error - ERROR:  ProcessObjectPrivileges: object "_V_EXTERNAL_DATA_SOURCE" not found.
Accessing event rules information
If you are on 11.2.1.9 or later and if your client software package version is earlier than 11.2.1.9, the output of the nzevent show command might show BadNotifyType for some event rules.

WORKAROUND:

  • Upgrade your client version to 11.2.1.9 or later.
  • Run the nzevent show command on the host itself.
11.0.7.3 library error
If you want to use Netezza Performance Server 11.2.1.9 with an HPIT virtual machine that has Netezza Performance Server HPIT 11.0.7.X software packages, the HPIT virtual machine version must be on version 11.21 or earlier.
If your virtual machine is on 11.31 or later, you must upgrade your Netezza Performance Server software packages to 11.2.1.X.
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.