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

SQLCONNECT FAILS WITH CLI0124E WHEN CAPTUREMODE=ON and PDQXML file is not
specified.

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
When captureMode is ON without pdqxml file name specified, 
SQLConnect throws following error 
[IBM][CLI Driver] CLI0124E  Invalid argument value. 
SQLSTATE=S1009 
 
This message is incorrect in the context. User is not aware if 
this is the cause of the error, a better 
message should be thrown.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2-connect                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to db2_v97fp7                                        * 
****************************************************************
Local Fix:
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
db2_v97fp7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
14.11.2012
14.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