last onchecks ran

Hi, Excuse me for this dumb question. Is there any way at database level which can tell when the last onchecks (with any switcth) ran and exist status? If not, it would be really great to have such info. if future releases. Thanks. --------------------------------- Get the name you always wanted with the new y7mail email address.

On Fri, Apr 11, 2008 at 4:10 PM, H.G <hariog@yahoo.com> wrote: > Excuse me for this dumb question. > > Is there any way at database level which can tell when the last onchecks (with > any switcth) ran and exist status? If not, it would be really great to have > such info. if future releases. I don't think so - unless you can track it via Unix process accounting. Do you mean "nice to know for each option separately", or "nice to know for any time oncheck is run regardless of options"? The latter is easy but not necessarily helpful ('oncheck -pD database:table' is not much help for tracking when 'oncheck -cr' was last run), so you'd probably want to track all operations. Consider whether to use auditing - it would be overkill for just oncheck, but would give you the information you need. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2008.0229 -- http://dbi.perl.org/ "Blessed are we who can laugh at ourselves, for we shall never cease to be amused." NB: Please do not use this email for correspondence. I don't necessarily read it every week, even.

Thanks JL. "nice to know for each option separately" would be the ideal case. Came across a site where oncheck runs every night via cron by root (crontab setup by sys admin). cron logs have root:root ower:group permission and do not have read permission to public. During an internal audit, DBA was asked a question, can she tell when last onchecks ran using SQL query or some onstat command from database (without looking at cron logs)? You rightly said "no" and I also thought the same thing as onchecks are command line utilities and nothing to do with database. However, later on I realise, would have been nice if a row is inserted or col value been updated in some sys??? db whenever onchecks runs. I know its not easy and there may be so many consideration like instance is up or down etc. etc. You are right, auditing is another option but I 100% agree it would be over kill even with using proper auditing masks. Thanks very much for your time to reply. Jonathan Leffler <jleffler.iiug@gmail.com> wrote: On Fri, Apr 11, 2008 at 4:10 PM, H.G wrote: > Excuse me for this dumb question. > > Is there any way at database level which can tell when the last onchecks (with > any switcth) ran and exist status? If not, it would be really great to have > such info. if future releases. I don't think so - unless you can track it via Unix process accounting. Do you mean "nice to know for each option separately", or "nice to know for any time oncheck is run regardless of options"? The latter is easy but not necessarily helpful ('oncheck -pD database:table' is not much help for tracking when 'oncheck -cr' was last run), so you'd probably want to track all operations. Consider whether to use auditing - it would be overkill for just oncheck, but would give you the information you need. -- Jonathan Leffler #include Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2008.0229 -- http://dbi.perl.org/ "Blessed are we who can laugh at ourselves, for we shall never cease to be amused." NB: Please do not use this email for correspondence. I don't necessarily read it every week, even. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. See you at the IIUG Informix 2008 Conference The Power Conference for Informix Professionals April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas http://www.iiug.org/conf Registration Now Open!! --------------------------------- Get the name you always wanted with the new y7mail email address.