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 IT28395 Status: Closed

DURING A DB2 UPGRADE, FIX PACK UPDATE, OR FRESH INSTALL OF DB2 V11.1, TSA
MAY NOT BE UPGRADED.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Db2Installer does not install TSA efix, if RSCT version in host
is higher than install media.
In 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 installation media version is 3.2.1.2

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

This means RSCT of installed host version is 3.2.2.2

Installed RSCT is 3.2.2.2, 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 V11.1 FP2
DB2-4103-efix3


If you face "cat: cannot open
/opt/IBM/tsamp/sam/efix/installed", efix is not exist in your
host.

Reference:
https://www-01.ibm.com/support/docview.wss?uid=swg21997032
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* DB2 TSA users on AIX                                         *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 V11.1 Mod3 FP3 or higher                      *
****************************************************************
Local Fix:
Execute db2installSAM separately.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.03.2019
28.01.2020
28.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)