Upgrading Netezza Performance Server and Persistent Transient Storage (PTS)

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

Learn how to upgrade Netezza Performance Server and Persistent Transient Storage (PTS) if you are on a version of Netezza Performance Server that uses Cloud Pak for Data System 1.0.7.6 or lower.

Note: These systems already have a PTS-based replication deployed (Netezza Performance Server Replication Services 1.6). NRS 1.6 goes end-of-service together with PureData System for Analytics.

Before you proceed with the upgrade, take note of these points:

Do this procedure only if you have the replication environment set up.
If you upgrade Netezza Performance Server, you must also upgrade the PTS (replication log server) software.
Upgrade Netezza Performance Server first, then the replication log server (PTS).
For a Netezza Performance Server upgrade, all subordinate systems must be the same as the primary system.
Both primary system and subordinate system must be upgraded.
No pending transactions are allowed. The CSNs must be the same.

Procedure

For an Netezza Performance Server upgrade, ensure that all subordinate systems are the same as the primary system.
Run the command on subordinate and primary systems.
```
nzsql -c "select NODE_ROLE,NODE_CSN from _v_replication_sync"
```
Suspend replication on all nodes.
Run the command on each node, starting with the primary one.
```
nzsql -c "ALTER REPLICATION NODE repslet.<nodename> STATE SUSPENDED;"
```
Follow the software upgrade steps as described in Upgrading Netezza Performance Server. Do the upgrade on the primary and subordinate nodes.
Note:
- If you are upgrading to 11.0.7.0 and later or 11.0.6.1 and lower, after you redeploy the container as described in Redeploying the container to 11.2.1.10 or later or Redeploying the container to 11.2.1.9 or earlier, do not start the system at the end of the procedure. Leave it in the Stopped state, and proceed to upgrading the PTS log server.
- If you are upgrading to 11.2.X, after you redeploy the container as described in Redeploying the container to 11.2.1.10 or later or Redeploying the container to 11.2.1.9 or earlier, do not start the system at the end of the procedure. Leave it in the Stopped state, and proceed to upgrading the PTS log server.
When all the upgrade steps are completed on the primary and subordinate systems, copy the PTS upgrade binary files on the PTS log server.
The PTS upgrade binaries are in the /nz/kit/pts/ directory on Netezza Performance Server.
Stand-alone means that there is one PTS node per primary and subordinate node.

Note: For a cluster PTS setup, for example, PTS in HA environment with HA1 and HA2 for primary PTS and HA1 and HA2 for SUB PTS, follow the instructions in Upgrading PTS in cluster environment.
1. On the replication log server host, log in as the root user.
2. If you are upgrading from 11.0.X to 11.2.X, uninstall pts on the PTS log server:
```
/opt/ibm/nzpts/uninstallpts
```
  Select Y if you are prompted for confirmation.
3. Run the following command.
```
export PATH=$PATH:/sbin:/usr/sbin
```
4. Copy the PTS software installation files, pts.tar and installpts, to the replication log server.
  You can find the PTS upgrade binary files under the /nz/kit/pts/ directory on the Netezza Performance Server servers.
```
mkdir /tmp/pts
scp nz@NPSHOST:/nz/kit/pts/* nz@pts:/tmp/pts
```
5. Change directories to the destination directory where you copied the files.
```
cd /tmp/pts
```
6. Run installpts standalone to install or update the PTS service software.
```
./installpts standalone -c
```
7. Confirm that the ptsd service is running.
```
service ptsd status
```
8. After you installed the PTS software, switch to the nz user.
```
su - nz
```
9. Verify the version.
```
export PATH=/opt/ibm/nzpts/bin/:$PATH
ptsrev 
(or)
/opt/ibm/nzpts/bin/ptsrev
```
10. Repeat steps a - i on subordinate PTS servers.
Start Netezza Performance Server on the primary and subordinate nodes.
```
nzstart
```
Activate the replication services on primary and the subordinate when Netezza Performance Server is online.
```
nzsql -c "ALTER REPLICATION NODE repslet.<nodename> STATE ACTIVE;"
```

Check the replication state.

nzsql -c "SELECT * FROM _v_replication_sync;"