In daily work, there have been several encounters with the Oracle database that have established new jobs but do not perform the problem. Write it down for everyone to share.
We are in the daily
Dbms_job This package set up the relevant work, but the point will not be executed, on Baidu and gave a look at the following solutions. A, the job_queue_processes parameter determines the total number of processes that the job job can use.
b, when the parameter is 0 value, no job will be executed, it is recommended to set this value reasonably and at least greater than 1.
C, for the job run time should also be as reasonable as possible to set the interval and start time.
D, if the number of jobs running at the same time is many, too small parameter values cause the job to wait. An oversized parameter value consumes more system resources.
F, for jobs that have dependencies, merge them into a job as much as possible, such as using chain.
-bash-4.1$ sqlplus "/as sysdba"
Sql*plus:release 11.2.0.1.0 Production on Fri 12 11:35:56 2016
Copyright (c) 1982, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-64bit Production
With the partitioning, OLAP, Data Mining and Real application testing options
Sql> show parameter job;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
Job_queue_processes integer 0
Sql> alter system set job_queue_processes =10 scope=spfile;
System altered.
Sql> create Pfile from SPFile;
File created.
sql> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
Sql> Startup
ORACLE instance started.
Total System Global area 5.3982E+10 bytes
Fixed Size 2218032 bytes
Variable Size 2.9796E+10 bytes
Database buffers 2.3891E+10 bytes
Redo buffers 292569088 bytes
Database mounted.
Database opened.
The Oracle job is not resolved after setting up