Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Usenet -> c.d.o.server -> Re: Jobs do not run

Re: Jobs do not run

From: Martin T. <>
Date: Thu, 09 Aug 2007 06:57:32 +0200
Message-ID: <46ba9f5a$0$1345$> wrote:

> On 8 août, 12:42, "Martin T." <> wrote:

>> wrote:
>>> On Aug 6, 1:55 am, "Martin T." <> wrote:
>>>> wrote:
>>>>> Comments embedded
>>>>> On Fri, 03 Aug 2007 17:30:51 +0200, "Martin T." <>
>>>>> wrote:
>>>>>> The problem only exists in our test db instance (at the moment)
>>>>>> I fully expected you and Daniel to tell me that. (Given the fact that
>>>>>> there are 7 patch sets we haven't even looked at it might even have some
>>>>>> foundation.)
>>>>> All patch sets are cumulative
>>>>>> Let's for a moment assume we were running Oracle 10g2 with the newest
>>>>>> patch and hit this. What would you propose except calling Oracle?
>>>>> a) The most common cause for jobs not running is forgetting to commit
>>>> I know this. That you replied it to my OP just goes to show that you did
>>>> only read "jobs" and "...0.1" and then shouted something at me.
>>>>> b) the problem doesn't exist in
>>>> Interesting ... which crystal ball told you that?
>>>> I tell you what: it also does not exist in on 40 other machines
>>>> with the same HW and SW setup. It also did not exist on this machine
>>>> prior to one week ago.
>>>> Well whatever.
>>>> regards,
>>>> Martin
>>> Some DBAs on this list need a reality check.
>>> In the real world Databases don't get upgraded at the drop of a hat -
>>> New patches sometimes introduce new issues.
>>> Upgrading takes lots of planning and testing, and based on the case
>>> mentioned I would not upgrade the database on the count that it might
>>> solve the issue, especially since it is not an issue anywhere else and
>>> not prior to today.
>>> Once you understand the root cause of the current issue, and you find
>>> out for certain that an upgrade will fix it (by testing elsewhere),
>>> then you need to upgrade.
>>> Jonathan
>> To wrap this up:
>> What we did was the following (remember this is a test machine) ...
>> 1.) We exported the relevant Schema(s) data
>> 2.) Scratched instance (not Oracle binaries, only database file&config)
>> 3.) Recreated instance, System tablespaces etc. (Which incidentally
>> provided a good opportunity to check the creation scripts again)
>> 4.) Imported the Schema(s) data.
>> Voila: Jobs run again.
>> I wouldn't go so far as to call it a beautiful solution, but it
>> certainly was less hassle than patching (which may or may not have helped).
> Certainly??
> What would have been so time-consuming during the upgrade in
> comparison with these 4 tedious steps?
> It is a test db. I guess it was a good opportunity to upgrade.
> You'll try this out next time this bug reappears.

The problem with the upgrade is that if we update the test system, we also have to update all productions systems (>40) because we would like to run the same version in test as in production.

If this bug really should reappear, then we will certainly try to analyze it further ...

Martin Received on Wed Aug 08 2007 - 23:57:32 CDT

Original text of this message