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

EXECUTION OF A QUERY CONTAINING SCALAR SUBQUERY OUTPUT COLUMN REFERENCE
MAY FAIL WITH SQL0901N IN A DPF ENVIRONMENT

Produkt:
DB2 CONNECT / DB2CONNCT / 950 - DB2
Problembeschreibung:
Execution of a query may fail with SQL0901N if the following 
conditions are satisfied: 
- Database is Data Partitioning Feature (DPF) enabled 
- Query or a view it references or one of its nested subselects 
contains a scalar subquery (SSQ) reference in the output column 
list 
- SSQ contains an equi-join predicate that directly references a 
local column and a column from the query that references SSQ 
- An SSQ output column (SSQOC) is from a base table or view (on 
at least one base table) that is referenced inside SSQ 
- SSQOC is used for output in the query column that references 
SSQ 
- SSQOC is not used in any predicates in the query that 
references SSQ 
 
The SQL0901N will look something like: 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason "probe 030 
in 
sqlkt_pack_tuple(), msg=cold=NULLABLE zvalue=NONULLS col(".) 
SQLSTATE=58004 
 
Corresponding entries in the db2diag.log may look something 
like: 
YYYY-MM-dd-hh.mm.SS.ssssss+sss xxxxxxxxxxx        LEVEL: Severe 
PID     : nnnnnnn              TID  : nnnn        PROC : db2sysc 
n 
INSTANCE: xxxxxxx              NODE : nnn         DB   : 
xxxxxxxx 
APPHDL  : nnn-nnnnn            APPID: *xxxx.xxxxxxx.nnnnnnnnnnnn 
AUTHID  : xxxxxxx 
EDUID   : nnnn                 EDUNAME: db2agntp (xxxxxxxx) n 
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: 70 
 sqlerrmc: probe 030 in sqlkt_pack_tuple(), msg=cold=NULLABLE 
zvalue=NONULLS col( 
 sqlerrp : SQLRI088 
 sqlerrd : (1) 0xhhhhhhhh      (2) 0xhhhhhhhh      (3) 
0xhhhhhhhh 
           (4) 0xhhhhhhhh      (5) 0xhhhhhhhh      (6) 
0xhhhhhhhh 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate:
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* EXECUTION OF A QUERY CONTAINING SCALAR SUBQUERY OUTPUTCOLUMN * 
* REFERENCE MAY FAIL WITH SQL0901N IN A DPF                    * 
* ENVIRONMENTExecution of a query may fail with SQL0901N if    * 
* the followingconditions are satisfied:- Database is Data     * 
* Partitioning Feature (DPF) enabled- Query or a view it       * 
* references or one of its nestedsubselects contains a scalar  * 
* subquery (SSQ) reference in theoutput column list- SSQ       * 
* contains an equi-join predicate that directlyreferences a    * 
* local column and a column from the query thatreferences SSQ- * 
* An SSQ output column (SSQOC) is from a base table or view(on * 
* at least one base table) that is referenced inside SSQ-      * 
* SSQOC is used for output in the query column thatreferences  * 
* SSQ- SSQOC is not used in any predicates in the query        * 
* thatreferences SSQThe SQL0901N will look something           * 
* like:SQL0901N  The SQL statement failed because of a         * 
* non-severesystem error.Subsequent SQL statements can be      * 
* processed.  (Reason "probe030insqlkt_pack_tuple(),           * 
* msg=cold=NULLABLE zvalue=NONULLS                             * 
* col(".)SQLSTATE=58004Corresponding entries in the            * 
* db2diag.log may look                                         * 
* somethinglike:YYYY-MM-dd-hh.mm.SS.ssssss+sss xxxxxxxxxxx     * 
* LEVEL:SeverePID    : nnnnnnn              TID  : nnnn        * 
* PROC :db2syscnINSTANCE: xxxxxxx              NODE : nnn      * 
* DB  :xxxxxxxxAPPHDL  : nnn-nnnnn                             * 
* APPID:*xxxx.xxxxxxx.nnnnnnnnnnnnAUTHID  : xxxxxxxEDUID  :    * 
* nnnn                EDUNAME: db2agntp (xxxxxxxx) nFUNCTION:  * 
* DB2 UDB, relation data serv, sqlrr_dump_ffdc,probe:300DATA   * 
* #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytessqlcaid : SQLCA      * 
* sqlcabc: 136  sqlcode: -901  sqlerrml: 70sqlerrmc: probe 030 * 
* in sqlkt_pack_tuple(), msg=cold=NULLABLEzvalue=NONULLS       * 
* col(sqlerrp : SQLRI088sqlerrd : (1) 0xhhhhhhhh      (2)      * 
* 0xhhhhhhhh      (3)0xhhhhhhhh(4) 0xhhhhhhhh      (5)         * 
* 0xhhhhhhhh      (6)0xhhhhhhhhsqlwarn : (1)      (2)      (3) * 
* (4)        (5)      (6)(7)      (8)      (9)      (10)       * 
* (11)sqlstate:                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fixpack 6.                        * 
****************************************************************
Local-Fix:
None exists apart from manually rewriting the query in question 
to preclude the conditions described
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 DB2 Version 9.5 Fixpack 6.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC68315 IC68316 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.03.2010
14.07.2010
14.07.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version