Informix 7.3 Engine keeps going down when accessing a table

Everytime we try to access a particular table including an attempt to drop that table this is the error: 14:30:51 Assert Failed: No Exception Handler 14:30:51 Informix Dynamic Server Version 7.30.UC2 14:30:51 Who: Session(21, informix@emco1, 1983, 0) Thread(104, sqlexec, 0, 1) File: mtex.c Line: 314 14:30:51 Results: Exception Caught. Type: MT_EX_OS, Context: fpe 14:30:51 Action: Please notify Informix Technical Support. 14:30:56 See Also: /tmp/af.6851db 14:30:56 mtex.c, line 314, thread 104, proc id 1496, No Exception Handler. 14:30:56 PANIC: Attempting to bring system down 14:31:19 Segment locked: addr=0x82000000, size=704643072 Even compiling the program that access the table causes the engine to go down. We also tried to rename the table, same error. Thanks Gary Quiring A snip from /tmp/af.6851db: 08:14:30 Assert Failed: No Exception Handler 08:14:30 Who: Session(21, informix@emco1, 1983, 0) Thread(104, sqlexec, 0, 1) File: mtex.c Line: 314 08:14:30 Results: Exception Caught. Type: MT_EX_OS, Context: fpe 08:14:30 Action: Please notify Informix Technical Support. --------------------------------- Begin System Alarm Program Output --------------------------------- Assertion Failure Type: CRASH Host Name: emco1 Database Server Name: emco1_shm Time of failure: Tue Aug 8 14:30:52 EDT 2000 AF file: /tmp/af.6851db Shared memory file: None System Blocking: OFF ===========------------- - - - - - - tail -100 /u/ifmx/online.log: Thread(0, idle, 0, 30) File: mtex.c Line: 314 14:18:45 Action: Please notify Informix Technical Support. 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill 14:18:45 Action: Please notify Informix Technical Support. 14:18:45 Action: Please notify Informix Technical Support. 14:18:45 Who: Session(0, @, 0, 0) Thread(0, idle, 0, 32) File: mtex.c Line: 314 14:18:45 Action: Please notify Informix Technical Support. 14:18:45 Who: Session(1, root@emco1, 0, 0) Thread(0, idle, 0, 10) File: mtex.c Line: 314 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill 14:18:45 Action: Please notify Informix Technical Support. 14:18:45 Action: Please notify Informix Technical Support. 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill 14:18:45 Action: Please notify Informix Technical Support. 14:18:47 See Also: /tmp/af.4f04 14:18:47 mtex.c, line 314, thread 0, proc id 29025, No Exception Handler. 14:18:47 PANIC: Attempting to bring system down 14:19:24 Segment locked: addr=0x82000000, size=704643072 Tue Aug 8 14:19:26 2000 14:19:26 Event alarms enabled. ALARMPROG = '/u/ifmx/etc/no_log.sh' 14:19:31 DR: DRAUTO is 0 (Off) 14:19:31 Requested shared memory segment size rounded from 2132KB to4096KB 14:19:31 Requested shared memory segment size rounded from 2132KB to4096KB 14:19:32 Informix Dynamic Server Version 7.30.UC2 Software Serial Number AAC#J493945 14:19:37 Informix Dynamic Server Initialized -- Shared Memory Initialized. 14:19:37 Physical Recovery Started. 14:19:37 Physical Recovery Complete: 0 Pages Restored. 14:19:37 Logical Recovery Started. 14:19:40 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks 14:19:40 Dataskip is now OFF for all dbspaces 14:19:40 Quiescent Mode 14:19:40 Checkpoint Completed: duration was 0 seconds. 14:20:21 shmget: [EEXIST][17]: key 52564801: shared memory already exists 14:20:21 mt_shm_init: can't create resident segment 14:23:43 Segment locked: addr=0x82000000, size=704643072 Tue Aug 8 14:23:45 2000

Gary, The portion of the af file that is most needed in determining the problem is left out of your email. That is the actual stack trace. The problem that you are running into "fpe" of course stands for Floating Point Error. That *often* indicates an attempt to divide by zero. By seeing the stack trace, we might could offer some workarround the issue until we knew exactly what was causing the failure. Please open a case with tech support as soon as possible. Thanks Gary Quiring wrote: > Everytime we try to access a particular table including an attempt to drop > that table this is the error: > > 14:30:51 Assert Failed: No Exception Handler > 14:30:51 Informix Dynamic Server Version 7.30.UC2 > 14:30:51 Who: Session(21, informix@emco1, 1983, 0) > Thread(104, sqlexec, 0, 1) > File: mtex.c Line: 314 > 14:30:51 Results: Exception Caught. Type: MT_EX_OS, Context: fpe > 14:30:51 Action: Please notify Informix Technical Support. > 14:30:56 See Also: /tmp/af.6851db > 14:30:56 mtex.c, line 314, thread 104, proc id 1496, No Exception Handler. > 14:30:56 PANIC: Attempting to bring system down > 14:31:19 Segment locked: addr=0x82000000, size=704643072> > Even compiling the program that access the table causes the engine to go > down. We also tried to rename the table, same error. > > Thanks > Gary Quiring > > A snip from /tmp/af.6851db: > > 08:14:30 Assert Failed: No Exception Handler > 08:14:30 Who: Session(21, informix@emco1, 1983, 0) > Thread(104, sqlexec, 0, 1) > File: mtex.c Line: 314 > 08:14:30 Results: Exception Caught. Type: MT_EX_OS, Context: fpe > 08:14:30 Action: Please notify Informix Technical Support.> > --------------------------------- > Begin System Alarm Program Output > --------------------------------- > > Assertion Failure Type: CRASH > Host Name: emco1 > Database Server Name: emco1_shm > Time of failure: Tue Aug 8 14:30:52 EDT 2000 > AF file: /tmp/af.6851db > Shared memory file: None > System Blocking: OFF > > ===========------------- - - - - - - > tail -100 /u/ifmx/online.log: > > Thread(0, idle, 0, 30) > File: mtex.c Line: 314 > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Who: Session(0, @, 0, 0) > Thread(0, idle, 0, 32) > File: mtex.c Line: 314 > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Who: Session(1, root@emco1, 0, 0) > Thread(0, idle, 0, 10) > File: mtex.c Line: 314 > 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill > 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:47 See Also: /tmp/af.4f04 > 14:18:47 mtex.c, line 314, thread 0, proc id 29025, No Exception Handler. > 14:18:47 PANIC: Attempting to bring system down > 14:19:24 Segment locked: addr=0x82000000, size=704643072> > Tue Aug 8 14:19:26 2000 > > 14:19:26 Event alarms enabled. ALARMPROG = '/u/ifmx/etc/no_log.sh' > 14:19:31 DR: DRAUTO is 0 (Off) > 14:19:31 Requested shared memory segment size rounded from 2132KB to> 4096KB > 14:19:31 Requested shared memory segment size rounded from 2132KB to> 4096KB > 14:19:32 Informix Dynamic Server Version 7.30.UC2 Software Serial Number > AAC#> J493945 > 14:19:37 Informix Dynamic Server Initialized -- Shared Memory Initialized. > 14:19:37 Physical Recovery Started. > 14:19:37 Physical Recovery Complete: 0 Pages Restored. > 14:19:37 Logical Recovery Started. > 14:19:40 Logical Recovery Complete.> 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks > > 14:19:40 Dataskip is now OFF for all dbspaces > 14:19:40 Quiescent Mode > 14:19:40 Checkpoint Completed: duration was 0 seconds. > 14:20:21 shmget: [EEXIST][17]: key 52564801: shared memory already exists > 14:20:21 mt_shm_init: can't create resident segment > > 14:23:43 Segment locked: addr=0x82000000, size=704643072> > Tue Aug 8 14:23:45 2000 -- Madison Pruet =========================================== Enterprise Replication Product Developement Dallas, Texas Informix Software ===========================================

Open a tech support case. Since this is repeatable they can at worst compile a debuggable engine, tell you what traces to turn on and have you run the crash again to gather the data they need to fix the problem. Art S. Kagel Gary Quiring wrote: > > Everytime we try to access a particular table including an attempt to drop > that table this is the error: > > 14:30:51 Assert Failed: No Exception Handler > 14:30:51 Informix Dynamic Server Version 7.30.UC2 > 14:30:51 Who: Session(21, informix@emco1, 1983, 0) > Thread(104, sqlexec, 0, 1) > File: mtex.c Line: 314 > 14:30:51 Results: Exception Caught. Type: MT_EX_OS, Context: fpe > 14:30:51 Action: Please notify Informix Technical Support. > 14:30:56 See Also: /tmp/af.6851db > 14:30:56 mtex.c, line 314, thread 104, proc id 1496, No Exception Handler. > 14:30:56 PANIC: Attempting to bring system down > 14:31:19 Segment locked: addr=0x82000000, size=704643072> > Even compiling the program that access the table causes the engine to go > down. We also tried to rename the table, same error. > > Thanks > Gary Quiring > > A snip from /tmp/af.6851db: > > 08:14:30 Assert Failed: No Exception Handler > 08:14:30 Who: Session(21, informix@emco1, 1983, 0) > Thread(104, sqlexec, 0, 1) > File: mtex.c Line: 314 > 08:14:30 Results: Exception Caught. Type: MT_EX_OS, Context: fpe > 08:14:30 Action: Please notify Informix Technical Support.> > --------------------------------- > Begin System Alarm Program Output > --------------------------------- > > Assertion Failure Type: CRASH > Host Name: emco1 > Database Server Name: emco1_shm > Time of failure: Tue Aug 8 14:30:52 EDT 2000 > AF file: /tmp/af.6851db > Shared memory file: None > System Blocking: OFF > > ===========------------- - - - - - - > tail -100 /u/ifmx/online.log: > > Thread(0, idle, 0, 30) > File: mtex.c Line: 314 > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Who: Session(0, @, 0, 0) > Thread(0, idle, 0, 32) > File: mtex.c Line: 314 > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Who: Session(1, root@emco1, 0, 0) > Thread(0, idle, 0, 10) > File: mtex.c Line: 314 > 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill > 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:45 Results: Exception Caught. Type: MT_EX_OS, Context: ill > 14:18:45 Action: Please notify Informix Technical Support. > 14:18:47 See Also: /tmp/af.4f04 > 14:18:47 mtex.c, line 314, thread 0, proc id 29025, No Exception Handler. > 14:18:47 PANIC: Attempting to bring system down > 14:19:24 Segment locked: addr=0x82000000, size=704643072> > Tue Aug 8 14:19:26 2000 > > 14:19:26 Event alarms enabled. ALARMPROG = '/u/ifmx/etc/no_log.sh' > 14:19:31 DR: DRAUTO is 0 (Off) > 14:19:31 Requested shared memory segment size rounded from 2132KB to> 4096KB > 14:19:31 Requested shared memory segment size rounded from 2132KB to> 4096KB > 14:19:32 Informix Dynamic Server Version 7.30.UC2 Software Serial Number > AAC#> J493945 > 14:19:37 Informix Dynamic Server Initialized -- Shared Memory Initialized. > 14:19:37 Physical Recovery Started. > 14:19:37 Physical Recovery Complete: 0 Pages Restored. > 14:19:37 Logical Recovery Started. > 14:19:40 Logical Recovery Complete.> 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks > > 14:19:40 Dataskip is now OFF for all dbspaces > 14:19:40 Quiescent Mode > 14:19:40 Checkpoint Completed: duration was 0 seconds. > 14:20:21 shmget: [EEXIST][17]: key 52564801: shared memory already exists > 14:20:21 mt_shm_init: can't create resident segment > > 14:23:43 Segment locked: addr=0x82000000, size=704643072> > Tue Aug 8 14:23:45 2000