This content has been marked as final. Show 3 replies
I understand what sometime it is necessary don't allow run jobs over specified period of time. But this is usually used for some maintainence task.
If you heavy_weight_prc do some bussines task and you know that it duration is longer than 60s why you want to kill it when running longer then 60s ?
This don't make any sense to me. When you procedure do all work in one transakction then it starts and after 60s it is killed and all is rolled back. You only produce heavy load on DB without any positive bussines efect.
1 min is simply a test value. In production it normally runs 5min and I want to kill it to free resources if it runs 10mins because something is wrong.
There is no buissness logic besides I want to kill all jobs that run over max_run_duration.
Edited by: Phil on Apr 18, 2013 8:52 AM
It seems the sniper job needs to run at highest priorty.
Chapter 4 Managing Resources in book "Mastering Oracle Scheduler" by Ronald Rood and the dbms_resource_manager package seem relevant.
Problem sloved it wasn't high load it seems to be very poor default value.
select value from v$parameter where name='job_queue_processes';
This statement fixed my problem
alter system set job_queue_processes=30;