DB2 - Problem description
| Problem IC95665 | Status: Closed |
SQL0153N INSTEAD OF SQL0783N ERROR IS RETURNED , IF DECLARE CURSOR OF FOR STATEMENT HAS UNNAMED COLUMN. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
SQL0153N instead of SQL0783N error was returned , if FOR
statement has unnamed column.
CREATE OR REPLACE PROCEDURE "DB2INST1"."TEST1"
(
MSG IN OUT VARCHAR2
)
IS
v_msg VARCHAR2(30);
BEGIN
FOR cur_test in (SELECT 1 FROM DUAL) LOOP
v_msg := 'HELLO';
END LOOP;
END Test1;
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL0153N The statement does not include a required column list.
LINE
NUMBER=8. SQLSTATE=42908
However, SQL0153N error is incorrect.
SQL0783N is correct error number.
A duplicate column name or unnamed column was specified in a
DECLARE CURSOR statement of a FOR statement. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB version 10.5 fixpack 4. * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
| Solution | |
Problem was first fixed in DB2 UDB Version 10.5 FixPack 4. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.09.2013 15.09.2014 15.09.2014 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.4 |
|