When you are saying that jobs stopped executing on Tuesday,
does it mean that they were not executed since then?
Your output from dba_jobs shows that all your jobs were
executed this morning (probably when your instance was started) and they all are
scheduled to be executed tomorrow at different times (probably, as they are
The reason they all were executed this morning right after
instance started is that most probably your instance was down at the time when
they were scheduled to be executed, and when oracle starts, it checks if it
missed to execute some jobs while the instance was down.
And if it finds such jobs that "missed" their scheduled
time, it will execute them immediately (not waiting for next scheduled
I found two trace files with the same time stamp on them. These
are the closest to when I saw the problem. Could this have "hung" since
the database bounced?
Systems Administrator / Oracle DBA
Walker & Associates,
Trace file information...
Oracle9i Enterprise Edition Release
188.8.131.52.0 - Production
With the Partitioning, OLAP and Oracle Data Mining
JServer Release 184.108.40.206.0 - Production
System name: Linux
Version: #1 SMP
Tue May 17 17:52:23 EDT
Redo thread mounted by this instance: 1
Oracle process number:
Unix process pid: 9659, image: email@example.com
*** SESSION ID:(27.52095) 2005-10-22 00:38:58.391
Uncaught error 1089. Error stack:
ORA-01089: immediate shutdown in progress -
no operations are permitted
ORA-00448: normal completion of background