DB2 - Problem description
| Problem IC77345 | Status: Closed |
NEGATIVE COST OR CARDINALITY MAY BE SEEN IN ACCESS PLAN WHEN UNNEST TABLE FUNCTION IS USED IN QUERIES. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
In queries, using UNNEST table function, sometimes based on some
statistics, negative cost or cardinality may be seen in access
plan of queries.
Ex:
Access Plan:
-----------
Total Cost: -32.6706
Query Degree: 1
Rows
RETURN
( 1)
Cost
I/O
|
0.175684
TBSCAN
( 2)
-32.6706
NA
|
0.175684
SORT
( 3)
-32.671
NA
|
0.175684
UNION
( 4)
-32.6718
NA
/--------------------------------------------------+------------
---------------------------------------\
0.182813
-0.00712883
^NLJOIN
>^NLJOIN
( 5)
( 15)
31.2597
-63.9317
NA
NA
/--------------+--------------\
/-------------------------+-------------------------\
0.182813
21.7391
-0.00712883 1
NLJOIN
TBSCAN
NLJOIN FETCH
( 6)
( 14)
( 16) ( 50)
31.2545
0.112203
-79.072 22.7011 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users on DB2 v97 Fp4 or lower * **************************************************************** * PROBLEM DESCRIPTION: * * NEGATIVE COST OR CARDINALITY MAY BE SEEN IN ACCESS PLAN WHEN * * UNNEST TABLE FUNCTION IS USED IN QUERIES. * **************************************************************** * RECOMMENDATION: * * First Fixed in DB2 V97 fp5. * **************************************************************** | |
| Local Fix: | |
No Local Fix. | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
| Solution | |
Apply DB2 v97 Fp5 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.07.2011 19.12.2011 19.12.2011 |
| 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 |
|