DB2 - Problem description
Problem IT24581 | Status: Closed |
ALL HOSTS IN THE PURESCALE CLUSTER MUST HAVE AN ENTRY IN SQLLIB_SHARED/.UPDATE OR INSTALLFIXPACK COULD FAIL. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
All hosts in the purescale cluster must have an entry in sqllib_shared/.update or installFixPack could fail. For instance, if a cluster contains hosts vmcoralinst01 - 04, Db2 is installed in /opt/ibm/db2/install_dir, and all hosts are on Db2 Version 10.5.0.9, then the .update file should look something like the following: ```[root@vmcoralinst01 sqllib_shared]# cat .update vmcoralinst01.torolab.ibm.com=/opt/ibm/db2/install_dir_2:10.5.0. 9 vmcoralinst03.torolab.ibm.com=/opt/ibm/db2/install_dir_2:10.5.0. 9 vmcoralinst02.torolab.ibm.com=/opt/ibm/db2/install_dir_2:10.5.0. 9 vmcoralinst04.torolab.ibm.com=/opt/ibm/db2/install_dir_2:10.5.0. 9``` Executing purescale installFixPack on a host that is not in the .update file but is part of the purescale cluster could fail and some softlinks in sqllib will not be recreated because of this | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.1 m4fp4 or later * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.03.2018 28.11.2018 28.11.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |