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

WHEN APP HAVE BOTH CLIENT SIDE TRIAL LIC AND SERVER LIC, THE SQLGETINFO
(CLI) FUNCTION WILL REPORT INCORRECT INFORMATION

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
CLI driver acquires information like DBMS version during first 
replay of SQLCA structure, however the structure might be 
cleared by a mechanism that is supposed to avoid throwing a 
warring message related to trial license, in case of valid 
license on DBMS side. 
 
Please notice that information returned by variables like 
'SYSIBM.VERSION' might be also affected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI users.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade DB2 client to 10.1 FP4.                       * 
****************************************************************
Local Fix:
N/A.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
fixed in v101 fp4
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC98989 IC98990 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.01.2014
09.06.2014
09.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList