My Oracle Support Banner

Batch Jobs In 10g Run In Parallel Instead Of Serial Order (Doc ID 731373.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Utilities Work and Asset Management - Version 1.7.0.3 and later
Information in this document applies to any platform.

Symptoms

**Any examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
WAM - Oracle Utilities Work and Asset Management

Under WAM / Oracle 9i, jobs scheduled through the Job Manager ran in serial. In 10g, they appear
to run in parallel.

For example, assume we have two scheduled jobs, Job 1 and Job 2, set up to run 15 minutes apart
(Job 2 fifteen minutes after Job 1). Under 9i, if Job 1 took 20 minutes to run in some cases, Job
2 wouldn't start until Job 1 was completed. I.e. the second job would go into a wait-queue of
sorts. Under 10g, under the same conditions, Job 2 begins executing at 15 minutes after Job 1,
regardless of whether Job 1 completed or not.

Because some of our scheduled jobs are set up to be dependent of the results of earlier jobs, the
new behavior under 10g might present some support issues in the future.





Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.