Re: Informix 5.01 crash often on IRIX 5.2 ?
Posted in 1996
Topics: General Discussion
In article <4o9vc8$3oo@cssun.mathcs.emory.edu>, billy.wheeler@pixie.co.za' says... > >At 07:17 AM 5/24/96 GMT, Liu, ping-chih wrote: >> We have a Challenge L machine runing IRIX 5.2 and Informix 5.01. >>The problem is that the database engine will crash several times a day. >>We check the Infomix log and find lots of records of abnormal aborted >>user process. We think these process terminate at the critical session >>and cause the shutdown of Informix server engine. The problem is that we >> do'nt know what cause these process to terminate abnormally. We are not >>able to find any regulation from the log. Got any clude? Plese forward >>this article to anyone you feel may have some idea abut it. > >Ping, > >Is anybody on your machine doing a kill -9 on sqlturbo processes? This can >cause such behaviour. > >HTH. > >Hasta la vista! > >-- > >billy.wheeler@pixie.co.za > For the security reason, our AP had set TRAP's in the user's .profile. The TRAP is to intercept user's interrupt key and "kill -9" all the relative user process. The purpose is that users could only run the application and would'nt be able to get into unix shell. We had had Informix people come and check. They too could'nt find the reason but it's them who suspect the TRAP stuff. They although raised another possible cause, the "sac" daemon process. Do you know anyhting of this process? As for the TRAP problem, I find that our AP "run" the application from the .profile instead of "exec" it. I think that using the "exec" may gets rid of the TRAP and maintains the security feature that user want. Any other suggestion? If not work, do you know how to deal with "sac"? And one last question. According to our AP leader, the database pointer "may" be messed up when applications want to create a temporary table. He does'nt know it for sure but can't find other cause. Fortunely, this situation is recoverable but still need to be fixed in case it's not. The AP leader think this may be resolved by upgateing the Informix version. Could it be an bug? What do you think? Sorry for so much bothering, thanks. Anyone out there got a clude? Help :( --ping p.c.liu@cdc.com