| Latest versions | fixlist |
| 14.10.xC10 |
 |
| 12.10.xC16.X5 |
|
| 11.70.xC9.XB |
|
| 11.50.xC9.X2 |
|
| 11.10.xC3.W5 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
Informix - Problem description
| Problem IT15283 | Status: Closed |
USING A BAD INDEX IN A QUERY CAN LEAD TO AN ASSERTION IN QUERY BIN FMFTOPEN() | |
| product: | |
IBM IDS ENTRP E / 5724L2304 / B15 - IDS 11.50 | |
| Problem description: | |
Opening a cursor in a session which accessed a Bad Index in one
of the previous executed statements may cause an exception in
the Server reporting the the following
stack :
21:37:01 Assert Failed: No Exception Handler
21:37:01 IBM Informix Dynamic Server Version 11.70.FC6
21:37:01 Who: Session(5463928, informix@server, 9208,
0x46fccfc08)
Thread(5652939, sqlexec, 46fcb7760, 1)
File: mtex.c Line: 490
21:37:01 Results: Exception Caught. Type: MT_EX_OS, Context:
mem
21:37:01 Action: Please notify IBM Informix Technical Support.
21:37:01 See Also:
/applikation/installed/informix/tmp/af.45b37f6d,
shmem.45b37f6d.0
(oninit) afstack
(oninit) mt_ex_throw_sig
(oninit) afsig_handler
(Linux)
(oninit) fmftopen_with_child
(oninit) fmftopen
(oninit) prepselect
(oninit) open_cursor
(oninit) sql_open
(oninit) sq_open
(oninit) sqmain
(oninit) spawn_thread
(oninit) startup | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * production environment * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 11.50.xC10 * **************************************************************** | |
| Local Fix: | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.05.2016 15.06.2017 15.06.2017 |
| Problem solved at the following versions (IBM BugInfos) | |
11.50.xC10 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
