question of dbms_Scheduler

11.2.0.4

I have a very simple solution to this question, but I was wondering if someone came up with a solution to the issue.

I can add a job with an expression of calendar which runs 15 and 45 minutes after to say 7 and 08:00 hours. FREQ = all days; BYHOUR = 7, byminute 8 = 15, 45; BYSECOND = 0

What happens if I want it to run at 7:15 only and 08:45? Is it possible to put in the same work? Is it easy to create a second job to do the same thing? Very easy. I wonder if there is a clever solution to do the same job.

Hello

I don't know if understand well your question, but please...

Read the following doco in the section which includes schedules

https://docs.Oracle.com/CD/B28359_01/AppDev.111/b28419/d_sched.htm

Is there a way where you can create several calendars with different times, then you can combined or joined to have several stamps in time for the same job.

In create annex statement, you can use the INCLUDE parameter.

See the example:

BEGIN dbms_scheduler.create_schedule ('embed_sched', repeat_interval => ' FREQ = YEAR;) BYDATE = 0130, 0220, 0725'); dbms_scheduler.create_schedule ('main_sched', repeat_interval => ' FREQ = MONTHLY;) INTERVAL = 2; BYMONTHDAY = 15; BYHOUR = 9, 17; INCLUDE = embed_sched'); END; /

When you create the task you set the main parameter of Planner create_job Planner.

If I do not understand your question please tell me.

Kind regards

Juan M

Tags: Database

Similar Questions

basic question on DBMS_SCHEDULER

DB version: 10 gr 2
I need to execute a stored procedure called PROCESS_SHIP_TRK every 5 minutes. How can I do this using DBMS_SCHEDULER?

Hello

Something like this should work.

Hope this helps,
Ravi.

As SYS :grant create job to scott;

connect scott/tiger

BEGIN  dbms_scheduler.create_job('j1',    job_type => 'PLSQL_BLOCK',    job_action => 'dbms_lock.sleep(1);',    start_date => trunc(systimestamp),    repeat_interval=>'FREQ=MINUTELY;INTERVAL=5;'    enabled=>true);END;/

Has no Job Scheduler executable
-QUESTION: Do DBMS_SCHEDULER failure. JOB_TYPE = CREATE_JOB > EXE file
-I am able to get the following code and work to be done if I create under SYS exclusively.
-The following code will create a job, schedule it, run it and it fails.
-The credentials are correct, the credentials are for the same server that oracle runs from.
-Oracle 11.2 on Windows 2003 server.
-I use the operating system credentials so to my understanding of a domain attribute is not necessary.
-All cases I saw, it is NOT advisable to use SYS to create and run the tasks so please do not recommending as a work-around.

CLEARS THE SCREEN

connect sys / & & sys_password @& & database_name have SYSDBA

Select to_char (SYSDATE, "the HH24: MI: SS DD/MM/YYYY) double START_TIME;

DROP USER CASCADE ALPHA;

CREATE USER IDENTIFIED BY ALPHA ALPHA;

ALTER USER ALPHA
DEFAULT TABLESPACE "DCN."
TEMPORARY TABLESPACE "TEMP".
RELEASE OF ACCOUNT;

ALTER USER QUOTA UNLIMITED ON DCN ALPHA;

GRANT CREATE JOBS EXTERNAL TO ALPHA;
GRANT CREATE EMPLOYMENT ALPHA;
GRANT TO CREATE A VIEW ON ALPHA;
GRANT CREATE ALPHA PROCEDURE;
GRANT CREATE ROLLBACK SEGMENT TO ALPHA;
GRANT CREATE SEQUENCE TO ALPHA;
GRANT CREATE SESSION TO ALPHA;
GRANT CREATE SYNONYM OF ALPHA;
GRANT CREATE TABLE FOR ALPHA;
GRANT CREATE TRIGGER FOR ALPHA;
GRANT CREATE VIEW TO ALPHA;

GRANT SDE_VIEWER OF ALPHA;

DBMS_SCHEDULER EXEC. DROP_CREDENTIAL ('DEV');

BEGIN
-Basic credential.
() DBMS_SCHEDULER.create_credential
credential_name = > "DEV."
username = > 'ADMIN',
password = > "PSWD");
END;
/

GRANT EXECUTE ON DEV to ALPHA;

SELECT THE USER CREDENTIAL_NAME, SUBSTR(USERNAME,1,16) AS NAME
OF USER_SCHEDULER_CREDENTIALS;

CONNECT ALPHA/ALPHA@DCNSDB

