Home > problem-cause-solution > Jobs in 9i does not start one day, 10g scheduler’s surprise!

Jobs in 9i does not start one day, 10g scheduler’s surprise!


I had ported the existing jobs in 9i to 10g. It was working properly for 2 or 3 months and one day the jobs did not work. I tried to reexecute them, it says it does not know the procedure in schemas. For instance, EXAMPLESCHEMA.mysampleproc(‘myparameter’); is not executed. So after some trials, like restarting the database but only omitting the schema name, solves the problem. I left the thoughts of why does it happen to later days.

But, because it is painful change the job definitions of hundreds of jobs, I preferred using job scheduler feature coming in 10g. Surprise is coming now: while defining the jobs in job scheduler, they did not start.


No real cause, it can be misleading design bug.


The only stupid reason behind was, setting the start time and next start date formula same time. In order to make it execute you must give next date apart from start time, they must not be same!

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Don Charisma

because anything is possible with Charisma

Carol no Mundo!

Aventuras de uma intercambista a trabalho pelo mundo!

Blog do PHP

Oracle DBA for rookies!


Welcome to the world of Oracle with me....


News and reviews from the world of gadgets, gear, apps and the web


WordPress.com is the best place for your personal blog or business site.

Gurcan Orhan's ODI and DWH Blog

Some words about Oracle Data Integrator and Data Warehousing.

%d bloggers like this: