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 IC67596 Status: Geschlossen

QUERY WITH RANGE PARTITIONED TABLE CAN FAIL WITH SQL0901 "BAD PL AN;
UNRESOLVED QNC FOUND" IF PREDICATES ELIMINATE ALL PARTITIONS

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of range partitioned tables.                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A query can fail with with SQL0901, "Bad Plan; UnresolvedQNC * 
* found".The conditions triggering the failure include a       * 
* rangepartitioned table where applying some of the            * 
* predicates, butnot all 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 Version 9.5 Fix Pack 6 or later releasecontaining * 
* the fix.                                                     * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.5 Fix Pack 6.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC67764 IC67765 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.04.2010
14.06.2010
14.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version