Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Job Scheduler in 9i
See inline...
Robert G. Freeman - Oracle8i OCP
Oracle DBA Technical Lead
CSX Midtier Database Administration
Author: Oracle9i New Features
Mastering Oracle8i
Clark Griswold: Eddie, has anyone ever told you that you're bad luck? Cousin Eddie: Those were my mother's dying words. But I guess if your body's covered in third degree burns, and your foot's caught in a bear trap, you tend to start talkin' crazy.
-----Original Message-----
Sent: Wednesday, June 12, 2002 8:03 AM
To: Multiple recipients of list ORACLE-L
Some comments...
>> some earlier versions of the db had job bugs where
>> the next date was not correctly calculated and thus
>> stopped running - typically threw an ora-600 or at
>> least a trace file in bdump (as opposed to udump)
Is this true in 9i? If so, can you provide any bug numbers we can reference with Oracle? I can't seem to come up with any specific to 9i in Metalink.
>> - we're running about 50 jobs at various frequencies
>> on 9013 and not experienced anything you've described,
>> at which point you're probably saying 'gee thanks' :-)
Well, that may be one catch, we are currently on 9011... we have plans to
move
to 9013, but have not yet for some.... *cough*... very good reasons. Maybe
this is an issue with 9011. If I could identify the bug then perhaps I can
get Oracle to backport an existing patch.
>> - see if the problem still occurs if you explicitly
>> - set next date within the job itself, ie 'procx;'
>> - becomes 'procx(next_date);' - this is not a great
>> - workaround, but it does confirm if the next date value
>> - is not being derived correctly by the scheduler itself
Tried that, no joy. It's really strange, some jobs will run all the time,
others
run once, twice, three times maybe and then just never run again.
>> - is the interval simple ? the most common errors for
>> job timings I've seen are typically dodgey interval
>> strings or passing a date to the parms instead of a
>> varchar2
Interval is something akin to "sysdate + 5/1440"... doesn't seem to complex. Like I said, this stuff worked fine in 8i, but in 9i it runs a while and dies.
Thanks for your thoughts!
RF
hth
connor
"Some days you're the pigeon, some days you're the statue"
-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: =?iso-8859-1?q?Connor=20McDonald?= INET: hamcdc_at_yahoo.co.uk 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: ListGuru_at_fatcity.com (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). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Freeman, Robert INET: Robert_Freeman_at_csx.com 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: ListGuru_at_fatcity.com (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).Received on Wed Jun 12 2002 - 12:56:49 CDT
![]() |
![]() |