Magnus,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 supposed to).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 time).HTHIgor
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Magnus Andersen
Sent: Thursday, October 27, 2005 10:17 AM
Subject: Re: dbms_job failed to executeI 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, Inc.
Trace file information...
Dump file /opt/oracle/ora92/rdbms/log/prd/bdump/prd_j000_9659.trc
Oracle9i Enterprise Edition Release 126.96.36.199.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 188.8.131.52.0 - Production
ORACLE_HOME = /opt/oracle/ora92
System name: Linux
Node name: oraprd.walkerassoc.com
Version: #1 SMP Tue May 17 17:52:23 EDT 2005
Instance name: prd
Redo thread mounted by this instance: 1
Oracle process number: 28
Unix process pid: 9659, image: firstname.lastname@example.org (J000)
*** 2005-10-22 00:38:58.415
*** SESSION ID:(27.52095) 2005-10-22 00:38:58.391
OPIRIP: Uncaught error 1089. Error stack:
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-00448: normal completion of background process