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

CURRENTOPTIMIZATIONPROFILE DB2CLI.INI KEYWORD IS IGNORED BY THE CLI DRIVER
WHEN DB2 CLIENT IS CONFIGURED FOR MULTI-CONNECT

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When a db2 client is configured for multi-connect, the 
CurrentOptimizationProfile db2cli.ini keyword is ignored by the 
CLI driver and no SET CURRENT OPTIMIZATION PROFILE statement is 
sent to the server.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All client connections                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP1 or newer                             * 
****************************************************************
Local Fix:
NA
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem Fixed in DB2 Version 10.1 Fix Pack 1 and subsequent fix 
packs
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
05.11.2012
05.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList