知识大全 OracleJob不自动运行解决办法

Posted 2022-07-16 机制

篇首语：人生不是一种享乐，而是一桩十分沉重的工作。本文由小常识网(cha138.com)小编为大家整理，主要介绍了知识大全 OracleJob不自动运行解决办法相关的知识，希望对你有一定的参考价值。

OracleJob不自动运行解决办法 以下文字资料是由(全榜网网www.cha138.com)小编为大家搜集整理后发布的内容，让我们赶快一起来看一下吧！

　　ORACLE有一种定时调度机制用dbms_job包来管理

　　设置的JOB就是不运行搞得的郁闷

　　最好执行了这个才搞定 exec dbms_ijob set_enabled(true);

　　下面提供一个checklist用于检查job异常的原因

　　 ) Instance in RESTRICTED SESSIONS mode?

　　Check if the instance is in restricted sessions mode:

　　select instance_name logins from v$instance;

　　If logins=RESTRICTED then:

　　alter system disable restricted session;

　　^– Checked!

　　 ) JOB_QUEUE_PROCESSES=

　　Make sure that job_queue_processes is >

　　show parameter job_queue_processes

　　^– Checked!

　　 ) _SYSTEM_TRIG_ENABLED=FALSE

　　Check if _system_enabled_trigger=false

　　col parameter format a

　　col value format a

　　select a ksppinm parameter b ksppstvl value from x$ksppi a x$ksppcv b

　　where a indx=b indx and ksppinm= _system_trig_enabled ;

　　If _system_trig_enabled=false then

　　alter system set _system_trig_enabled =TRUE scope=both;

　　^– Checked!

　　 ) Is the job BROKEN?

　　select job broken from dba_jobs where job=<job_number>;

　　If broken then check the alert log and trace files to diagnose the issue

　　^– Checked! The job is not broken

　　 ) Is the job MITted?

　　Make sure a mit is issued after submitting the job:

　　DECLARE X NUMBER;

　　BEGIN

　　SYS DBMS_JOB SUBMIT

　　(

　　job => X

　　 what => dbms_utility analyze_schema

　　( SCOTT PUTE NULL NULL NULL);

　　 next_date => to_date( / / : : ′ dd/mm/yyyy hh :mi:ss )

　　 no_parse => FALSE

　　);

　　MIT;

　　END;

　　If the job executes fine if forced (i e exec dbms_jobs run(<job_no>);) then likely a mit

　　is missing

　　^– Checked! The job is mitted after submission

　　 ) UPTIME > days

　　Check if the server (machine) has been up for more than days:

　　For SUN use uptime OS mand

　　If uptime> and the jobs do not execute automatically then you are hitting unpublished bug

　　(Jobs may stop running after days uptime) which is fixed in and A

　　^– Checked! The server in this case has been up days only

　　 ) DBA_JOBS_RUNNING

　　Check dba_jobs_running to see if the job is still running:

　　select * from dba_jobs_running;

　　^– Checked! The job is not running

　　LAST_DATE and NEXT_DATE

　　Check if the last_date and next_date for the job are proper:

　　select Job Next_date Last_date from dba_jobs where job=<job_number>;

　　^– NEXT_DATE is porper however LAST_DATE is null since the job never executes automatically

　　 ) NEXT_DATE and INTERVAL

　　Check if the Next_date is changing properly as per the interval set in dba_jobs:

　　select Job Interval Next_date Last_date from dba_jobs where job=<job_number>;

　　^– This is not possible since the job never gets executed automatically

　　 ) Toggle value for JOB_QUEUE_PROCESSES

　　Stop and restart CJQ process(es)

　　alter system set job_queue_processes= ;

　　–<Wait for some time to ensure CJQ process stopped>

　　alter system set job_queue_processes= ;

　　Ref: Bug (fixed by: )

　　^– Done but did not help

　　 ) DBMS_IJOB(Non documented):

　　Last ditch effort

　　Either restart the database or try the following:

　　exec dbms_ijob set_enabled(true);

　　Ref: Bug (Closed Not a Bug)

　　Done but did not help

　　These are the most mon causes for this behavior

　　Solution

　　The solution ended up to be the server (machine) uptime

　　Even though it was up for only days after the server was rebooted all jobs were able to execute automatically

　　To implement the solution please execute the following steps:

　　 Shutdown all applications including databases

　　 Shutdown the server (machine)

　　 Restart all applications including databases

　　 Check that jobs are executing automatically

cha138/Article/program/Oracle/201311/16944