|
Problem IC67764
|
Status: Closed |
IN DB2 V9.7, QUERY W/ RANGE PARTITION TABLE RETURNS -901 "BAD PLAN;UNRESOLVED QNC FOUND" IF PREDICATE ELIMINATES ALL PARTITION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A query can fail with with SQL0901, "Bad Plan; Unresolved QNC
found".
The conditions triggering the failure include a range
partitioned table where applying some of the predicates, but not
all predicates, will eliminate all partitions in a range
partitioned table.
The db2diag.log will contain the following message:
2010-03-18-11.24.10.716184-240 I624697E862 LEVEL: Severe
PID : 23763 TID : 187955145056 PROC :
db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB : SAMPLE
APPHDL : 1-32931 APPID:
*LOCAL.db2inst1.10031516111
AUTHID : DB2INST1
EDUID : 151518 EDUNAME: db2agent (SAMPLE) 1
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:300
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 30
sqlerrmc: Bad Plan; Unresolved QNC found
sqlerrp : SQLNG006
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000001 (5) 0xFFFFFFCE (6)
0x00000001
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Range Partitioned Tables *
****************************************************************
* PROBLEM DESCRIPTION: *
* A query can fail with with SQL0901, "Bad Plan; *
* UnresolvedQNCfound".The conditions triggering the failure *
* include a rangepartitioned table where applying some of the *
* predicates, butnotall predicates, will eliminate all *
* partitions in a rangepartitioned table.The db2diag.log will *
* contain the following message:2010-03-18-11.24.10.716184-240 *
* I624697E862 LEVEL:SeverePID : 23763 *
* TID : 187955145056 PROC :db2sysc 1INSTANCE: db2inst1 *
* NODE : 001 DB :SAMPLEAPPHDL : 1-32931 *
* APPID:*LOCAL.db2inst1.10031516111AUTHID : *
* DB2INST1EDUID : 151518 EDUNAME: db2agent *
* (SAMPLE) 1FUNCTION: DB2 UDB, relation data serv, *
* sqlrr_dump_ffdc,probe:300DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, *
* 136 bytessqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 *
* sqlerrml: 30sqlerrmc: Bad Plan; Unresolved QNC foundsqlerrp *
* : SQLNG006sqlerrd : (1) 0x00000000 (2) 0x00000000 *
* (3)0x00000000(4) 0x00000001 (5) 0xFFFFFFCE *
* (6)0x00000001sqlwarn : (1) (2) (3) (4) *
* (5) (6)(7) (8) (9) (10) *
* (11)sqlstate: *
****************************************************************
* RECOMMENDATION: *
* Upgrade to fix pack 3 or another release of DB2 *
* whichcontains the fix. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 |
Problem was first fixed in Version 9.7 Fix Pack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.04.2010
27.09.2010
27.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
