|
Problem IC61510
|
Status: Closed |
INSTANCE ABEND POSSIBLE DUE TO INCORRECTION EXECUTION SECTION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
An instance may abend when copying data into a table queue under
some very specific access plan conditions.
A typical trap file may show the following functions on top in
the stacktrace :
Stack:
======================
memmove
sqlkt_pack_tuple
sqlktins
sqlritqb2
The problem is due to an incorrect buffer location being
accessed.
This can only be confirmed by db2 service personnel by
examining the "section dump" of the execution plan,
which is located in the binary dump file.
From an access plan point of view, at least the following
conditions need to be true :
* There is a star join that has a join of a dimension table
(above the IXAND operator ) that references
the same columns of the dimension table that were already
accessed in the star join (below the IXAND operator )
( this may also be referred to as a back join )
* The dimension table column that is accessed in the star join
is accessed via list prefetching
i.e. there is a RID scan operator followed by a fetch
operation on the base table.
* The index scan in the list prefetch of the dimension table
within the star join has a sargable predicate on a column that
is used in the back join. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all users with a DPF environment *
****************************************************************
* PROBLEM DESCRIPTION: *
* An instance may abend if this apar is not applied. Although *
* the conditions for triggering this problem are rare, there *
* is no easy way to predict if your workload is liable to this *
* problem. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v9.7 Fix Pack 1 *
**************************************************************** |
| Local Fix: |
There is no known workaround for this problem, other than to
force a different access plan to avoid
at least one of the above conditions. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.06.2009
22.02.2010
22.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
