|
Problem IC62372
|
Status: Closed |
After a call to SQLGetDiagField(), the message pointed to by the DiagInfoPtr output argument is padded to the right with garbage |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
After you call the CLI (Call Level Interface) function
SQLGetDiagField(), the message pointed to by the DiagInfoPtr
output argument might be padded to the right with garbage
characters.
This problem occurs only when SQLGetDiagField() retrieves the
message text from a DB2 for zOS database server.
The problem does not occur when SQLGetDiagField() retrieves the
message text from local message files on the client.
SQLGetDiagField() retrieves the message from the database server
only when the CLI configuration keyword UseServerMsgSP
is set to 1.
Here is an example of the error message that is
retrieved when you try to create an index that already exists in
your database:
SQLGetDiagField( pDiagInfo="[IBM][CLI Driver][DB2] THE NAME OF
THE OBJECT TO BE CREATED OR THE TARGET OF A RENAME STATEMENT IS
IDENTICAL TO THE EXISTING NAME OWNER.NAME~IDX x 34",
pcbDiagInfo=154 )
<--- SQL_SUCCESS Time elapsed - +1.173940E-001 seconds |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of CLI (Call Level Interface) applications with DB2 *
* for Linux, UNIX and Windows that connect to a DB2 on zOS *
* database. *
****************************************************************
* PROBLEM DESCRIPTION: *
* After you call the CLI (Call Level Interface) function *
* SQLGetDiagField(), the message pointed to by the DiagInfoPtr *
* output argument might be padded to the right with garbage *
* characters. *
* This problem occurs only when SQLGetDiagField() retrieves *
* the message text from a DB2 for zOS database server. *
* The problem does not occur when SQLGetDiagField() retrieves *
* the message text from local message files on the client. *
* SQLGetDiagField() retrieves the message from the database *
* server only when the CLI configuration keyword *
* UseServerMsgSP is set to 1. *
* *
* Here is an example of the error message that is retrieved *
* when you try to create an index that already exists in your *
* database: *
* *
* SQLGetDiagField( pDiagInfo="[IBM][CLI Driver][DB2] THE *
* NAMEOF THE OBJECT TO BE CREATED OR THE TARGET OF A *
* RENAMESTATEMENT IS IDENTICAL TO THE EXISTING NAME *
* OWNER.NAME~IDX x34", pcbDiagInfo=154 )<--- SQL_SUCCESS Time *
* elapsed - +1.173940E-001 seconds *
****************************************************************
* RECOMMENDATION: *
* . *
**************************************************************** |
| Local Fix: |
As a workaround, do not set the CLI configuration keyword
UseServerMsgSP to 1. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 1.
At a minimum, this fix should be applied on the client. |
| Workaround |
As a workaround, do not set the CLI configuration keyword
UseServerMsgSP to 1. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.08.2009
09.03.2010
16.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