BEGIN
SYS. DBMS_SCHEDULER. () CREATE_JOB
job_name = > ' "MKDIR '",
job_type = > 'EXECUTABLE. "
number_of_arguments = > 3,
job_action = > '\windows\system32\cmd.exe ',.
auto_drop = > FALSE);
SYS. DBMS_SCHEDULER. SET_JOB_ARGUMENT_VALUE('MKDIR',1,'/C');
SYS. DBMS_SCHEDULER. SET_JOB_ARGUMENT_VALUE('MKDIR',2,'mkdir');
SYS. DBMS_SCHEDULER. SET_JOB_ARGUMENT_VALUE('MKDIR',3,'c:\temp\MKDIR_JOB3');
SYS. DBMS_SCHEDULER. SET_ATTRIBUTE ('MKDIR', 'credential_name','SYS.) DEV');
SYS. DBMS_SCHEDULER. ENABLE ('MKDIR');
END;
/

connect sys / & & sys_password @& & database_name have SYSDBA

SELECT JOB_NAME, STATUS, OWNER, LAST_START_DATE FROM DBA_SCHEDULER_JOBS WHERE OWNER = "ALPHA";

Select to_char (SYSDATE, "the HH24: MI: SS DD/MM/YYYY) double START_TIME;

SELECT JOB_NAME, STATUS, OWNER, LAST_START_DATE FROM DBA_SCHEDULER_JOBS WHERE OWNER = "ALPHA";
STATE OF JOB_NAME OWNER
------------------------------ ------------------------------ ---------------
LAST_START_DATE
---------------------------------------------------------------------------
MKDIR ALPHA FAILED
20 APRIL 11 03.35.49.156000 PM - 04:00

Any help will be greatly appreciated.

Published by: LONGENECKER on April 20, 2011 16:05
Hello

2 things

-This error is thrown only if a credential is not used. Make sure that you create the disabled task, assigning to the attribute credential_name then allowing the work.

-This error usually indicates that the run Scheduler service is not started on windows. Make sure that the OracleJobScheduler Windows service is started.

Hope this helps,
Ravi.

Dbms_scheduler OEM question

I use 11.2.0.2 on AIX 7.1 and I have a question regarding the retention period of the newspapers for newspapers in dbms_scheduler within OEM.

We use OEM 10.2.0.5.
Go to your database and then click on 'server', then click on "global attributes".
This will bring up the page Scheduler global attributes.
By default, the history of newspaper has 30 days (retention period in days for jobs and Windows logs).

Now, if back us to our "Server" tab and click on "Jobs", then click on history, we see that we have job logs that are much older than 30 days.

Why is there a base of more than 30 days?

THX...

It is by default but the automatic use of certain jobs a category of different jobs for which number of days is great:

SQL> select job_class_name, log_history, comments
  2  from dba_scheduler_job_classes c
  3  where log_history is not null;

JOB_CLASS_NAME                 LOG_HISTORY COMMENTS
------------------------------ ----------- -----------------------------------
ORA$AT_JCURG_OS                    1000000 auto optimizer stats collection
ORA$AT_JCNRM_OS                    1000000 auto optimizer stats collection
ORA$AT_JCMED_OS                    1000000 auto optimizer stats collection
ORA$AT_JCURG_SA                    1000000 auto space advisor
ORA$AT_JCNRM_SA                    1000000 auto space advisor
ORA$AT_JCMED_SA                    1000000 auto space advisor
ORA$AT_JCURG_SQ                    1000000 sql tuning advisor
ORA$AT_JCNRM_SQ                    1000000 sql tuning advisor
ORA$AT_JCMED_SQ                    1000000 sql tuning advisor

9 rows selected.

You can view the logs of related job more than 30 days with:

select log_date, job_name, job_class
from dba_scheduler_job_log
where job_class in (select job_class_name from dba_scheduler_job_classes where log_history is not null)
and log_date < sysdate - 30
order by log_date;

Edited by: P. Forstmann October 18, 2011 22:17

dbms_scheduler: next_run_date questions...
Hello guys,.

I created a JOB at 23:56:18.0 2011-02-15, using the script below.
Start
() dbms_scheduler.create_job
job_name = > 'TestJoB.
, job_type = > 'PLSQL_BLOCK '.
, job_action = > ' start / * / end; »
, start_date = > SYSDATE
, repeat_interval = > ' FREQ = DAILY; BYHOUR = 06; BYMINUTE = 15; BYSECOND = 0'
enabled = > TRUE);
end;

