|
Problem IC73051
|
Status: Closed |
CALL STATEMENT RETURNS SQL0464W, DEFINED LIMIT DIFFERENT THAN SPECIFIED IN CREATE PROCEDURE STATEMENT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If the DYNAMIC RESULT SET clause is specified in a CREATE
PROCEDURE statement, and the number of result sets is greater
than 255, SQL0464W may be returned when the procedure is
executed:
CREATE PROCEDURE MYSCHEMA.MYPROC
DYNAMIC RESULT SETS 9999
...
CALL MYSCHEMA.MYPROC()
SQL0464W Procedure "MYSCHEMA.MYPROC" returned "30" query result
sets, which exceeds the defined limit "15". SQLSTATE=0100E
The number of dynamic result sets specified in the CREATE
PROCEDURE statement is inadvertently truncated to a one byte
value. In the example above, the 9999 value specified - 0x270F
in hexadecimal - is truncated to 0x0F or 15. The defined limit
will vary from 0 to 255 depending on the number of result sets
specified. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* If the DYNAMIC RESULT SET clause is specified in a CREATE *
* PROCEDURE statement, and the number of result sets is *
* greater than 255, SQL0464W may be returned when the *
* procedure is executed: *
* *
* *
* CREATE PROCEDURE MYSCHEMA.MYPROC *
* *
* DYNAMIC RESULT SETS 9999 *
* *
* ... *
* *
* *
* *
* CALL MYSCHEMA.MYPROC() *
* *
* SQL0464W Procedure "MYSCHEMA.MYPROC" returned "30" query *
* result sets, which exceeds the defined limit "15". *
* SQLSTATE=0100E *
* *
* *
* The number of dynamic result sets specified in the CREATE *
* PROCEDURE statement is inadvertently truncated to a one byte *
* value. In the example above, the 9999 value specified - *
* 0x270F in hexadecimal - is truncated to 0x0F or 15. The *
* defined limit will vary from 0 to 255 depending on the *
* number of result sets specified. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 4 *
**************************************************************** |
| Local Fix: |
None, warning can be ignored |
| 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 |
Problem was first fixed in DB2 Version 9.7 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC73196
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.12.2010
28.04.2011
28.04.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
|
 |
