Geek Answers Handbook

Change JOB_QUEUE_PROCESSES

Does JOB_QUEUE_PROCESSES change to 0 in Oracle DB to schedule locks for Oracle jobs too?

I found at http://download-west.oracle.com/docs/cd/A97630_01/server.920/a96521/jobq.htm some information about this, basically the following:

The initialization of the JOB_QUEUE_PROCESSES parameter controls whether the coordinator's job queue process is started by the instance. If this parameter is set to 0, no coordinator of the job queue process starts with starting the database, and therefore, no job queue jobs are executed. Initialization JOB_QUEUE_PROCESSES The parameter also determines the maximum number of Jnnn processes that can run simultaneously on an instance. The maximum number of processes that can be specified is 1000.

However, I am not sure that the “coordinate task queue” is a great scheme of things.

Thank you in advance for your timely responses.

+4
source share
2 answers

Before 11.2, if you set JOB_QUEUE_PROCESSES to 0, no job scheduled with DBMS_JOB will be executed. This parameter does not affect scheduled tasks through the DBMS_SCHEDULER . If in the "Oracle Tasks" section you refer to things such as background work in 10g and later, which automatically collects statistics on objects with missing or outdated statistics, these are DBMS_SCHEDULER tasks that JOB_QUEUE_PROCESSES will not affect.

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

+8
source

In Oracle EBS, Oracle recommends a value of 10 for JOB_QUEUE_PROCESSES.

0
source

More articles:


All Articles