home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC71942 Status: Geschlossen

SQL COMPILATION FAILS WITH SQL0401N OR SQL0440N WHEN QUERY USES BUILT-IN
FUNCTION WITH STRING UNIT

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
A query may fail to compile with SQL0401N or SQL0440N when the 
query uses one of the following built-in string manipulation 
functions: 
 
    SYSIBM.CHARACTER_LENGTH 
    SYSIBM.INSERT 
    SYSIBM.LCASE 
    SYSIBM.LEFT 
    SYSIBM.LENGTH 
    SYSIBM.LOCATE 
    SYSIBM.LOWER 
    SYSIBM.OVERLAY 
    SYSIBM.POSITION 
    SYSIBM.RIGHT 
    SYSIBM.SUBSTRING 
    SYSIBM.UCASE 
    SYSIBM.UPPER 
 
The problem only occurs if one of the above string function 
invocations includes the optional string unit parameter 
(CODEUNITS16, CODEUNITS32 or OCTETS). For example: 
 
select * from t1 where substring (c1, 1, 5, codeunits16) = '' 
and c2=6939 
 
SQL0401N  The data types of the operands for the operation "=" 
are not compatible.  SQLSTATE=42818 
 
select * from t1 where c2=7453 and substring (c1, 1, 5, octets) 
= '' 
 
SQL0440N  No authorized routine named "SUBSTRING" of type 
"FUNCTION" having compatible arguments was found. 
SQLSTATE=42884
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who are using one of the built-in string manipulation  * 
* functions.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If this APAR is not applied, it is possible that a query may * 
* fail to compile with SQL0401N or SQL0440N.                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.1, Fixpack 10.                      * 
****************************************************************
Local-Fix:
If possible, avoid the use of the string unit.
verfügbare FixPacks:
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Lösung
First fixed in DB2 Version 9.1, Fixpack 10.
Workaround
n/a
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.10.2010
13.06.2011
13.06.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.1.FP10
Problem behoben lt. FixList in der Version
9.1.0.10 FixList