Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT02020 Status: Geschlossen

LPAD() AND RPAD() FUNCTION WITH EMPTY STRING CAUSES THE RESULT STRING TO BE
PADDED WITH '00' CHARACTERS

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Calling LPAD() and RPAD() function with an empty string '' (pad, 
third parameter) results in a output string with right padded 
with '00'`s characters up to the length provided. The resulting 
varchar string is padded with '00' chars which should not 
happen. 
 
Example: 
 
select LPAD('AAAAA', 10, '') AS F1 from sysibm.sysdummy1 
 
F1 
---------- 
AAAAA 
 
  1 record(s) selected. 
 
 
 
select HEX(LPAD('AAAAA', 10, '')) AS F1 from sysibm.sysdummy1 
 
F1 
-------------------- 
41414141410000000000 
 
  1 record(s) selected. 
 
 
If the pattern (third argument of L/RPAD()) is an empty string 
'', then we should return the result without any padding.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.05.2014
14.07.2015
14.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList