|
Problem IC71783
|
Status: Closed |
DB2 FAILS TO SHOW TSA UPGRADE ERROR WHEN THE LOCALE IS ZH_TW |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
When using the locale ZH_TW, the TSA may fail to upgrade without
showing an error message in the log file. This may be the case
when the TSA license installed on the system is permanent while
the license available on the image is a try & buy license.
After applying the fix, you will see the message in the log
file, translated to the current locale:
"The DB2 installer could not update the IBM Tivoli System
Automation for Multiplatforms Base Component (SA MP Base
Component) from the currently installed version 2.2.0.7 to the
version 3.1.0.6 on the DB2 install media. Upgrading from this
particular older version to this particular newer version is not
supported. For information about manually upgrading the SA MP
Base Component, see the SA MP Base Component Installation and
Configuration Guide at
http://www.ibm.com/support/docview.wss?uid=swg21433814" |
| Problem Summary: |
|
| Local Fix: |
See the upgrade process at:
http://www.ibm.com/support/docview.wss?uid=swg21433814 |
| available fix packs: |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Comment |
This fix is needed to detect the license type in samlicm under
the ZH_TW locale. The output cannot be parsed when the locale is
ZH_TW. Since samlicm is a tsa command that is already installed
on the system, our code needs to work around this issue to
change the locale temporarily to EN_US prior to executing
samlicm. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC71878 IC71879
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2010
25.10.2010
25.10.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.7
|
 |
| 9.5.0.7
|
|
