DB2 - Problem description
| Problem IC68107 | Status: Closed |
SILENT INSTALLATION (SETUP WITH THE -U OPTION) FAILS WHEN THE -P INSTALLATION-PATH PARAMETER ENDS WITH A BACKSLASH ("") | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
| Problem description: | |
When you try to do a silent installation by running the setup command with the -u option, if you also use the -p option to specify an installation path with a backslash "\" at the end then the installation does not work but returns immediately to the command prompt outputting no message. If you also use the -l option to generated an installation log, the installation log file is zero-length. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of DB2 on Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * . * **************************************************************** | |
| Local Fix: | |
As a workaround, remove the backslash ("\") at the end of the
installation-path that you specify using the -p option.
For example, rather than a command like:
setup -m -u DB2.RSP -p C:\MYINSTALL\
run a command like this instead:
setup -m -u DB2.RSP -p C:\MYINSTALL | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
Problem was first fixed in Version 9 Fix Pack 10 | |
| Workaround | |
As a workaround, remove the backslash ("\") at the end of the
installation-path that you specify using the -p option.
For example, rather than a command like:
setup -m -u DB2.RSP -p C:\MYINSTALL\
run a command like this instead:
setup -m -u DB2.RSP -p C:\MYINSTALL | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC68188 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.04.2010 07.02.2011 07.02.2011 |
| Problem solved at the following versions (IBM BugInfos) | |
9.0.FP10 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.1.0.10 |
|
| 9.7.0.3 |
|
| 9.7.0.3 |
|