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

BUILT-IN STRING FUNCTIONS MAY RETURN AN INCORRECT RESULT OR FAIL WITH
SQL0901N WHEN CODEUNITS16 OR CODEUNITS32 IS SPECIFIED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The built-in scalar functions INSTR, LOCATE, LOCATE_IN_STRING 
and POSITION may return an incorrect result or fail with SQLCODE 
-901 when CODEUNITS16 or CODEUNITS32 is specified, e.g.: 
 
  values LOCATE(LOWER('eq'),'1eq3', CODEUNITS16) 
 
  1 
  ----------- 
            0 <- Wrong, should be 2 
 
    1 record(s) selected. 
 
  values LOCATE(UPPER('e'),'1EQ3', CODEUNITS32) 
  SQL0901N  The SQL statement or command failed because of a 
  database system error. (Reason 
  "(POSSTR: unable to precompile search pattern)".) 
  SQLSTATE=58004 
 
This can happen when the search-string is an expression that 
includes only literals and built-in functions.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 fix pack 4                       * 
****************************************************************
Local Fix:
Replace the search-string expression with a simple string 
literal
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 version 10.1 fix pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.12.2013
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList