Folks -
I'm a Newbie...
Progress 10.1b on a AIX 5.3 box. I'd like to be able to create a cron job that checks if the database is down, and if it is, restarts it. Is this even advisable?
Background: Have a very stable environment that has crashed twice in the last 10 weeks. Seems to be due to the actions of a single user, cannot quite determine the cause - am thinking it's terminal emulator or print queue issues. Anyways, the database always starts nicely once it's brought back up.
Was thinking I could grep the output of ps -A for '_mprosrv', and if not found then perhaps proceed with a start-up.
Feel free to slam me if this is a totally irresponsible approach to restarting an db instance who's crash has not been properly investigated. But my thinking is that if it's in any kind of state that actually requires intervention\recovery, then it simple would not restart. Am I right?
Thanks,
crafuse
I'm a Newbie...
Progress 10.1b on a AIX 5.3 box. I'd like to be able to create a cron job that checks if the database is down, and if it is, restarts it. Is this even advisable?
Background: Have a very stable environment that has crashed twice in the last 10 weeks. Seems to be due to the actions of a single user, cannot quite determine the cause - am thinking it's terminal emulator or print queue issues. Anyways, the database always starts nicely once it's brought back up.
Was thinking I could grep the output of ps -A for '_mprosrv', and if not found then perhaps proceed with a start-up.
Feel free to slam me if this is a totally irresponsible approach to restarting an db instance who's crash has not been properly investigated. But my thinking is that if it's in any kind of state that actually requires intervention\recovery, then it simple would not restart. Am I right?
Thanks,
crafuse