IT12944: ASSERT SEGV IN RSIDXSCAN_READ CAN HAPPEN WHEN USING MULTI INDEX SCAN

APAR status

• Closed as program error.

Error description

• A typical stack is:
  
  (oninit) afstack
  (oninit) mt_ex_throw_sig
  (oninit) afsig_handler
  (Linux) <signal frame>
  (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
  

Local fix

• Presumably, a workaround would be to set onconfig
  MULTI_INDEX_SCAN to 0.
  

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                      *
  ****************************************************************
  

Problem conclusion

• Problem Fixed In IBM Informix Server 12.10.xC7
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  INFORMIX SERVER

• Fixed component ID

  5725A3900

Applicable component levels

• RB70 PSN

     UP

• RC10 PSN

     UP