Process Aborted Abnormally

Hello, Has anybody seen this before when running tbstat -m. 10:02:24 Process Aborted Abnormally: pid=3D32074 user=3D0 us=3D30002044 f= lags=3D81 This is very similar to the example given on page 570 of "Informix Unleas= hed." The process is no longer active when I go looking for it. I am going to c= heck the Message log file next. Any other log files I could check? Does "user=3D0" mean root or informix? What does "us" mean and how can I use it in my investigation? What does "flags" mean and how can I use it in my investigation? Environment: Informix 5.01ud2, AIX 4.01, IBM RS6000 Box, 4GB mirrored dri= ve, 236MB ram. data base size is 1.5GB. Thanks Stan

Stan Hixon wrote: > > Hello, > > Has anybody seen this before when running tbstat -m. > > 10:02:24 Process Aborted Abnormally: pid=3D32074 user=3D0 us=3D30002044 f= > lags=3D81 > This is very similar to the example given on page 570 of "Informix Unleas= > hed." Right this means that some user killed a process attached to the online instance - a HUGE no-no - using INTERRUPT or the QUIT key or a kill -9. If the task had been in a critical section the whole engine would have crashed. > The process is no longer active when I go looking for it. I am going > to check the Message log file next. > Any other log files I could check? No. > Does "user=3D0" mean root or informix? The 3D is an artifact of your TERM variable which is probably not set correctly (just vi the online logfile to verify the actual message) so it looks like the user was root (0) so that kind of limits the number of culprits (I hope). > What does "us" mean and how can I use it in my investigation? The us is the user address space of the connection as reported in tbstat -u. Flags is the numeric value of the flags column reported by tbstat -u indicating what the process was doing at the time of it's abort. Tell your users/administrators to keep their fingers off the INTERRUPT key and do not kill -9 any Informix client. Always run tbstat -s to determine if there are any processes in critical sections and if so use the address to correlate back to the tbstat -u listing to see if the sqlexec is the one that belongs to the process you want to kill. Then you can use tbmode -z as Informix or root to kill the connection safely. If tbmode -z does not work and you ABSOLUTELY have to kill off the process use the following sequence: kill -TERM ...;kill -PIPE ...; kill -TERM .... Art S. Kagel