Re: onmode and system shutdown
use 'onstat -g ses' on the server and check for active sessions. only
when there r no active sessions, issue the shutdown command.
i don't believe its wise to interrupt the shutdown
or startup operations. i interrupt them only when they hang for ages.
one would then need to clear the shared memory structures using
the ipcrm commands at the system level. hope this helps
regards,
bipin
On Mar 18, 9:52pm, David Williams wrote:
} Subject: Re: onmode and system shutdown
} In article <332D643C.13A8@edge.net>, Mark Spears <pmspears@edge.net>
} writes
} >We have a weekly shutdown procedure that requires us to reboot one of
} >our production machines that runs informix. Recently we had a slight
} >problem; there was an index rebuild occuring when the automated reboot
} >script kicked in. The system shut down, and on reboot Online went into
} >recovery mode for about four hours.
} >
} >My question: is there a straightforward way to determine what the
} >Online 7.12 engine is doing? Some option to onstat, for example, that
} >would allow a script to intelligently opt for or against shutting down
} >the informix system?
} >
} Look at the output to onstat -p and see if the isamtot field changes
} very much...note it is proably an idea to do an onstat -z to reset the
} value to be near 0 as it can overflow and become negative or get large
} and become hard to read...
}
} >My next question: After giving an onmode -ky command, is there any way
} >to "undo" that and tell the engine that we dont want it to go offline
} >after all? (We found that it is possible for the engine to go into
} >quiescent mode for quite a while before actually going offline... )
} >
}
} Not that I have idea of, almost certainly no documented way...
}
} >Thanks,
} >Jeff Anderson
} >Service Merchandise
} >(thanks Mark for letting me use this account)
}
} --
} David Williams
}-- End of excerpt from David Williams