Results: Exception Caught. Type: MT_EX_OS, Context

Posted in 2007

Topics: Error Codes & Troubleshooting, Logging & Checkpoints, Platform-Specific Issues, Internationalization & Character Sets

FRANK — Mon, 30 Jul 2007 19:22:03 — source: IIUG Forums & Mailing Lists

HI, We suffered a crash on production this weekend( see below). One of my question is, what does the "Results: Exception Caught. Type: MT_EX_OS, Context: mem" mean? I appreciate if you have more ideas. Build Version: 10.00.UC5 Build Number: N202 Build Host: ibm6c1b Build OS: AIX 5.2 Build Date: Thu May 18 00:09:08 CDT 2006 GLS Version: glslib-4.00.UC8 Thanks, Frank 04:17:28 Fuzzy Checkpoint Completed: duration was 3 seconds, 2170 buffers not flushed. 04:17:28 Checkpoint loguniq 26363, logpos 0x4327900, timestamp: 0xa43e3d77 04:17:28 Maximum server connections 106 04:17:44 stack trace for pid 245784 written to /tmp/af.20bdc367 04:17:44 Assert Failed: No Exception Handler 04:17:44 IBM Informix Dynamic Server Version 10.00.UC5 04:17:44 Who: Session(15384579, informix@erika, 364862, b031de00) Thread(15408341, sqlexec, b030947c, 1) File: mtex.c Line: 472 04:17:44 Results: Exception Caught. Type: MT_EX_OS, Context: mem 04:17:44 Action: Please notify IBM Informix Technical Support. 04:17:44 stack trace for pid 245784 written to /tmp/af.20bdc367 04:17:44 See Also: /tmp/af.20bdc367, shmem.20bdc367.0 04:17:54 stack trace for pid 409870 written to /tmp/af.207dc371 04:17:54 Assert Failed: No Exception Handler 04:17:54 IBM Informix Dynamic Server Version 10.00.UC5 04:17:54 Who: Session(15384582, saapmgr@kate-dat, 1568930, b0314dc8) Thread(15408277, sqlexec, b0300c38, 1) File: mtex.c Line: 472 04:17:54 Results: Exception Caught. Type: MT_EX_OS, Context: mem 04:17:54 Action: Please notify IBM Informix Technical Support. 04:17:54 stack trace for pid 409870 written to /tmp/af.207dc371 04:17:54 See Also: /tmp/af.207dc371, shmem.207dc371.0 04:19:26 Error writing '/tmp/shmem.207dc371.0' errno = 28 04:19:26 Error writing '/tmp/shmem.20bdc367.0' errno = 28 04:19:28 mtex.c, line 472, thread 15408277, proc id 409870, No Exception Handler. 04:19:28 mtex.c, line 472, thread 15408341, proc id 245784, No Exception Handler. 04:19:37 Fatal error in ADM VP at mt.c:13055 04:19:38 Unexpected virtual processor termination, pid = 409870, exit = 0x100 04:19:38 invoke_alarm(): /bin/sh -c '/dbbackup/logbackup/EventAlarm.pl 5 6 "Internal Subsystem failure: 'MT'" "Unexpected virtual processor termination, pid = 409870, exit = 0x100 " ' 04:19:38 invoke_alarm(): mt_exec failed, status 65280, errno 0 04:19:38 PANIC: Attempting to bring system down

↪ replying to FRANK

ART KAGEL, — Mon, 30 Jul 2007 19:47:24 — source: IIUG Forums & Mailing Lists

An internal error within the server code was caught by an exception handler which possibly core dumped and shut the engine down to prevent collateral damage to your data. The error was in some memory handling subsystem the details of which are only interesting to the server developers. Art S. Kagel ----- Original Message ----- From: Frank <ids@iiug.org> At: 7/30 15:22:38 HI, We suffered a crash on production this weekend( see below). One of my question is, what does the "Results: Exception Caught. Type: MT_EX_OS, Context: mem" mean? I appreciate if you have more ideas. Build Version: 10.00.UC5 Build Number: N202 Build Host: ibm6c1b Build OS: AIX 5.2 Build Date: Thu May 18 00:09:08 CDT 2006 GLS Version: glslib-4.00.UC8 Thanks, Frank 04:17:28 Fuzzy Checkpoint Completed: duration was 3 seconds, 2170 buffers not flushed. 04:17:28 Checkpoint loguniq 26363, logpos 0x4327900, timestamp: 0xa43e3d77 04:17:28 Maximum server connections 106 04:17:44 stack trace for pid 245784 written to /tmp/af.20bdc367 04:17:44 Assert Failed: No Exception Handler 04:17:44 IBM Informix Dynamic Server Version 10.00.UC5 04:17:44 Who: Session(15384579, informix@erika, 364862, b031de00) Thread(15408341, sqlexec, b030947c, 1) File: mtex.c Line: 472 04:17:44 Results: Exception Caught. Type: MT_EX_OS, Context: mem 04:17:44 Action: Please notify IBM Informix Technical Support. 04:17:44 stack trace for pid 245784 written to /tmp/af.20bdc367 04:17:44 See Also: /tmp/af.20bdc367, shmem.20bdc367.0 04:17:54 stack trace for pid 409870 written to /tmp/af.207dc371 04:17:54 Assert Failed: No Exception Handler 04:17:54 IBM Informix Dynamic Server Version 10.00.UC5 04:17:54 Who: Session(15384582, saapmgr@kate-dat, 1568930, b0314dc8) Thread(15408277, sqlexec, b0300c38, 1) File: mtex.c Line: 472 04:17:54 Results: Exception Caught. Type: MT_EX_OS, Context: mem 04:17:54 Action: Please notify IBM Informix Technical Support. 04:17:54 stack trace for pid 409870 written to /tmp/af.207dc371 04:17:54 See Also: /tmp/af.207dc371, shmem.207dc371.0 04:19:26 Error writing '/tmp/shmem.207dc371.0' errno = 28 04:19:26 Error writing '/tmp/shmem.20bdc367.0' errno = 28 04:19:28 mtex.c, line 472, thread 15408277, proc id 409870, No Exception Handler. 04:19:28 mtex.c, line 472, thread 15408341, proc id 245784, No Exception Handler. 04:19:37 Fatal error in ADM VP at mt.c:13055 04:19:38 Unexpected virtual processor termination, pid = 409870, exit = 0x100 04:19:38 invoke_alarm(): /bin/sh -c '/dbbackup/logbackup/EventAlarm.pl 5 6 "Internal Subsystem failure: 'MT'" "Unexpected virtual processor termination, pid = 409870, exit = 0x100 " ' 04:19:38 invoke_alarm(): mt_exec failed, status 65280, errno 0 04:19:38 PANIC: Attempting to bring system down ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to ART KAGEL,

FRANK — Mon, 30 Jul 2007 20:01:26 — source: IIUG Forums & Mailing Lists

Thanks, Art! I am curious and thinking what caused the problem.. Any typical experience? Frank On 7/30/07, ART KAGEL, BLOOMBERG/ 731 LEXIN <kagel@bloomberg.net> wrote: > > An internal error within the server code was caught by an exception > handler > which possibly core dumped and shut the engine down to prevent collateral > damage to your data. The error was in some memory handling subsystem the > details of which are only interesting to the server developers. > > Art S. Kagel > > ----- Original Message ----- > From: Frank <ids@iiug.org> > At: 7/30 15:22:38 > > HI, > > We suffered a crash on production this weekend( see below). > > One of my question is, > what does the "Results: Exception Caught. Type: MT_EX_OS, Context: mem" > mean? > > I appreciate if you have more ideas. > > Build Version: 10.00.UC5 > Build Number: N202 > Build Host: ibm6c1b > Build OS: AIX 5.2 > Build Date: Thu May 18 00:09:08 CDT 2006 > GLS Version: glslib-4.00.UC8 > > Thanks, > Frank > > 04:17:28 Fuzzy Checkpoint Completed: duration was 3 seconds, 2170 buffers > not flushed. > 04:17:28 Checkpoint loguniq 26363, logpos 0x4327900, timestamp: 0xa43e3d77 > > 04:17:28 Maximum server connections 106 > 04:17:44 stack trace for pid 245784 written to /tmp/af.20bdc367 > 04:17:44 Assert Failed: No Exception Handler > 04:17:44 IBM Informix Dynamic Server Version 10.00.UC5 > 04:17:44 Who: Session(15384579, informix@erika, 364862, b031de00) > > Thread(15408341, sqlexec, b030947c, 1) > > File: mtex.c Line: 472 > 04:17:44 Results: Exception Caught. Type: MT_EX_OS, Context: mem > 04:17:44 Action: Please notify IBM Informix Technical Support. > 04:17:44 stack trace for pid 245784 written to /tmp/af.20bdc367 > 04:17:44 See Also: /tmp/af.20bdc367, shmem.20bdc367.0 > 04:17:54 stack trace for pid 409870 written to /tmp/af.207dc371 > 04:17:54 Assert Failed: No Exception Handler > 04:17:54 IBM Informix Dynamic Server Version 10.00.UC5 > 04:17:54 Who: Session(15384582, saapmgr@kate-dat, 1568930, b0314dc8) > > Thread(15408277, sqlexec, b0300c38, 1) > > File: mtex.c Line: 472 > 04:17:54 Results: Exception Caught. Type: MT_EX_OS, Context: mem > 04:17:54 Action: Please notify IBM Informix Technical Support. > 04:17:54 stack trace for pid 409870 written to /tmp/af.207dc371 > 04:17:54 See Also: /tmp/af.207dc371, shmem.207dc371.0 > 04:19:26 Error writing '/tmp/shmem.207dc371.0' errno = 28 > 04:19:26 Error writing '/tmp/shmem.20bdc367.0' errno = 28 > 04:19:28 mtex.c, line 472, thread 15408277, proc id 409870, No Exception > Handler. > 04:19:28 mtex.c, line 472, thread 15408341, proc id 245784, No Exception > Handler. > 04:19:37 Fatal error in ADM VP at mt.c:13055 > 04:19:38 Unexpected virtual processor termination, pid = 409870, exit = > 0x100 > > 04:19:38 invoke_alarm(): /bin/sh -c '/dbbackup/logbackup/EventAlarm.pl 5 6 > "Internal Subsystem failure: 'MT'" > "Unexpected virtual processor termination, pid = 409870, exit = 0x100 > " ' > 04:19:38 invoke_alarm(): mt_exec failed, status 65280, errno 0 > 04:19:38 PANIC: Attempting to bring system down > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >

