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 IT35066 Status: Closed

LPAD OR RPAD BUILTIN FUNCTION FAIL WITH

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
A SQL statement may fail with the following error if the
statement uses the LPAD or RPAD functions, and the length
argument of the function is a constant expression that has a
value greater than 101:

     select LPAD(C1, TRIM(' 102 ')) from T
     SQL0901N  The SQL statement or command failed because of a
database system
     error. (Reason "Value is too large for the buffer".)
SQLSTATE=58004
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 version 11.5.6.0                              *
****************************************************************
Local Fix:
If possible, replace the constant expression with a simple
constant, e.g.:
     select LPAD(C1, 102) from T
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 version 11.5.6.0                              *
****************************************************************
Comment
First fixed in Db2 version 11.5.6.0
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.11.2020
21.06.2021
21.06.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)