|
Problem IC85658
|
Status: Closed |
SQLGETDIAGFIELDW TRUNCATES THE ERROR MESSAGE RETURNED |
| product: |
DB2 CONNECT / DB2CONNCT / A10 - DB2 |
| Problem description: |
If you have a CLI application that calls SQLGetDiagField(), the
error message returned may be incomplete because CLI calls
SYSIBM.SQLCAMESSAGE() with incorrect parameters.
Example :
If your CLI application is calling the following procedure CALL
SYSPROC.ADMIN_INFO_SYSLOG
(NULL,'*','2012-05-06','00.01.00','2012-05-30','23.00.00',3000,?
) and it fails with error -471 :
the message returned is
SQLGetDiagField( pDiagInfo="[IBM][CLI Driver][DB2] INVOCATION OF
FUNCTION OR PROCEDURE SYSPROC.ADMIN_INFO_SYSLOG", pcbDiagInfo=84
)
<--- SQL_SUCCESS Time elapsed - +1.237700E-002 seconds
instead of
SQLGetDiagField( pDiagInfo="[IBM][CLI Driver][DB2] INVOCATION OF
FUNCTION OR PROCEDURE SYSPROC.ADMIN_INFO_SYSLOG FAILED DUE TO
REASON 00E79106", pcbDiagInfo=114 )
<--- SQL_SUCCESS Time elapsed - +1.237700E-002 seconds |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* db2connect users using cli. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v101fp2 or later releases. *
**************************************************************** |
| Local Fix: |
n/a |
| available fix packs: |
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_v101fp2 contains fix of this issue. After the fix, user will
get correct error message. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.08.2012
31.12.2012
31.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
