Monitoring and Troubleshooting
The Most Common Cause of Database Crashes for OnLine Systems
In an environment with many programmers who are familiar with UNIX, your most common problem will occur when somebody kills an engine process. Informix does not take lightly to the untimely death of a sqlturbo engine or an oninit process. This often causes the database to abort, necessitating a restart and recovery that can take anywhere from minutes to hours. In general, if a sqlturbo process is killed with a kill -9 command while it is in a critical section of code or when it is holding a latch, the engine will abort.
This problem can best be solved by enforcing a prohibition that no one but the DBA can kill -9 a sqlturbo process. It's safe for anyone ...
Get Informix DBA Survival Guide, Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
