home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84307 Status: Closed

SQL0433N error received by FUNCTION DBMS_UTILITY.EXEC_DDL_STATEM ENT if
statement is greater than 1024 characters

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
This is a current limitation of function 
DBMS_UTILITY.EXEC_DDL_STATEMENT where the statement cannot be 
greater than 1024 characters. This APAR will remove this 
limitation. 
 
error message is : 
SQL0433N  Value "<ddl text>" is too long.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgarde to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 Version 10.1 Fix Pack 1
Workaround
As a workaround for the current length restriction for 
DBMS_UTILITY 
instead of: 
CALL DBMS_UTILITY.EXEC_DDL_STATEMENT(?<ddl text>?); 
 
use: 
EXECUTE IMMEDIATE ?<ddl text>?;
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
28.01.2013
28.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList