DB2 - Problem description
Problem IT34026 | Status: Closed |
INSTANCE COULD GO DOWN WHEN DOING A FULL OUTER JOIN ON TWO COLUMNAR ORGANIZED TABLES WITH NULL COLUMNS | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Instance could go down when doing a FULL OUTER JOIN on two Columnar organized tables with NULL columns Stack for this issue will look like this and coul dbe reported as a memory corruption in db2diag.log (diagnoseMemoryCorruptionAndCrash/sqloDiagnoseFreeBlockFailure): 7 ibm_cde::services::Heap::freeMem 8 ibm_cde::services::ManagedArray::~ManagedArray 9 void ibm_cde::query::GetJoinPayloadEvaluator::getJoinPayloads_Partiti oned_Fast | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Columnar Full Outer Join Queries Only. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2_v115m5fp0 or later * **************************************************************** | |
Local Fix: | |
Turn Columnar support for Full Outer Join using this registry variable: db2set DB2_EXTENDED_OPTIMIZATION="FOHSJN OFF" this registry variable will change Access Plan. Static Sections need to be recompiled. | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Columnar Full Outer Join Queries Only. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2_v115m5fp0 or later * **************************************************************** | |
Comment | |
Upgrade to db2_v115m5fp0 or later | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2020 19.11.2020 19.11.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |