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 IC99967 Status: Closed

32-BIT RUN-TIME CLIENT INSTALL ON WINDOWS 64-BIT FAILS WHEN RESPONSE FILE
KEYWORD FILE=C:PROGRAM FILESIBMSQLLIB IS USED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Silent installation of 32-bit Run-time Client on Windows 64-bit 
fails 
when response file keyword FILE=C:\PROGRAM FILES\IBM\SQLLIB is 
used. 
 
Install Log shows: 
 
MSI (s) (10!38) [18:01:41:550]: WIN64DUALFOLDERS: 'C:\Program 
Files (x86)\' will substitute 17 characters in 'C:\Program 
Files\IBM\SQLLIB\' folder path. (mask argument = 0, the folder 
pair's iSwapAttrib member = 0). 
MSI (s) (10!38) [18:01:41:550]: In SetTargetPath, re-mapping 
'C:\Program Files\IBM\SQLLIB\' to 'C:\Program Files 
(x86)\IBM\SQLLIB\' because this is a 32-bit package being 
installed on Win64. 
: 
MSI (s) (10:7C) [18:01:54:137]: Product: IBM Data Server Runtime 
Client - DB2COPY1 -- Installation operation failed.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Run-time Client users on Windows                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FP5 or higher                           * 
****************************************************************
Local Fix:
Use response file keyword FILE=C:\PROGRAM FILES (x86) 
\IBM\SQLLIB which installs 32-bit Run-Time Client successfully.
Solution
First fixed in DB2 V10.1 FP5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.03.2014
12.10.2017
12.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)