Recently I wrote an Oracle job, which runs at an interval of 1 minute. However, I found that this job was not running. I initially suspected that the time interval was incorrect, but I found that the time interval was not an error. I also suspected that there was a problem with the stored procedure, however, it is okay to execute the stored procedure separately. Later, I checked it online and found that it may be the system parameter job_queue_process. Job_queue_process indicates the number of jobs that can be concurrently run by oracle.
Show parameter job_queue_process;
To view the value of job_queue_process in oracle. When job_queue_process is set to 0, all oracle jobs are stopped. Statements
Alter system set job_queue_processes = 10;
To modify the value of job_queue_process in oracle (here it is changed to 10, and the value of job_queue_process is set to another problem). However, this modification is dynamic, after oracle restarts, The job_queue_process value will still be from \ % ORACLE_HOME % \ admin \ mydb \ pfile \ init. read from the ora file.