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

SELECT STATEMENT GOT SQL0901N WHEN IT HAS A LIKE PREDICATE WITH A NICKNAME

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
SQL0901N error may happen for a select statement having a like 
predicate and the like predicate is used with a nick name. 
 
An error example: 
 
$ db2 "select * from t1, rt2 where t1.c2 like rt2.c2||'%' 
SQL0901N  The SQL statement or command failed because of a 
database system 
error. (Reason "sqlno_cost_function       [153]:rc(     0) 
".) 
SQLSTATE=58004
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF environment.                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10.1 Fix Pack 1.                                 * 
****************************************************************
Local Fix:
Not available.
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 UDB Version 10.1 Fix Pack 1.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95980 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.08.2012
01.11.2012
01.11.2012
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