DB2 - Problem description
Problem IC87851 | Status: Closed |
DB2 MAY ABEND IN SQLNG_BUILD_SQLD_VALS_OBJ DURING SQL STATEMENT COMPILATION | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
DB2 may abend in sqlng_build_SQLD_VALS_obj during SQL statement compilation with the stack similar to following: sqlng_build_SQLD_VALS_obj sqlng_build_TA_op sqlng_process_f_ioa sqlng_process_fetch_op sqlng_process_sort_op sqlng_build_thread ..... The following conditions must be satisfied for the trap to occur 1. There exists optimizer MQT to which the query may be routed. An optimizer MQT is Materialized Query Table whose definition is plainly a SELECT statement from one base table or multiple base table joined together. 2. The query has equality join predicate Tab1.ColX = Tab2.ColY. The two columns are defined in different column types, e.g. one is CHAR(10) the other is VARCHAR(10). 3. The query has IN predicate Tab1.ColX IN (<liberal1>, <literal2>, ..., <liberalN>). The IN element list consists of literals. 4. The SELECT clause of MQT definition query contains exactly one column out of Tab1.ColX and Tab2.ColY. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10.1 Fixpak 2 * **************************************************************** | |
Local Fix: | |
Make both join columns present in MQT SELECT list. For example, if MQT definition is "SELECT Tab1.ColX...", change it to "SELECT Tab1.ColX, Tab2.ColY...". | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 V10.1 Fixpak 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.11.2012 24.04.2013 24.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.2 | |
10.5.0.2 |