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

INSTALLING IBM DATA SERVER RUNTIME CLIENT VIA SILENT INSTALL, FAILS TO
CREATE A DB2 INSTANCE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Environment:  Installing on Windows platforms.  Tested on
Windows 7 and 2008 server.

When using following command to silently install IBM Data Server
runtime client:
v10.5fp5_ntx64_rtcl_EN.exe /S /v"/l*v c:DB2LOGdb2rtcl.log /qn
RSP_FILE_PATH=c:db2rtcl.rsp"

the default instance is not created.

Following install if you open a DB2 CLP window and type db2level
or any db2 command you will receive error:
sql1022C Not enough memory to run command

If you then run db2icrt 

All works.

Issue is caused by db2rspgn generating
FILE=c:SQLLIB
where is should be
FILE=c:SQLLIB

Once we removed the extra  from the response file keyword
above, the silent install works.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************
Local Fix:
Ensure that response file keyword FILE value does not have a 
at the end.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT12695 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.12.2017
27.11.2018
27.11.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)