Re: Assert Failed: Internal Error - Segmentation Violation

rt10hp@csl.gov.uk (Richard Thomas) wrote: >Hi all, >I saw a similar request to this last week, but as it involved >Powerbuilder, I ignored it :-) >As June Tong suggested in her reply, this is being caused by >a dodgy char to int conversion (a known bug). I asked the user >who caused it initially to tell me what he had been doing, and >reproduced it perfectly! The user was running an ACE report from >a user-menu that prompts for a 6 digit reference number. The >problem is occurring when users mistype the number, and a character >gets it by mistake (in this case it was a '-' instead of a '0'). >I find it hard to believe that a simple typo can crash the whole >online engine. Is there a fix for this. (Yes, I have already told >the users to be careful when typing anything in at a prompt!!). >We are running Online 7.13. Last weeks problems were reported as >being on 7.10 (which we had, and then upgraded when Nils told me >it was "buggy"). >Here's the output from the log file: >11:07:10 Assert Failed: Internal Error - Segmentation Violation >11:07:10 Who:Session(23, rt10hp@harpm, -1, 170003028) > Thread(48, sqlexec, a2001b0, 1) >11:07:10 Results: OnLine must abort >11:07:10 Action: Reinitialize shared memory >11:07:10 See Also: /tmp/af.30184e, shmem.30184e.0 >11:07:11 rsinit.c, line 9217, thread 48, proc id 13680, Segmentation Violation. >11:07:11 PANIC: Attempting to bring system down >Unfortunately, I don't have /tmp/af.30184e to hand, as our sysadmin >decided to reboot the server ;-) In response to all these posts: We had this problem fairly often on 7.11 uc.1 engine on sparc center 2000 running Solaris 2.4. By setting the environment variable AFDEBUG=1 before bringing the engine online, you can get the engine to hang in this instance allowing you to get a stack trace and onstat results. Send this info to Informix tech support and they can help trace the problem. I have done this and they traced our problems to specific bugs. We have since upgraded to 7.13 uc.2 and so far have had no problems or crashes(keeping fingers crossed). Tech support can also send you an instruction sheet regarding this. By the way, when the engine crashes it takes no more than 10 minutes to get the info you need before restarting the engine.