dbms_job failed to execute 2005-10-27 - By Igor Neyman
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).
HTH
Igor
__ ____ ____ ____ ____ ____ ____
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)] On Behalf Of Magnus Andersen
Sent: Thursday, October 27, 2005 10:17 AM
Cc: oracle-l@(protected)
Subject: Re: dbms_job failed to execute
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?
--
Magnus Andersen
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 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
ORACLE_HOME = /opt/oracle/ora92
System name: Linux
Node name: oraprd.walkerassoc.com <http://oraprd.walkerassoc.com/>
Release: 2.4.21-32.0.1.ELsmp
Version: #1 SMP Tue May 17 17:52:23 EDT 2005
Machine: i686
Instance name: prd
Redo thread mounted by this instance: 1
Oracle process number: 28
Unix process pid: 9659, image: oracle@(protected) (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 (See ORA-01089.ora-code.com): immediate shutdown in progress - no operations are permitted
ORA-00448 (See ORA-00448.ora-code.com): normal completion of background process
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2769" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=346092414-27102005><FONT face=Arial
color=#0000ff size=2>Magnus,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=346092414-27102005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=346092414-27102005><FONT face=Arial
color=#0000ff size=2>When you are saying that jobs stopped executing on Tuesday
,
does it mean that they were not executed since then?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=346092414-27102005><FONT face=Arial
color=#0000ff size=2>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).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=346092414-27102005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=346092414-27102005><FONT face=Arial
color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=346092414-27102005><FONT face=Arial
color=#0000ff size=2>And if it finds such jobs that "missed" their scheduled
time, it will execute them immediately (not waiting for next scheduled
time).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=346092414-27102005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=346092414-27102005><FONT face=Arial
color=#0000ff size=2>HTH</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=346092414-27102005><FONT face=Arial
color=#0000ff size=2>Igor</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)] <B>On Behalf Of </B>Magnus
Andersen<BR><B>Sent:</B> Thursday, October 27, 2005 10:17 AM<BR><B>Cc:</B>
oracle-l@(protected)<BR><B>Subject:</B> Re: dbms_job failed to
execute<BR></FONT><BR></DIV>
<DIV></DIV>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?<SPAN class=q><BR clear=all><BR>-- <BR>Magnus
Andersen<BR>Systems Administrator / Oracle DBA<BR>Walker & Associates,
Inc.<BR><BR><BR></SPAN>Trace file information...<BR><BR>Dump file
/opt/oracle/ora92/rdbms/log
<DIV id=mb_2>/prd/bdump/prd_j000_9659.trc<BR>Oracle9i Enterprise Edition
Release
9.2.0.6.0 - Production<BR>With the Partitioning, OLAP and Oracle Data Mining
options<BR>JServer Release 9.2.0.6.0 - Production<BR>ORACLE_HOME =
/opt/oracle/ora92<BR>System name: Linux<BR>Node
name: <A
onclick="return top.js.OpenExtLink(window,event,this)"
href="http://oraprd.walkerassoc.com/"
target=_blank>oraprd.walkerassoc.com</A><BR>Release:
2.4.21-32.0.1.ELsmp<BR>Version: #1
SMP
Tue May 17 17:52:23 EDT
2005<BR>Machine: i686<BR>Instance
name: prd<BR>Redo thread mounted by this instance: 1<BR>Oracle process number:
28<BR>Unix process pid: 9659, image: <A
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:oracle@(protected)"
target=_blank>oracle@(protected)</A> (J000)<BR><BR>*** 2005-10-22
00:38:58.415<BR>*** SESSION ID:(27.52095) 2005-10-22 00:38:58.391<BR>OPIRIP:
Uncaught error 1089. Error stack:<BR>ORA-01089 (See ORA-01089.ora-code.com): immediate shutdown in progress
-
no operations are permitted<BR>ORA-00448 (See ORA-00448.ora-code.com): normal completion of background
process</DIV></BODY></HTML>
|
|
