>Hi all, > >I have used the dbms_job package in some cases. >Normally I use the INTERVAL >method of the packages. i.e. 30 sec. > >But.... > >soemtimes it occurs, that users change their system >time to the future to >test something, >then changing back to the correct time. > >The INTERVAL job then stops, as he has not reached >his "future" time...... > >any ideas to handle this ?? (Oracle 7.3.4.1 on NT4) > > >TNX > >> Frank <
Except forbidding your users to play with time, I don't see any 'clean' way to do this. Basically a job runs and INTERVAL is used to compute the next time when it must run. Job processes wake up periodically and check the system current time against this. If the current time and the previous computation are incoherent, you are done. The best you can do is perhaps a (manually executed) SQL script which checks whether times in DBA_JOBS make sense. HTH, Stephane Faroult Oriole -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Stephane Faroul INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
