Netezza Performance Server 11.0.7.1 release notes

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

Version 11.0.7.1 provides critical fixes, FIPS compliance support (the provided Cloud Pak for Data System release is 1.0.7.0.4 or higher).

Note:

During upgrade, a postgres crash might happen if FIPS and QUERY/AUDIT history are enabled on the system. To prevent the postgres crash, you must apply the workaround that is described in the Known Issues section before upgrading Netezza Performance Server.
You must migrate data from the existing SQLQUERIES table to a new one after the installation of Cloud Pak for Data System 1.0.7.5 is complete if you want to use stored queries on the Netezza Performance Server web console. For instructions, see the Known issues section of this release notes.

Resolved issues

Fixed the issue with replication getting suspended with Extended attr not found for <path>. This error was caused by an absence of a large file support for PTS.
Fixed performance issues that were related to queries, which were running against the _v_obj_relation and _v_object_data system views.
Added instrumentation for diagnosing the stuck spinlock. Aborting error.
Fixed a process crash, which happened when aggregate page counts reported by an SPU were out of range.
Fixed the issue with the OLE-DB driver not working on Windows 2012, Windows 2016 and Windows 10.

Known issues

During upgrade, a postgres crash might happen if FIPS and QUERY/AUDIT history are enabled on the system. To prevent the postgres crash, you must apply the following workaround before upgrading Netezza Performance Server.
To check if QUERY/AUDIT history is enabled on the system, run:
```
SHOW HISTORY CONFIGURATION;
```
If the CONFIG_DBTYPE column shows 1 or 2, QUERY/AUDIT history is enabled on the system.
WORKAROUND:
You must disable QUERY/AUDIT history if it's enabled on the system.
1. Run the following queries from the nzsql prompt:
```
CREATE HISTORY CONFIGURATION MY_NONE HISTTYPE NONE;
```
```
SET HISTORY CONFIGURATION MY_NONE;
```
2. Stop and restart the system:
```
nzstop
```
```
nzstart
```
3. Verify if query history is disabled:
```
SHOW HISTORY CONFIGURATION;
```
  If the CONFIG_DBTYPE column shows 3, QUERY/AUDIT history is disabled on the system.
You must migrate data from the existing SQLQUERIES table to a new one after the installation of Cloud Pak for Data System 1.0.7.5 is complete if you want to use stored queries on the Netezza Performance Server web console.
1. As admin, check the version of the SQLQUERIES table on the SYSTEM database:
```
select longsql from SQLQUERIES limit 1;
```
  You can run the query from the Query Editor on the web console.
  - If you see this error message Netezza Error: ERROR: Attribute 'LONGSQL' not found, this means the SQLQUERIES table is old and needs to be migrated.
2. To migrate, run the following sql queries on the System database:
  1. Rename the SQLQUERIES table to SQLQUERIESold:
```
alter table SQLQUERIES rename to SQLQUERIESold;
```
  2. Create a new SQLQUERIES table:
```
CREATE TABLE SQLQUERIES (name nvarchar(128), host varchar(256), port integer, database nvarchar(128),
schema nvarchar(128), sql nvarchar(15000), username nvarchar(128), timestamp timestamp, longsql boolean, pieces int);
```
  3. Copy data from SQLQUERIESold to SQLQUERIES:
```
insert into SQLQUERIES select *, false, 1 from SQLQUERIESold;
```
  4. Drop the SQLQUERIESold table:
```
drop table SQLQUERIESold;
```
Database connection errors out if a local host is used as a client system for a Netezza Performance Server connection when FIPS is enabled.
Platform manager is hung due to /var/log filesystem being full. It's full because it was flooded by NPS events, and gigabyte-sized logs from Netezza Performance Server are stored there.
WORKAROUND:

When the upgrade to 11.0.7.1 is completed, you must clean up events from the _t_event_info table. Contact IBM Support for assistance. IBM Support might reference this document.