DB2 - Problem description
Problem IC91727 | Status: Closed |
DB2_INSTALL WITH "-F NOTSAMP" OPTION FAILS ON HP-UX WITH: UNKNOWN KEYWORD "INSTALL_TSAMP" | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Running db2_install or installFixPack with "-f NOTSAMP" option fails on HP-UX platform with the following error message: DB2 Setup log file started at: Wed Oct 31 08:51:43 2012 MEZ ============================================================ Operating system information: HP-UX U.B.11.31 ERROR: A Response file error occurred. Unknown keyword "INSTALL_TSAMP" at line "5". ERROR: One or more errors occurred while checking the syntax of the response file "/tmp/db2_install.22283.rsp". Correct the errors and run the install again. DB2 Setup log file finished at: Wed Oct 31 08:51:43 2012 MEZ ============================================================ This happens because there is no "TSA MP" (Tivoli System Automation Multi Platforms) product that is bundled with DB2 on HP platform. In this case we should not generate a wrong response file. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * USERS ON HP-UX * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 3. * **************************************************************** | |
Local Fix: | |
omit the "-f NOTSAMP" option and rerun db2_install or installFixPack, there will be no TSA package installed anyways | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 10.1 Fix Pack 3. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.04.2013 02.10.2013 02.10.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 |