According to above script, use must turn Feb 16, 06:15.

When I checked the table dba_scheduler_jobs, next_run_date column shows 2011-2-17 6.15.0.700000000 GMT.

can someone tell me what the problem is... and how to fix it.
Thank you
AB
In fact, try to omit the start_date. Maybe it's some nonsense zone.

DBMS_SCHEDULER. Question CREATE_JOB

I wan to the Scheduler to execute the procedure each Monday and Friday-09:00. Here I get the error

Hello

Try on MONDAY, Friday, instead of 1 MON, FRI 1

requirement of dbms_scheduler admin privileges

I have a requirement to run a procedure stored at the end of each month and want to use dbms_scheduler to plan the execution of store procedures. I understand that it is possible to use dbms_scheduler to schedule the stored procedure... My question is if I want to use dbsms_scheduler do I do any admin installation? The version of oracle 11g database is

Jitendra says:

Should have the Execute privilege to run DBMS_SCHEDULAR.

Oracle gives to everyone by default:

SQL > select the beneficiary, the privilege of dba_tab_privs where table_name = 'DBMS_SCHEDULER ';

HOLDER OF PRIVILEGE
------------------------------ ----------------------------------------
PUBLIC PERFORMANCE
RUN ORACLE_OCM
RUN EXFSYS

SQL >

SY.

CLOB by moving to DBMS_SCHEDULER. SET_JOB_ANYDATA_VALUE

I use OracleXE 11 g.
My question is: "is it possible to pass the CLOB value to DBMS_SCHEDULER. SET_JOB_ANYDATA_VALUE? »
Example:
Does not work:
Start
dbms_scheduler.set_job_anydata_value (job_name = > 'some_job', argument_position = > 1, argument_value = > SYS.) ANYDATA. ConvertClob ('blabla'));
end;
Error report-
ORA-22370: incorrect use of method
ORA-06512: at "SYS." DBMS_ISCHED', line 244
ORA-06512: at "SYS." DBMS_SCHEDULER', line 739
ORA-06512: at line 9 level
22370 00000 - "incorrect use of the %s method.
* Cause: This method of SYS. AnyType or SYS. AnyData or SYS. AnyDataSet is
be used inappropriately.
* Action: See documentation for correct use.
Works great:
Start
dbms_scheduler.set_job_anydata_value (job_name = > 'some_job', argument_position = > 1, argument_value = > SYS.) ANYDATA. ConvertVarchar2 ('blabla'));
end;
Thanks for any help!

Hello

It is a behavior that is expected according to the documents:

ANYDATA TYPE

Restrictions

Persistent storage of ANYDATA cases whose type contains incorporated another LOBs that BFILE s is not currently supported.

You then use VARCHAR2.

DBMS_SCHEDULER and Script Shell on 10.2.0.1

