home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC75034 Status: Closed

A QUERY WITH A PREDICATE OF "QUERYTAG=?" OR "QUERYNO=?"
MAY REPORT A SQL0901N ERROR

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When you submit a query, DB2 will report error SQL0901N when all 
of the following conditions are met: 
 
- The query contains the predicate "QUERYTAG=?" or "QUERYNO=?"; 
 
- The query contains another predicate with a literal value that 
may be replaced with a host variable if the statement 
concentrator is turned ON; that is, if the database 
configuration parameter STMT_CONC is set to LITERALS. 
 
For example, 
 
# Create a table named TEST with a column named QUERYTAG. 
db2 "create table TEST(C1 char(1) not null, QUERYTAG char(1) not 
null)" 
 
# Issue a SELECT sql with two predicates: One is QUERYTAG=? and 
# the other one is C1='P'.  You will see a SQL0901N error. 
 
db2 "select * from TEST where C1='P' and QUERYTAG=?" 
 
SQL0901N  The SQL statement failed because of a non-severe 
system error. Subsequent SQL statements can be processed. 
(Reason "Parameter marker in literal replaced statement".) 
SQLSTATE=58004
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5 or newer               * 
****************************************************************
Local Fix:
Turn the statement concentrator off, i.e., 
 
db2 "update db cfg for <dbname> using STMT_CONC OFF" 
 
replacing <dbname> with the database name.
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 Version 9.7 fix pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.03.2011
19.01.2012
19.01.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList