Re: Oninit from cron leaves engine in permanent fast recovery

Try creating a startup script, informix_start. Include in the beginning of the scripts a source file to set all of your env variables. Below is the script I use to start informix. It works via cron as well as the rc3 startup scripts (atleast it works on HP): informix_start: # Source the informix environment variable . /etc/informix_env # Start the Informix Database engine. oninit# Start backing up logical logs sleep 30 /usr/informix/scripts/log_backup.ksh # Set priority of jobs /usr/informix/scripts/set_inf_prio 120 Thanks Andreas Breitfeld <abreitfe@de.ibm. com> To Sent by: informix-list@iiug.org owner-informix-li cc st@iiug.org Subject Re: Oninit from cron leaves engine 10/06/2005 10:01 in permanent fast recovery AM On Thursday 06 October 2005 12:25, you wrote: > Thanks for the responses. > > Including a 'c' in the shutdown doesn't make any difference Dave ... > sadly. I have tried flushing, forcing, advancing, clearing shm ... all > to no avail. > > There are no relative paths referenced in the script. It's all very > explicit. The script has been executed from different staring points. > > I don't know about open file descriptors Jonathan, but I will find out. > There is no input and output is redirected to a log file in both > cases. Did you redirected stdout _and_ stderr of your script to a file? your_script > /tmp/cron.log 2>&1 Otherwise try additional redirecting for commands of your script, e.g. ... /usr/informix/bin/onmode -yuk > /tmp/onmode.log 2>&1 ... /usr/informix/bin/oninit -v > /tmp/oninit.log 2>&1 Andreas > > I'm not sure what to draw from the fact that it hangs on the temp space > initialisation either ... but it would seem like a clue :) There is, > however, nothing apparently wrong with the spaces. > > Thanks for the suggestions. sending to informix-list sending to informix-list

If your CONSOLE param in the ONCONFIG file is set to /dev/console try pointing it at a plain file instead, e.g /usr/informix/<instance>.console. I had a similar problem earlier this year when my server console daemon left town and informix just wouldn't start, it was waiting to write to console and couldn't

Nog wrote: > If your CONSOLE param in the ONCONFIG file is set to /dev/console try > pointing it at a plain file instead, e.g > /usr/informix/<instance>.console. > > I had a similar problem earlier this year when my server console daemon > left town and informix just wouldn't start, it was waiting to write to > console and couldn't > I think Nog has it :)