Release Notes
Abstract
This document provides additional required steps to take after updating to 4.1.1.30 to migrate to the latest Postgres15 fileset, to resolve security vulnerabilities.
Content
Postgres Version | 15.18 |
VIOS levels | 4.1.1.30 |
Fix files | ios.viodb15 (7.3.4.3) ios.viodb13 (7.3.4.1) |
Fix Location | https://aix.software.ibm.com/aix/efixes/postgresql/pg1518/pg1518_fixes.tar |
Supported Environments
- This fix and procedure are intended for VIOS 4.1.1.30
- For systems running VIOS 3.1 or earlier levels of VIOS 4.1, it is recommended to upgrade to VIOS 4.1.1.30. Once the upgrade is complete, follow the steps below to update PostgreSQL to the latest supported version.
Note: These procedures require stopping the vio_daemon while the updates are done. Queries from the HMC or other management consoles may fail during this time.
Fix Installation
- Download the fix files from the above provided link.
- (For VIOS SSP Only) Follow the steps below for each node in the cluster, one at a time. Before starting, verify all nodes in the cluster are at ON_LEVEL:
$ cluster –status –verbose | grep –e “Node Upgrade Status”
Node Upgrade Status: 4.1.1.20 ON_LEVEL
Node Upgrade Status: 4.1.1.20 ON_LEVEL
- (For VIOS SSP Only) Stop cluster services on the node
$ clstartstop -stop -n <cluster_name> -m <node_name> - Stop the vio_daemon
$ stopsrc -s vio_daemon
0513-044 The viod Subsystem was requested to stop. - Make sure the vio_daemon is in “inoperative” state, before applying the fileset. Wait for the process to be inoperative.
$ lssrc -s vio_daemon
Subsystem Group PID Status vio_daemon inoperative - Apply the new filesets
$ updateios -dev <fileset location> -install - The installation summary will show the latest fileset version as below
+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
ios.viodb15.rte 7.3.4.3 USR APPLY SUCCESS
ios.viodb15.rte 7.3.4.4 ROOT APPLY SUCCESS
- Start the vio_daemon
$ startsrc -s vio_daemon -a "-d 4" - Repopulate the change management database by signaling the vio_chgmgt daemon.
$ oem_setup_env
> ps -ef | grep vio_chgmgt”
> kill -1 <process_id of vio_chgmgt> - (For VIOS SSP Only) Start cluster services
$ clstartstop -start -n <cluster_name> -m <node_name>
Removal of Postgres13
To remove the Postgres 13 filesets please follow the below steps…
Stop the cluster services on the node (For SSP cluster only)
clstartstop -stop -n <cluster_name> -m <node_name>Stop the vios services
stopsrc -s vio_daemonInstall the ios.viodb13.rte from the location to unlink the Postgres13 binaries from the base ios.database.rte fileset
updateios -dev <fileset location> -installRemove the fileset
updateios -remove ios.viodb13.rte
+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
ios.viodb13.rte 7.3.4.1 ROOT DEINSTALL SUCCESS
ios.viodb13.rte 7.3.4.1 USR DEINSTALL SUCCESSStart the cluster services (For SSP cluster only)
clstartstop -start -n <cluster_name> -m <node_name>Start the vios services
startsrc -s vio_daemon -a "-d 4"
Was this topic helpful?
Document Information
Modified date:
14 August 2026
UID
ibm17283823