|
Problem IC68230
|
Status: Closed |
A QUERY RETURNING A BIGGER RESULT SET MAY FAIL WITH SQL0902C, WHEN USING COMMUNICATION BUFFER GREATER 32K AND DATA_ENCRYPT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When AUTHENTICATION is set to DATA_ENCRYPT in the DBM CFG, a
query can fail with SQL0902C reason code 9, when the
communication buffer size is greater than 32K.
The following messages can be found in the db2diag.log file:
2010-04-28-09.09.49.311641+000 I1315A1115 LEVEL: Info
PID : 1904884 TID : 1 PROC : db2bp
INSTANCE: xxxxxxx NODE : 000
APPID : *LOCAL.xxxxxxx.100428090915
FUNCTION: DB2 UDB, DRDA Communication Manager,
sqljcReadDssContLen, probe:50
MESSAGE : ZRC=0x87360009=-2026504183=SQLJC_ERROR_BEOF "DATA DOES
NOT EXIST"
DIA8506C Unexpected end of file was reached.
CALLSTCK:
[0] 0x0900000021B71EA4 sqljcReadDssContLen__FP10sqljCmnMgr
[1] 0x0900000021A558A4 sqljrParseOpenSuccessReply__FP14db2UC
[2] 0x0900000021A55F2C sqljrParseOpenQueryReply__FP14db2UC
[3] 0x0900000021A447D4 sqljrParse__FP14db2UCinterface
[4] 0x0900000021A366C0 sqljrDrdaArOpen__FP14db2UCinterface
2010-04-28-09.09.49.506555+000 I2431A830 LEVEL: Info
PID : 1904884 TID : 1 PROC : db2bp
INSTANCE: xxxxxxx NODE : 000
APPID : *LOCAL.xxxxxxx.100428090915
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrParseQryDta,
probe:10
MESSAGE : ZRC=0x87360009=-2026504183=SQLJC_ERROR_BEOF "DATA DOES
NOT EXIST"
DIA8506C Unexpected end of file was reached.
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 2
sqlerrmc: 9
sqlerrp : sqljrqry
sqlerrd : (1) 0x87360009 (2) 0x00000009 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 4. *
**************************************************************** |
| Local Fix: |
In the DBM CFG on server side:
* Set ASLHEAPSZ to a smaller value like 10 (default is 15)
* Do not set DATA_ENCRYPT for AUTHENTICATION
For remote clients:
* Set RQRIOBLK to 32767 on the client side |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.7 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.04.2010
01.05.2011
01.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
