home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC68096 Status: Closed

INCORRECT CODE RETURNED DURING SILENT INSTALLATION

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
After a  silent installation, the error return code from the 
msiexec process can be overrided by an internal warning code. 
As an example, if you are doing a silent installation on a 
unsupported platform, the error returned code value will be 1 
(the action returns a warning), when the msiexec process will 
return 1603 (A fatal error occurred.)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* performing silent installation on Microsoft Windows          * 
* platforms only.                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see error description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 9.1 fix pack 10                           * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
first fixed in version 9.1 fix pack 10
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC68105 IC68106 IC68141 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2010
23.06.2011
23.06.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP10,
9.1.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.10 FixList