Hi all
My env, Oracle 10.2.0.1 and OS is Solaris.
My script can run on the operating system that is a work without error that contain create file, delete the file, call sqlplus, function to get the value of database and return to the variables of the BONE.
Shell script to the code as below
-------------------------------------------------------------------------------------------------------------------------------------
get_val () {}
sqlplus-s/nolog < < EOF
Conn test/test
set the position
Set feedback off
set pages 0
SELECT SUBSTR (SYS_CONNECT_BY_PATH (Z, ' '), 2) z
FROM (SELECT NAMEDQUERY, ROW_NUMBER () ON the rn (ORDER OF Z),
COUNT (*) NTC)
X
WHERE Z LIKE "% FULL")
WHERE rn = NTC
START WITH rn = 1
Rn = rn + 1 PRIOR CONNECTION.
EXPRESSIONS OF FOLKLORE
}
VX = $(get_val)
If [${#vx} - gt 0]; then
for x in $vx
do
RM-f $CURRDIR / $xfile.txt 2 >/dev/null
fact
FI
-------------------------------------------------------------------------------------------------------------------------------------
When it is executed by dbms_scheduler showing below error
ORA-27369: jobs of type EXECUTABLE failed with exit code: no such file or directory
STANDARD_ERROR="/home/Oracle/script/test.sh: error of syntax on line 26: ' vx = $' unexpected
How to fix above error? (owner of $CURRDIR / $xfile.txt is oracle user)
One last question, how to force dbms_scheduler that use user oracle (OS) to run the shell script?, as I know, the default user is null and Oracle 10.2.0.2 later version which have external.job.ora to define but 10.2.0.1 has not.
Thank you in advance,
Hiko

I changed the planner of the storyline of the game as below

dbms_scheduler.create_job (job_name => 'TEST', job_type => 'EXÉCUTABLE', job_action => ' / usr/bin/bash ', number_of_arguments-online 1);

dbms_scheduler.set_job_argument_value('TEST',1,argument_value,'/home/Oracle/test.sh');

It's the job. This is the finding of fact

1. change the permissions of $ORACLE_HOME/bin/extjob to 4750 (- rwsr - x) -

2. change the owner of $ORACLE_HOME/bin/extjob to oracle: dba

3. use "/ usr/bin/bash ' instead of ' / usr/bin/sh".

But I found the error on the process of downloading the files I use wget to download the source in shell script file and run by dbms_scheduler as shown above.

My problem, the first file can download normally and until the end of the process but second file has to hang.

You have an idea or a solution to prove and solve it?

Thank you

Hiko

Problem with DBMS_SCHEDULER. CREATE_JOB in the package

Hi all

I tried the following with DBMS_SCHEDULER example. CREATE_JOB.
This is just an example, I tried to use the DBMS_SCHEDULER package. Exception block is also not have good standards, because I just want to understand that the package

create table test_test1 (process_id number  ,name varchar2(22) )

CREATE OR REPLACE PACKAGE PKG_SCHEDULER_TEST
IS
   PROCEDURE proc_test (v_process_id NUMBER, v_name VARCHAR2);

   PROCEDURE DATA_LOAD (v_process_id NUMBER, v_name VARCHAR2);
END PKG_SCHEDULER_TEST;



CREATE OR REPLACE PACKAGE BODY PKG_SCHEDULER_TEST
IS
   PROCEDURE Data_load (v_process_id NUMBER, v_name VARCHAR2)
   IS
   BEGIN
      DBMS_OUTPUT.PUT_LINE ('Data_Load Started ');

      INSERT INTO test_test1 (process_id, name)
           VALUES (v_process_id, v_name);

      COMMIT;
   EXCEPTION
      WHEN OTHERS
      THEN
         DBMS_OUTPUT.put_line ('sp_Data_load error');
   END;


   PROCEDURE proc_test (v_process_id NUMBER, v_name VARCHAR2)
   IS
   BEGIN
      DBMS_OUTPUT.PUT_LINE ('PROC_TEST STARTED ');

      FOR i IN 1 .. 10
      LOOP
         DBMS_OUTPUT.PUT_LINE ('Inside loop started');
         DBMS_SCHEDULER.CREATE_JOB (
            JOB_NAME          => 'Scheduler' || i,
            JOB_TYPE          => 'PLSQL_BLOCK',
            JOB_ACTION        => 'begin
                                           PKG_SCHEDULER_TEST.DATA_LOAD ('
                                          || v_process_id
                                          || ','
                                          || ''''
                                          || v_name
                                          || '); end;',
            START_DATE        => NULL,
            REPEAT_INTERVAL   => NULL,
            END_DATE          => NULL,
            ENABLED           => TRUE,
            COMMENTS          => ' Comments');
      END LOOP;

      DBMS_OUTPUT.PUT_LINE (' Lood ended');
   EXCEPTION
      WHEN OTHERS
      THEN
         DBMS_OUTPUT.put_line (
            'proc_test error' || SQLCODE || ',' || SQLERRM);
   END;
END PKG_SCHEDULER_TEST;

The above package was created successfully, but when I tried to run this package the following is the output

SQL> set serverout on
SQL> exec PKG_SCHEDULER_TEST.proc_test(1,'A
PROC_TEST STARTED
Inside loop started
Inside loop started
Inside loop started
Inside loop started
Inside loop started
Inside loop started
Inside loop started
Inside loop started
Inside loop started
Inside loop started
Lood ended

PL/SQL procedure successfully completed.

The question now is after the execution of this package, that the data is not loaded in the TEST_TEST1 table and no statement of output which is located in the Data_load procedure

Please guide me where I am doing wrong

Thank you

Take a close look at your JOB_ACTION

            JOB_ACTION        => 'begin
                                           PKG_SCHEDULER_TEST.DATA_LOAD ('
                                          || v_process_id
                                          || ','
                                          || ''''
                                          || v_name
                                          || '); end;',

It will come out with something like

begin
PKG_SCHEDULER_TEST.DATA_LOAD(1,'name); end;

See the problem?

Questions of DST, part two
Oracle 11.20.1.0 SE - One
Oracle Linux 5.6 x 86-64

Cut to the Chase. Most of our tasks in the Scheduler is set so that start_date, last_start_date, and next_run_date all specify them the zone with a fixed offset. As a result, the first execution after the time change DST, they ran an hour initially, but then calculation for the next execution corrected and they found running at the scheduled time.

Finally, almost.

We have two application schemas that have Task Scheduler.

Jobs in a schema is featured as above.

But all the work of the other schema to continue to run an hour earlier.

the above can be seen in the result of this query:
```
select
     instance_name
,     systimestamp
from
     v$instance;
--
select 
     owner
,     job_name
,     log_date
,     status
from
     dba_scheduler_job_log
here   log_date > sysdate - 10
  and   owner not in ('EXFSYS',
                      'ORACLE_OCM',
                      'PERFSTAT',
                      'SYS'
                      )
order by
     owner
,     job_name
,     log_date
;
```
Very easy to simply go to the bottom of the column LOG_DATE and see time to change.

For my first two questions is - can someone explain the behavior above, in particular the inconsistency in a single schema 'cure' jobs themselves after the first run after the time change, but another schema employment continuing to run an hour earlier.

I don't know if she's wearing on her or not, but most of the jobs (two patterns) is provided with a local function to "frequency" that uses a decimal representation of the time (ie: WEEKLY(.4583,'SATURDAY'))

And a second question - what are the things that affect the representation of time zone in the start_date when defining a new job? Our programmer creates / manages jobs using SQL Navigator, and there is no provision in the GUI it to specify a specific time zone or (offset vs name) method to represent a time zone. I read that there are some influences on the client side, but have not restored that right away.
Try
```
SELECT CAST (SYSDATE AS TIMESTAMP WITH TIME ZONE) FROM dual;
```
you will see the time zone.

Or a more detailed example
```
ALTER SESSION SET TIME_ZONE='Europe/Prague';
SELECT dbms_scheduler.stime, sysdate, systimestamp, current_timestamp,CAST (SYSDATE AS TIMESTAMP WITH TIME ZONE), CAST (to_date('1.1.2012','dd.mm.yyyy') AS TIMESTAMP WITH TIME ZONE) FROM dual;

ALTER SESSION SET time_zone='Asia/Bangkok';
SELECT dbms_scheduler.stime, sysdate, systimestamp, current_timestamp,CAST (SYSDATE AS TIMESTAMP WITH TIME ZONE), CAST (to_date('1.1.2012','dd.mm.yyyy') AS TIMESTAMP WITH TIME ZONE) FROM dual;

ALTER SESSION SET time_zone='-6:00';
SELECT dbms_scheduler.stime, sysdate, systimestamp, current_timestamp,CAST (SYSDATE AS TIMESTAMP WITH TIME ZONE), CAST (to_date('1.1.2012','dd.mm.yyyy') AS TIMESTAMP WITH TIME ZONE) FROM dual;
```
You can see that DATE to TIMESTAMP WITH TIME ZONE conversion session TIME_ZONE.

dbms_job question...
Hi all..

Please help with this question dbms_job.

I have a dbms_jobs(some procedure) that I started running "" every 5 minutes"".

Question:

If my proc lasts more than 5 minutes to complete. What insiders dbms_job another execution of this procedure?
or does stop until the current to complete? and lance another run after completing the existing

EX: My first run began at 10:00, the second round will start at 10:05.
But my first run is not yet up to 10:05.

The 2nd run wait until the first round ends?

Please let me know.

I thank in advance for the help...
Kumar wrote:
Hi all..

Please help with this question dbms_job.

I have a dbms_jobs(some procedure) that I started running "" every 5 minutes"".

What you mean?
Hear you that labour was presented with
```
INTERVAL => 'SYSDATE + (5 / (24 * 60))'
```
?

Question:

If my proc lasts more than 5 minutes to complete. What insiders dbms_job another execution of this procedure?
or does stop until the current to complete? and lance another run after completing the existing

EX: My first run began at 10:00, the second round will start at 10:05.
But my first run is not yet up to 10:05.

INTERVAL said when the next execution will start from the end of the period of the current run.
If a race starts at 10:00, the next run will not start until the ends that run.
If it ends at 10:04, the next run will start at 10:09.
If it ends at 10:05, the next series will begin at 10:10.
If it ends at 10:06, the next run will start at 10:11.

In addition, if you are using Oracle 10 or later version, you must use dbms_scheduler rather than dbms_job.
http://docs.Oracle.com/CD/B28359_01/AppDev.111/b28419/d_sched.htm#CIHHBGGI

Published by: Frank Kulash, 19 March 2012 10:52

Parallel execution of DBMS_SCHEDULER
Hello
I have a few procedures that I want to run in parallel for a batch, and I thought to create a job for each of them and a string of DBMS_SCHEDULER to run all together.
My question is, is it possible to order the number of jobs that are running simmultaneoulys? If I have 4 work that isn't really a problem, but if I get to 400 job I wouldn't have them all try to run together.

Thanks for your help

Published by: Pedro_gloria on May 5, 2011 11:58 (typo)
Hello

One way is that to store your procedure names in a table and their loop and keep to submit jobs with the name "SOMENAME1", "SOMENAME2" etc.

Inside the loop to keep control for the number of jobs in DBA_SCHEDULER_RUNNING_JOBS where job_name like 'UNNOM % '. IF the number is 4 then wait until she gets down like that.
```
DECLARE
   l_cnt          NUMBER;
BEGIN
   FOR i IN (SELECT * FROM table_procedure_names)
   LOOP
      l_sql       :=  --build your scheduler submit in dynamic sql with i.procedure_name use job names as say 'ORAJOB1','ORAJOB2'

      EXECUTE IMMEDIATE l_sql;

      LOOP
         SELECT COUNT (1)
           INTO l_cnt
           FROM DBA_SCHEDULER_RUNNING_JOBS
          WHERE job_name LIKE 'ORAJOB%';

         EXIT WHEN l_cnt < 4;
      END LOOP;
   END LOOP;
END;
```
Or you could also manage resources for a set of jobs by creating a job class and assigning a group of consumers of resources

http://www.Stanford.edu/dept/ITSS/docs/Oracle/10gR2/AppDev.102/b14258/d_sched.htm#i1011092

G.

Question about JOB_QUEUE_PROCESSES
DB version: 10.2.0.4
Operating system: Solaris

Question * 1 *.

If a DBMS_JOB x is running and if the value
```
ALTER SYSTEM SET JOB_QUEUE_PROCESSES = 0 ;
```
This will not affect the work running x. You just can't run any DBMS_JOB job more in the future. Right?

Question * 2 *.

In version 10.2, JOB_QUEUE_PROCESSES definition has no effect on DBMS_SCHEDULER. But workplace 11.2 JOB_QUEUE_PROCESSES affect both
Dbms_job and DBMS_SCHEDULER. Am I wrong?
1. set job_queue_processes 0 will not stop a running job.

2 Ronald Rood has a writeup in the various implications job_queue_processes here:
http://ronr.blogspot.com/2009/09/jobqueueprocesses-and-dbmsscheduler.html

DBMS_SCHEDULER and load balancing works
Hi all

I have a question about the DBMS_SCHEDULER jobs package.

We handle about 100000 records in a package and it takes a lot of time.
If we intend to divide the 100000 records in 5 batches of 20000 each and treat them at the same time.

For this we intend to schedule 5 jobs using the DBMS_SCHEDULER package.
These 5 jobs will be subject both to the database.

Now the question is, if we submit the 5 jobs at the same time, will oracle load balancing.
Suppose that if 5 jobs are treatment and 2 are fine and he finds jobs 3,4,5 are waiting for resources, then these jobs will be kept on hold and it once the tasks 1 and 2 are made, will begin work pending in the queue.

Receive your answer on that.

Thank you
Madhu K.
How you treat these records? 100,000 records isn't really a high volume of our days.

I'm not aware of anything in DBMS_SCHEDULER who will do what you asked, the jobs will run as planned and consume the resources that they require or wait until resources are available.

By breaking the lot well you will find that your treatment time increases (for example if you have managed to increase the claim within the system), you must identify the bottleneck in the current process before going on the road that you are trying.

The first step would be to see if there is anything in the process, you can adjust (see what consumes system resources and see if you can make more effective) and go from there. Possibly using AWR/StatsPack, TKPROF, etc... Depending on your version and that you have a license.

question of dbms_Scheduler

Similar Questions

Start

dbms_scheduler.set_job_anydata_value (job_name = > 'some_job', argument_position = > 1, argument_value = > SYS.) ANYDATA. ConvertClob ('blabla'));

end;

Start

dbms_scheduler.set_job_anydata_value (job_name = > 'some_job', argument_position = > 1, argument_value = > SYS.) ANYDATA. ConvertVarchar2 ('blabla'));

end;

Restrictions

Maybe you are looking for