Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Scheduler jobs are disabled after successfully running in 12.2

YadorJan 2 2018 — edited Jan 3 2018

Hello,

After migration from 11.1.0.7 to 12.2.0.1, I have a problem with some of the scheduler jobs.

Indeed, some of the jobs are marked as "disabled" after running, even if the last result is successfull.

Some of them ran 1,2,3,n times and suddenly, they are disabled.

Some were disabled after the first execution (successfull).

There is no entry in the alert.log

Where could I dig to find what happened ?

Is someone experiencing same problem ?

Thank you,

Regards.

Yann

Here is the creation code of one of the problematic job:

BEGIN

  SYS.DBMS_SCHEDULER.CREATE_JOB

    (

       job_name        => 'MY_SCHEMA.RUN_IMPORTATION'

      ,start_date      => TO_TIMESTAMP_TZ('2017/02/08 06:45:00.000000 Europe/Zurich','yyyy/mm/dd hh24:mi:ss.ff tzr')

      ,repeat_interval => 'FREQ=DAILY; BYHOUR=6; BYMINUTE=45'

      ,end_date        => NULL

      ,job_class       => 'DEFAULT_JOB_CLASS'

      ,job_type        => 'STORED_PROCEDURE'

      ,job_action      => 'my_package.run_importation'

      ,comments        => 'Blahblahblah'

    );

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'RESTARTABLE'

     ,value     => FALSE);

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'LOGGING_LEVEL'

     ,value     => SYS.DBMS_SCHEDULER.LOGGING_OFF);

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'MAX_FAILURES');

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'MAX_RUNS');

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'STOP_ON_WINDOW_CLOSE'

     ,value     => FALSE);

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'JOB_PRIORITY'

     ,value     => 3);

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'SCHEDULE_LIMIT');

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'AUTO_DROP'

     ,value     => FALSE);

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'RESTART_ON_RECOVERY'

     ,value     => FALSE);

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'RESTART_ON_FAILURE'

     ,value     => FALSE);

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'STORE_OUTPUT'

     ,value     => TRUE);

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'RAISE_EVENTS'

     ,value     => SYS.DBMS_SCHEDULER.JOB_FAILED + SYS.DBMS_SCHEDULER.JOB_BROKEN + SYS.DBMS_SCHEDULER.JOB_STOPPED);

  SYS.DBMS_SCHEDULER.SET_ATTRIBUTE

    ( name      => 'MY_SCHEMA.RUN_IMPORTATION'

     ,attribute => 'number_of_arguments'

     ,value     => 1);

  SYS.DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE

    ( job_name             => 'MY_SCHEMA.RUN_IMPORTATION'

     ,argument_position    => 1

     ,argument_value       => 'ARG1');

  SYS.DBMS_SCHEDULER.ENABLE

    (name                  => 'MY_SCHEMA.RUN_IMPORTATION');

END;

/

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Nov 9 2020
Added on Jan 2 2018
11 comments
10,017 views