|
Problem IC91807
|
Status: Closed |
WITH DATA_ENCRYPT A QUERY MAY FAIL AND RETURN SQL0902C. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When AUTHENTICATION on the database server is set to
DATA_ENCRYPT, any data transferred between the server and the
client is encrypted.
It was found that, with DATA_ENCRYPT DB2 LUW client sometimes
fails to parse the query result, and returns SQL0902C.
The size of the communication buffer is controlled by ASLHEAPSZ
for local clients.
For remote client at least a 128K buffer is allocated.
The issue can be hit by both local and remote client.
Here's the error message that will appear in db2diag.log.
====
2013-03-06-11.29.11.620518+060 I174864A1392 LEVEL: Severe
PID : 52232198 TID : 1 PROC : db2bp
INSTANCE: db2inst1 NODE : 000
APPID : *N0.db2inst1.130306102052
EDUID : 1
FUNCTION: DB2 UDB, DRDA Application Requester,
sqljrPostErrorProcessin probe:911
MESSAGE : ZRC=0x87360009=-2026504183=SQLJC_ERROR_BEOF "DATA DOES
NOT EXIST"
DIA8506C Unexpected end of file was reached.
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] pdLog
[1] sqljrPostErrorProcessing
[2] sqljrPostErrorProcessing
[3] sqljrDrdaArFetch
[4] csmDriveFetch
[5] csmDriveFetch
[6] csmGetCursorBuf
[7] clientboWriteStringNoConv
[8] clientboDDFMode1Conversions
[9] clientboDDFMode1Conversions
====
The LUW client in question can be CLP, CLI/ODBC or legacy JDBC
(using CLI under the covers). JCC type 4 driver does not have
this problem.
The data in the server is never corrupted. The problem is only
on the client that fails to parse the encrypted data. Any
fix pack containing the fix for this problem must be applied to
clients. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 and Fix Pack 3 *
**************************************************************** |
| Local Fix: |
Local fix:
If this problem occurs for a local connection, change the value
of ASLHEAPSZ to any other value eg 8.
For remote client, try changing FetchBufferSize greater than
128K.
Also note that this problem is only applicable to DATA_ENCRYPT.
One may choose to change AUTHENTICATION on the server side to
some other value to work around it. |
| available fix packs: |
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 was first fixed in DB2 Version 10.1 and Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2013
21.10.2013
21.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
