Exception Caught. Type: MT_EX_OS, Context: mem

[ids2000]

Hi everybody,
recently I had one of my engines bounced for an exception caught in one of my userthreads.
Unfortunately, this happened again today and I have to explain the causes for the bouncing.
Here is the Assert Failure generated:

19:27:12 Assert Failed: No Exception Handler
19:27:12 Informix Dynamic Server Version 7.30.TC9
19:27:12 Who: Session(299830, apontala@aa004094.vcp.advcp.br, 217, 0)
Thread(315234, sqlexec, 0, 1)
Exception at Addr: 0x77f7d32f, TOS: 0x31177f8c, FP:0x31177fa8, Exc: c0000005
19:27:12 Results: Exception Caught. Type: MT_EX_OS, Context: mem

Informix technical support team gives me always the same answer: we can't tell what caused the bouncing only with these informations.
This is an Windows 2000 enviroment and the Event Viewer has brought nothing.
Another informations from this session can be paste here if anyone could help me.

Thanks,


FFO
"The only way of knowing is to understand"

 

[WiccaChic]

Do you have a log that you can refer back to in order to determine who/what process ID=299830? Then maybe if its a general issue you can recreate and monitor the culprit.

I know how you feel, I have found this forum MUCH more helpful than IBM support with basic troubleshooting.

 

[vpshriyan]

Hi,

An internal problem within an IDS may shore-up in form of an assertion failure. It shows what type of problem, which session-id is responsible, when it was occurred, and where the finer details were dumped along with circumstantial evidences.

One of the easiest way for gathering an ample information relevant to the failure is through the evidence.sh script. The database server must be set with the parameter SYSALARMPROGRAM with $INFORMIXDIR/etc/evidence.sh

This shell script is executed by the db server during an assertion failure event. It largely dumps status of onstat with different switches passed on at the time of a failure. The output of this script is dumped in what is commonly called an af file.

The analysis of af file and shared memory dump file, often, get into the identification of a known bug or even uncover a previously unidentified problem in the database server engine.

Regards,
Shriyan
"Good ideas do not drop into closed minds."

 

[ids2000]

Hi guys,
technical support discovered a bug on:

Informix Dynamic Server Version 7.30.TC9

We have been tremendously adviced to move to 7.31.TD2.

Thanks anyway.



FFO
"The only way of knowing is to understand"