Informix - Problem description
Problem IT41351 | Status: Closed |
HASH JOINS REQUIRING OVERFLOW NOW FAILING WITH -208 | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem description: | |
After upgrade to 14.10.xC4W1 (or 12.10.xC14) and newer, hash joins that so far ran well can now fail with error -208. Trapping the error would show the join in following stack: afstack afhandler affail_interface check_traperror sqerr ha_insrt_hashtab_or_ovrfl_page hjoin_open producer_thread startup With hash joins so far relying on PSORT_DBTEMP setting, this might appear as though PSORT_DBTEMP didn't work any more - which is true only indirectly. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server 12.10.xC14+ and 14.10.xC4W1+. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC16 (if available) or * * 14.10.xC9. * **************************************************************** | |
Local Fix: | |
Turn on (add) flag 0x10000000 in onconfig SQL_DEF_CTRL parameter to get back the old behavior (first determine its current value using 'onstat -g cfg SQ_DEF_CTRL). | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server 12.10.xC14+ and 14.10.xC4W1+. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC16 (if available) or * * 14.10.xC9. * **************************************************************** | |
Comment | |
Fixed in Informix Server 12.10.xC16 and 14.10.xC9. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.06.2022 04.10.2022 04.10.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |