RE: Informix Crash!

You did not give us much information to work from. The /tmp/af.* files and output from the $INFORMIXDIR/etc/evidence.sh script should provide relevant diagnostic information. You should open a case with Informix Technical support and send these files to them. However, the brief information, which you provided, indicates that an onmode thread was running. Do you know what the full command syntax was? We encontered a similar crash with IDS 7.30.UC7XK several months ago. An oncheck -cIw command had been running for 10 hours. Informix Technical Support said shared memory had been previously corrupted. They considered our hourly "onmode -F" commands as a likely cause. Apparently, there are several open issues with this command. They recommended that we only issue this command twice a day. We no longer issue "onmode -F" commands on days that we perform database consistency checks. Our PRD crash has not reoccurred. (Knock on wood...) Good luck. -----Original Message----- From: duffybj1@my-deja.com To: informix-list@iiug.org Sent: 6/16/00 10:26 AM Subject: Informix Crash! We suffered an Informix crash on a production server this morning, and I was wondering if any of you guys have any idea what I can do to stop this from happening again. This is the error message we got: 11:30:04 Informix Dynamic Server Version 7.31.UC4 11:30:04 Assert Failed: No Exception Handler 11:30:04 Who: Session(24, informix@crabtree, 0, 561392824) Thread(62, onmode_mon, 2173fb24, 1) File: mtex.c Line: 446 11:30:04 Results: Exception Caught. Type: MT_EX_OS, Context: mem We were able to restart the db and it has been up and running for a couple of hours now. Duff Sent via Deja.com http://www.deja.com/ Before you buy.

Rick - UC7XK => probably SAP - do you restart your work processes every so (2-4 hours) often? That's usually very effective in minimizing Virtual segment footprint as well. Tends to reduce the need for onmode -F greatly. greg "Bernstein, Rick" wrote: > You did not give us much information to work from. > The /tmp/af.* files and output from the $INFORMIXDIR/etc/evidence.sh > script should provide relevant diagnostic information. You should open > a case with Informix Technical support and send these files to them. > > However, the brief information, which you provided, indicates that an > onmode thread was running. Do you know what the full command syntax was? > We encontered a similar crash with IDS 7.30.UC7XK several months ago. > An oncheck -cIw command had been running for 10 hours. Informix > Technical Support said shared memory had been previously corrupted. > They considered our hourly "onmode -F" commands as a likely cause. > Apparently, there are several open issues with this command. > They recommended that we only issue this command twice a day. > We no longer issue "onmode -F" commands on days that we perform database > consistency checks. Our PRD crash has not reoccurred. (Knock on wood...) > > Good luck. > > -----Original Message----- > From: duffybj1@my-deja.com > To: informix-list@iiug.org > Sent: 6/16/00 10:26 AM > Subject: Informix Crash! > > We suffered an Informix crash on a production server this morning, and > I was wondering if any of you guys have any idea what I can do to stop > this from happening again. > > This is the error message we got: > 11:30:04 Informix Dynamic Server Version 7.31.UC4 > > 11:30:04 Assert Failed: No Exception Handler > 11:30:04 Who: Session(24, informix@crabtree, 0, 561392824) > Thread(62, onmode_mon, 2173fb24, 1) > File: mtex.c Line: 446 > 11:30:04 Results: Exception Caught. Type: MT_EX_OS, Context: mem> > We were able to restart the db and it has been up and running for a > couple of hours now. > > Duff > > Sent via Deja.com http://www.deja.com/ > Before you buy.