DB2 FOR LUW / DB2FORLUW / A50 - DB2

TSA changed the way they deliver efixes to DB2 in 10.5 and as a 
result, the installer is not able to detect if a TSA efix is 
already installed or not, so the installer needs to be updated 
to recognize the TSA efix differently. 
 
The problem was firstly met while installing a special build on 
top of V10.5 FP8 by rolling update. 
 
Due to this issue,  the installer consider it needs require a 
TSA update but not GPFS, it will explicitly enter TSA 
maintenance mode and will not enter GPFS maintenance mode. Due 
to some dependencies between TSA and GPFS, GPFS will also go 
down implicitly since it would detect that TSA is down. After 
TSA update, the installer will exit TSA maintenance but will not 
exit GPFS maintenance (because it didn't enter GPFS 
maintenance). Then it will then continue even GPFS is still down 
when it should wait. 
 
You will have the following in the db2iupdt.log indicating gpfs 
is down during the rolling update: 
 
ERROR: Could not switch current DB2INSTANCE to "db2sdin1". The 
return code is 
"-5010". 
 
ERROR: The "db2instance -list" command failed with the return 
code: "127", and 
following error: "-bash: db2instance: command not found". 
 
ERROR: The "db2instance -list" command failed with the return 
code: "127", and 
following error: "-bash: db2instance: command not found".

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************

As a workaround, you can run "touch 
/opt/IBM/tsamp/sam/efix/0001.efix" on ALL the nodes with root 
user. This allows the installer to detect that the efix is 
installed already.

First fixed in Db2 10.5 Fix Pack 9

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

14.06.2017
29.09.2017
29.09.2017

9.0.