Re: Trapping Informix Crashes ??'s

Glenn Travis wrote: > > You can set AFDEBUG=1, then start the instance. This will cause the [SNIP] > David Parent wrote: > > Wondering what tools DBAs are using to > trap Informix crashes (at any level, OS > or Informix). > > For instance, Informix crashes at 2:55 AM > and I am at home sleeping, how do I know > that the engine crashed. > > Currently, I page when any Informix event > alarm with a severity of 3, 4 or 5 occurs. > This does not trap all possible problems that > could occur however, OS & perhaps even [SNIP] Version 7.3 adds another event handler that traps all of those fatal crashes that the event alarm handler could not handle. The problem was that the event alarms were triggered by the thread that crashed, for certain kinds of crashes it could not trap itself. I beat them up about that for over a year and the result is the monitoring thread in V7.30+ that watches for another thread to go down. In addition 7.30 will usually not go down in these cases only the one affected oninit will crash and the engine will stay up (a side effect of the monitor thread is that it can clean things up and determine if it is safe to continue or if the engine needs to be brought down). Also, if you have any version before 7.21 there were many trapable crashes that were simply not caught. The ultimate answer? Upgrade! Gee I seem to be pushing upgrades a lot lately ... ahh well, too bad I don't get a commission on them though. Art S. Kagel