|
Problem IC84497
|
Status: Geschlossen |
OPTIMIZER'S ESTIMATED CARDINALITY INCORRECTLY DROPS AT TQ OPERATOR WHEN QUERY CONTAINS NODENUMBER PREDICATE |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
If a query contains a predicate on NODENUMBER which restricts
to a single node (such as NODENUMBER(T1.C1) = <const>), the
optimizer may incorrectly reduce the estimated cardinality at
certain TQ operators in the access plan. This can potentially
lead to a suboptimal plan choice. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Any DPF users with nodenumber predicates *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fixpack 1 or later *
**************************************************************** |
| Local-Fix: |
If the TQ cardinality drops at the TQ of a base table,
replicating the base table may correct the cardinality, but
this depends on the optimizer choosing to use the replicated
table based on cost. |
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
Problem first fixed in DB2 Version 10.1 Fixpack 1 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 14.06.2012
03.12.2012
03.12.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
