IDS 7.31UD1 on Solaris8
Posted in 2007
Topics: Installation, Setup & Upgrades, Error Codes & Troubleshooting, Platform-Specific Issues, Versions, Editions & End-of-Life
Hello, A few months ago, I installed IDS 7.31UD1 on a Solaris8 server. Untill now the server was not used very often, but we are supposed to put it in production within a few weeks. Since a few days now, every morning at 06:30 the server crashes with the following messages: 06:30:00 Assert Failed: No Exception Handler 06:30:00 Informix Dynamic Server Version 7.31.UD1 06:30:00 Who: Session(13, informix@, 0, 0) Thread(9, tlitcplst, 0, 1) File: mtex.c Line: 446 06:30:00 Results: Exception Caught. Type: MT_EX_OS, Context: mem 06:30:00 Action: Please notify Informix Technical Support. 06:30:11 See Also: /var/tmp/af.3f17d58 06:30:11 mtex.c, line 446, thread 9, proc id 11630, No Exception Handler. 06:30:11 PANIC: Attempting to bring system down The config hasn't changed. I checked the crontabs: nothing is executed at that hour. Does anyone have an idea where this might come from? Thanks. Kurt Van Gompel.
Kurt, You may want to check that solaris 8 and IDS 7.31 are still supported.... It sounds like the problem we had several years back.... Mutex-exclusive lock waits..... As unusual as it is, I think it turned out to be an informix bug on that platform..... You may need to upgrade your informix ..... Luckily that is a very easy and quick thing to do in most cases..... Should be for you since are not in production yet..... ask informix tech support to confirm. I will see if I stiill have my doc of when we upgraded or patched informix (and the reasons). NormaJean Sebastian via bberry ----- Original Message ----- From: ids-bounces@iiug.org <ids-bounces@iiug.org> To: ids@iiug.org <ids@iiug.org> Sent: Mon Dec 10 07:14:49 2007 Subject: IDS 7.31UD1 on Solaris8 [10667] Hello, A few months ago, I installed IDS 7.31UD1 on a Solaris8 server. Untill now the server was not used very often, but we are supposed to put it in production within a few weeks. Since a few days now, every morning at 06:30 the server crashes with the following messages: 06:30:00 Assert Failed: No Exception Handler 06:30:00 Informix Dynamic Server Version 7.31.UD1 06:30:00 Who: Session(13, informix@, 0, 0) Thread(9, tlitcplst, 0, 1) File: mtex.c Line: 446 06:30:00 Results: Exception Caught. Type: MT_EX_OS, Context: mem 06:30:00 Action: Please notify Informix Technical Support. 06:30:11 See Also: /var/tmp/af.3f17d58 06:30:11 mtex.c, line 446, thread 9, proc id 11630, No Exception Handler. 06:30:11 PANIC: Attempting to bring system down The config hasn't changed. I checked the crontabs: nothing is executed at that hour. Does anyone have an idea where this might come from? Thanks. Kurt Van Gompel. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================
On Mon, Dec 10, 2007 at 10:29:53AM -0500, Sebastian, Norma J. wrote: > Kurt, > > You may want to check that solaris 8 and IDS 7.31 are still supported.... Yes they are. and we're running successfully on that platform. > > It sounds like the problem we had several years back.... Mutex-exclusive lock > waits..... > As unusual as it is, I think it turned out to be an informix bug on that > platform..... > You may need to upgrade your informix ..... Luckily that is a very easy and > quick thing to do in most cases..... Should be for you since are not in > production yet..... Check the required solaris patches HTH -- Mark Thornber ========================= E M Thornber CEng MIET Enchanted Systems Limited Software Toolsmiths +44 (0) 1503 272097 Registered in England No: 3595651 Registered Office: Little Garth, Talland Hill, Polperro, LOOE, Cornwall PL13 2JL VAT No: GB 717 7967 83
Hi Kurt, Mark Thornber indicated you are on a supported platform... I found my "informix bug history".... All our work was on solaris.... We had that problem (or very close).... In November 1999, on solaris 8, and IDS 7.30.UC9 (32bit), we had "mutex lock hanging" issues. =20 I don't have the specific error from onlinelog, but it was IDS bug 119707. In May 2000, we upgraded to IDS 7.31.UC6 (still on solaris 8), and that problem didn't come back. We next encountered the problem in July 2004. Our failure string was "File: mtex.c Line: 446 MT_EX_OS Context: mem" We were still on solaris 8. We were IDS 7.31.FC6x2 (64 bit). We went to solaris 9 in July of 2004 and upped our IDS to 7.31.FD6x3 I do not have a record of that problem between July 2004 and October 2007.... Maybe my history will help you find your bug or help you feed Informix tech support and they will find the bug.... Good luck, Norma Jean =20 --- Procrastination isn't so bad - The undertaker will lose patience trying to get me into the box.=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D