DB2 - Problem description
Problem IC94377 | Status: Closed |
POSSIBLE SEGV (CRASH/TRAP) IN SQLDROWFETCH() WHEN SQL IS USING PBT(Parameterized Base Table) ACCESS IN A NESTED LOOP JOIN | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
It is possible for a SQL statement to generate a segv in sqldRowFetch() while executing a join using PBT access. The top of the stack would show the following functions: 0x090000000756256C sqldRowFetch 0x0900000007577A7C sqlriFetch 0x0900000007A767BC sqlriNljnNonPiped This problem would not happen in v9.8 and v10.1. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * It is possible for a SQL statement to generate a segv in * * sqldRowFetch() while executing * * a join using PBT access. The top of the stack would show the * * following functions: * * * * 0x090000000756256C sqldRowFetch * * 0x0900000007577A7C sqlriFetch * * 0x0900000007A767BC sqlriNljnNonPiped * * * * This problem would not happen in v9.8 and v10.1. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V101FP3 or Higher * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Fixed on DB2 V101FP3 or Higher | |
Workaround | |
N/A | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.07.2013 04.11.2013 04.11.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |