DB2 - Problem description
Problem IC85503 | Status: Closed |
ACCESSING DB2/Z OS WITH CLI MAY ENCOUNTER -904 ERROR | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
DB2 client has a chance to use QRYBLKSZ basing on ASLHEAPSZ(max here is 10MB) when accessing DB2 z/OS with CLI. However, DB2 for z/OS has a limitation of supporting the QRYBLKSZ up to 10MB, 256K is currently the max supported, if the max size is exceeded, SQLCODE -904 or -246 will be generated. The issue can be reproduced with a Federation case: 1. Create DRDA wrapper 2. Create a server pointing to a DB2/z OS databse, set server option DB2_TWO_PHASE_COMMIT to 'Y' 3. Create an user mapping 4. Create a nickname pointing to a table on DB2/z OS The last steps will end up with following error: DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL1415N The statement was compiled for diagnostic purposes only and has not been executed. The fix will limit the QRYBLKSZ up to 256K on the client. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * The users are accessing DB2 z/OS via DRDA nickname with * * DB2_TWO_PHASE_COMMIT = 'Y'. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Server v97fp7 or later. * **************************************************************** | |
Local Fix: | |
Reduce DBM CFG ASLHEAPSZ to a value less than 2560. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
The problem is first fixed at v97fp7. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.07.2012 24.10.2012 24.10.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.7 |