DB2 - Problem description
Problem IC93123 | Status: Closed |
INSTALLING FIXPACK FOR DB2 CLIENT USING DB2 SERVER OR UNIVERSAL IMAGE MAY REPORT A MINOR ERROR RELATED TO TSA. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
When installing DB2 Client using DB2 server or universal fixpack image on the machine where TSA is already installed, it may report a minor error related to TSA as follows. This can occur even with -f NOTSAMP option. Updating DB2 file sets :.......Success WARNING: DB2 internal error: the required utility "/opt/ibm/db2/V10.1_FP2client/install/tsamp/db2cptsa" cannot be found. Rerun the install or update utility (db2setup, db2_install, or installFixPack) again with trace turned on (by adding the -t argument.) Collect the resulting trace file, and the install log file, and contact IBM DB2 service for assistance. Installing or updating DB2 HA scripts for IBM Tivoli System Automation for Multiplatforms (Tivoli SA MP) :.......Failure The error is ignorable and the installation should be completed if no other errors are reported. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 3. * **************************************************************** | |
Local Fix: | |
Using DB2 Client fixpack image. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Version 10.1 Fix Pack 3. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC95470 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.06.2013 25.11.2013 25.11.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |