oracle 改变 JOB_QUEUE_PROCESSES

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/1201279/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-09-18 18:40:37  来源:igfitidea点击:

Altering JOB_QUEUE_PROCESSES

databaseoracledbms-schedulerdbms-job

提问by jnt30

Does altering the JOB_QUEUE_PROCESSES to 0 on an Oracle DB block the Oracle jobs from being scheduled too?

将 Oracle DB 上的 JOB_QUEUE_PROCESSES 更改为 0 是否也会阻止 Oracle 作业的调度?

I found in http://download-west.oracle.com/docs/cd/A97630_01/server.920/a96521/jobq.htmsome information about it, principally, the following:

我在http://download-west.oracle.com/docs/cd/A97630_01/server.920/a96521/jobq.htm 中找到了一些关于它的信息,主要是以下内容:

The JOB_QUEUE_PROCESSES initialization parameter controls whether a coordinator job queue process is started by an instance. If this parameter is set to 0, no coordinator job queue process is started at database startup, and consequently no job queue jobs are executed. The JOB_QUEUE_PROCESSES initialization parameter also specifies the maximum number of Jnnn processes that can concurrently run on an instance. The maximum number of processes that can be specified is 1000.

JOB_QUEUE_PROCESSES 初始化参数控制协调器作业队列进程是否由实例启动。如果此参数设置为 0,则数据库启动时不会启动协调器作业队列进程,因此不会执行任何作业队列作业。JOB_QUEUE_PROCESSES 初始化参数还指定了可以在一个实例上并发运行的最大 Jnnn 进程数。可以指定的最大进程数是 1000。

However, I am uncertain what the "coordinator job queue" represents in the grand scheme of things.

但是,我不确定“协调器作业队列”在总体方案中代表什么。

Thank you very much in advance for your timely responses.

非常感谢您及时的回复。

回答by Justin Cave

Prior to 11.2, if you set JOB_QUEUE_PROCESSESto 0, no job scheduled via DBMS_JOBwill be executed. That parameter does not affect jobs scheduled via the DBMS_SCHEDULERpackage. If by "Oracle jobs" you are referring to things like the background job in 10g and later that automatically gathers statistics on objects with missing or stale statistics, those are DBMS_SCHEDULERjobs that would be unaffected by JOB_QUEUE_PROCESSES.

在 11.2 之前,如果设置JOB_QUEUE_PROCESSES为 0,DBMS_JOB则不会执行任何调度通过的作业。该参数不会影响通过DBMS_SCHEDULER包安排的作业。如果“Oracle 作业”指的是 10g 及更高版本中的后台作业,它会自动收集有关缺少或陈旧统计信息的对象的统计信息,那么这些DBMS_SCHEDULER作业将不受JOB_QUEUE_PROCESSES.

Starting in 11.2, that changed and JOB_QUEUE_PROCESSES began to affect DBMS_SECHEDULER.The default value also changed from 0 to 1000 and it was made a non-basic initialization parameter.

从 11.2 开始,情况发生了变化,JOB_QUEUE_PROCESSES 开始影响 DBMS_SECHEDULER。默认值也从 0 更改为 1000,并成为非基本初始化参数。

回答by Val Sor

In Oracle EBS, Oracle recommends value for JOB_QUEUE_PROCESSESbe 10.

在 Oracle EBS 中,Oracle 建议值为JOB_QUEUE_PROCESSES10。