↪ replying to FRANK

ART KAGEL, — Mon, 30 Jul 2007 20:13:11 — source: IIUG Forums & Mailing Lists

Most likely, you've run into a bug. Contact tech support to see if there's a patch for it. Art S. Kagel ----- Original Message ----- From: Frank <ids@iiug.org> At: 7/30 16:02:11 Thanks, Art! I am curious and thinking what caused the problem.. Any typical experience? Frank On 7/30/07, ART KAGEL, BLOOMBERG/ 731 LEXIN <kagel@bloomberg.net> wrote: > > An internal error within the server code was caught by an exception > handler > which possibly core dumped and shut the engine down to prevent collateral > damage to your data. The error was in some memory handling subsystem the > details of which are only interesting to the server developers. > > Art S. Kagel > > ----- Original Message ----- > From: Frank <ids@iiug.org> > At: 7/30 15:22:38 > > HI, > > We suffered a crash on production this weekend( see below). > > One of my question is, > what does the "Results: Exception Caught. Type: MT_EX_OS, Context: mem" > mean? > > I appreciate if you have more ideas. > > Build Version: 10.00.UC5 > Build Number: N202 > Build Host: ibm6c1b > Build OS: AIX 5.2 > Build Date: Thu May 18 00:09:08 CDT 2006 > GLS Version: glslib-4.00.UC8 > > Thanks, > Frank > > 04:17:28 Fuzzy Checkpoint Completed: duration was 3 seconds, 2170 buffers > not flushed. > 04:17:28 Checkpoint loguniq 26363, logpos 0x4327900, timestamp: 0xa43e3d77 > > 04:17:28 Maximum server connections 106 > 04:17:44 stack trace for pid 245784 written to /tmp/af.20bdc367 > 04:17:44 Assert Failed: No Exception Handler > 04:17:44 IBM Informix Dynamic Server Version 10.00.UC5 > 04:17:44 Who: Session(15384579, informix@erika, 364862, b031de00) > > Thread(15408341, sqlexec, b030947c, 1) > > File: mtex.c Line: 472 > 04:17:44 Results: Exception Caught. Type: MT_EX_OS, Context: mem > 04:17:44 Action: Please notify IBM Informix Technical Support. > 04:17:44 stack trace for pid 245784 written to /tmp/af.20bdc367 > 04:17:44 See Also: /tmp/af.20bdc367, shmem.20bdc367.0 > 04:17:54 stack trace for pid 409870 written to /tmp/af.207dc371 > 04:17:54 Assert Failed: No Exception Handler > 04:17:54 IBM Informix Dynamic Server Version 10.00.UC5 > 04:17:54 Who: Session(15384582, saapmgr@kate-dat, 1568930, b0314dc8) > > Thread(15408277, sqlexec, b0300c38, 1) > > File: mtex.c Line: 472 > 04:17:54 Results: Exception Caught. Type: MT_EX_OS, Context: mem > 04:17:54 Action: Please notify IBM Informix Technical Support. > 04:17:54 stack trace for pid 409870 written to /tmp/af.207dc371 > 04:17:54 See Also: /tmp/af.207dc371, shmem.207dc371.0 > 04:19:26 Error writing '/tmp/shmem.207dc371.0' errno = 28 > 04:19:26 Error writing '/tmp/shmem.20bdc367.0' errno = 28 > 04:19:28 mtex.c, line 472, thread 15408277, proc id 409870, No Exception > Handler. > 04:19:28 mtex.c, line 472, thread 15408341, proc id 245784, No Exception > Handler. > 04:19:37 Fatal error in ADM VP at mt.c:13055 > 04:19:38 Unexpected virtual processor termination, pid = 409870, exit = > 0x100 > > 04:19:38 invoke_alarm(): /bin/sh -c '/dbbackup/logbackup/EventAlarm.pl 5 6 > "Internal Subsystem failure: 'MT'" > "Unexpected virtual processor termination, pid = 409870, exit = 0x100 > " ' > 04:19:38 invoke_alarm(): mt_exec failed, status 65280, errno 0 > 04:19:38 PANIC: Attempting to bring system down > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Glossary

checkpoint