Informix - Problem description
Problem IT12944 | Status: Closed |
ASSERT SEGV IN RSIDXSCAN_READ CAN HAPPEN WHEN USING MULTI INDEX SCAN | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
A typical stack is: (oninit) afstack (oninit) mt_ex_throw_sig (oninit) afsig_handler (Linux) (oninit) rsidxscan_read (oninit) fmh_idxscan_read (oninit) pull_eq (oninit) pull (oninit) pull_and (oninit) pull (oninit) fill_result_buf (oninit) rmap_fetch (oninit) readmidx (oninit) gettupl (oninit) scan_next (oninit) join_next (oninit) join_next (oninit) getrow (oninit) fetchrow (oninit) exfetch (oninit) sql_nfetch (oninit) sq_nfetch (oninit) sqmain (oninit) spawn_thread (oninit) th_init_initgls (oninit) startup | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of 12.10.xC1 through 12.10.xC6, and 11.70.xC1 through * * 11.70.xC8. * **************************************************************** * PROBLEM DESCRIPTION: * * A query using multi-index scan may result in assertion * * failure under the following conditions: * * - a multi-index scan is used to access a table in the * * query, i.e. tab1 * * - one of the index scans uses a "!=" predicate, i.e., * * tab1.col1 != "" * * - the column referenced, col1, is NOT a character column, * * rather it's numeric, e.g. integer, float, decimal, etc * * - the predicate uses a NULL string "" as the right hand * * side of the predicate * * - tab1 has an index with col1 as lead index column (such * * that an index scan is used as part of multi-index scan) * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC7 * **************************************************************** | |
Local Fix: | |
Presumably, a workaround would be to set onconfig MULTI_INDEX_SCAN to 0. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.12.2015 28.06.2016 28.06.2016 |
Problem solved at the following versions (IBM BugInfos) | |
12.10.xC7 | |
Problem solved according to the fixlist(s) of the following version(s) |