|
Problem IC62349
|
Status: Closed |
Usage of global variable name longer than 64 characters results in error message SQL0206N |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
Variable name longer than 64 characters cannot be used in the
context of a parameter of a procedure results in SQL0206N.
Example:
-- create a global variable with 65-character name
CREATE VARIABLE
V234567890V234567890V234567890V234567890V234567890V234567890V234
5
INTEGER DEFAULT 42 ;
-- create a simple procedure
CREATE PROCEDURE PROC01(in A INTEGER)
BEGIN
RETURN A;--
END;
-- return SQL0206N
CALL
PROC01(V234567890V234567890V234567890V234567890V234567890V234567
890V2345); |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Software *
****************************************************************
* PROBLEM DESCRIPTION: *
* Variable name longer than 64 characters cannot be used in *
* the *
* context of a parameter of a procedure results in SQL0206N. *
****************************************************************
* RECOMMENDATION: *
* Move to v95fp5 *
**************************************************************** |
| Local Fix: |
Change the variable name to less than or equal 64 characters. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in v95fp5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.08.2009
05.02.2010
05.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.5
|
 |
