suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT27867 Status: Closed

TSA efix cannot be upgraded by installFixPack command.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Db2Installer does not install TSA efix, if RSCT version in host
is higher than install media.
The following case, Db2Installer does not install TSA efix.

e.g.)
server_t/db2//tsamp/db2cktsa -s media
3.2.1.2

This means RSCT of install media version is 3.2.1.2

server_t/db2//tsamp/db2cktsa -s install
3.2.1.15

This means RSCT of installed host version is 3.2.1.15

Installed RSCT is 3.2.1.15, install media RSCT is 3.2.1.2.  So,
Installer does not install TSA efix.

You can confirm install efix as below.
$ cat /opt/IBM/tsamp/sam/efix/installed

In case of V10.5FP8
DB2-4103-efix1

In case of V10.5FP9
DB2-4103-efix4

If you face "cat: cannot open
/opt/IBM/tsamp/sam/efix/installed", efix is not exist in your
host.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Db2 V10.5 FP9                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 V10.5 FP10                                    *
****************************************************************
Local Fix:
Execute db2installSAM separately.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.01.2019
10.03.2019
10.03.2019
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)