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

Similar Questions

DBMS_SCHEDULER. CREATE_JOB and relaxation
Hi all,
Please inform if there is another way to create jobs in trigger to execute the batch file.

SQL > create table test (name varchar2 (200));

Table created.

SQL > create or replace
TRIGGER 2 AFT_INSERT
3. INSERT AFTER THE Test
4. FOR EACH LINE
5 REPORT
6 bis varchar2 (200);
7. START
8
9 create_job_through_trigger;
10
11 END;
12.

Trigger created.

SQL > insert into test values ('ff');
Insert into test values ('ff')
*
ERROR on line 1:
ORA-04092: cannot in a trigger
ORA-06512: at "SYS." DBMS_ISCHED', line 124
ORA-06512: at "SYS." DBMS_SCHEDULER', line 271
ORA-06512: in the 'END. VSM_SCHEDULER', line 5
ORA-06512: in the 'END. AFT_INSERT', line 5
ORA-04088: error during execution of trigger ' FINAL. AFT_INSERT'

The create_job_through_trigger

CREATE OR REPLACE PROCEDURE create_job_through_trigger
is

BEGIN
DBMS_SCHEDULER. () CREATE_JOB
job_name = > "fit."
job_type = > 'EXECUTABLE. "
job_action = > 'c:\a.bat ',.
activated = > false);
END;
/
Hi Isabelle,.

As we cannot engage in a trigger, which is explained by the fact to maintain a database of ACID properties.

A number of VALIDATION is required when the job is sent to the queue of work that can be done in the triggers.

You can use AUTONOMOUS TRANSACTIONS, which are independent transactions where you cannot perform a
engage in a Trigger.
```
 DECLARE
  PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
  /* Your Code Here */
  COMMIT;
END;
```
I am a friend in Oracle 9i, and we use DBMS_JOB. Submit() to submit a job to the queue and I don't know much about the
the schedular package for jobs.

Hope this might help you, little understanding...

Thank you
Shankar.

SYS. DBMS_SCHEDULER. CREATE_JOB
I have written following code, I think I know that this will run ipcards.ipcards_data procedure daily at 12:40:35 if I am not correct then what else is necessary.

BEGIN

SYS. DBMS_SCHEDULER. DROP_JOB

(job_name = > ' IPCARDS.) AVAILABLE_IP_CARDS_DATA');

END;

/

BEGIN

SYS. DBMS_SCHEDULER. CREATE_JOB

(

job_name = > ' IPCARDS. AVAILABLE_IP_CARDS_DATA'

, start_date = > TO_TIMESTAMP_TZ ('12:40:35.000000 21/01/2020 + 05:00 ',' yyyy/mm/dd hh24:mi:ss.ff tzh:tzm')

", repeat_interval = > ' FREQ = DAILY"

, end_date = > NULL

, job_class = > 'DEFAULT_JOB_CLASS '.

, job_type = > 'PLSQL_BLOCK '.

, job_action = > ' BEGIN ipcards.ipcards_data; END; '

, comments = > NULL

);

SYS. DBMS_SCHEDULER. SET_ATTRIBUTE

(name = > ' IPCARDS.) AVAILABLE_IP_CARDS_DATA'

, attribute = > 'RESTARTABLE.

value = > FALSE);

SYS. DBMS_SCHEDULER. SET_ATTRIBUTE

(name = > ' IPCARDS.) AVAILABLE_IP_CARDS_DATA'

, attribute = > 'LOGGING_LEVEL.

, value = > SYS. DBMS_SCHEDULER. LOGGING_OFF);

SYS. DBMS_SCHEDULER. SET_ATTRIBUTE_NULL

(name = > ' IPCARDS.) AVAILABLE_IP_CARDS_DATA'

attribute = > 'MAX_FAILURES');

SYS. DBMS_SCHEDULER. SET_ATTRIBUTE_NULL

(name = > ' IPCARDS.) AVAILABLE_IP_CARDS_DATA'

attribute = > 'MAX_RUNS');

BEGIN

SYS. DBMS_SCHEDULER. SET_ATTRIBUTE

(name = > ' IPCARDS.) AVAILABLE_IP_CARDS_DATA'

, attribute = > 'STOP_ON_WINDOW_CLOSE '.

value = > FALSE);

EXCEPTION

-can fail if the program is EXECUTABLE type...

WHILE OTHERS THEN

NULL;

END;

SYS. DBMS_SCHEDULER. SET_ATTRIBUTE

(name = > ' IPCARDS.) AVAILABLE_IP_CARDS_DATA'

, attribute = > 'JOB_PRIORITY '.

value = > 3);

SYS. DBMS_SCHEDULER. SET_ATTRIBUTE_NULL

(name = > ' IPCARDS.) AVAILABLE_IP_CARDS_DATA'

attribute = > 'SCHEDULE_LIMIT');

SYS. DBMS_SCHEDULER. SET_ATTRIBUTE

(name = > ' IPCARDS.) AVAILABLE_IP_CARDS_DATA'

, attribute = > 'AUTO_DROP '.

value = > TRUE);

SYS. DBMS_SCHEDULER. ENABLE

(name = > ' IPCARDS.) AVAILABLE_IP_CARDS_DATA');

END;

/
Seems to be correct, should start each day at 12:40:35 (zone + 05.00) from January 21, 2020. It takes 10 years to know if is correct or not ;)

Max
[My Italian blog Oracle | http://oracleitalia.wordpress.com/2010/01/17/supporto-di-xml-schema-in-oracle-xmldb/]

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?

How to refresh a materialized with DBMS_SCHEDULER view. CREATE_JOB();

I am trying to refresh the MView manually (on request). For this
1. I created a MV.
2. then a SP for update using DBMS_MVIEW. REFRESH()
3. and then anonymous block for CREATE_JOB
But the job is not running. Its status is failed display.
When I tried to run
DBMS_SCHEDULER. RUN_JOB ('MY_MVIEW_REFRESH', TRUE); -No performance
But DBMS_SCHEDULER. RUN_JOB ('MY_MVIEW_REFRESH', FALSE); -Execution successfully.
So, please suggest, what should I do to update.
Mv_emp CREATE MATERIALIZED VIEW
IMMEDIATE CONSTRUCTION
REFRESH THE STRENGTH TO DEMAND
ACTIVATE THE QUERY REWRITING
AS
SELECT deptno, SUM (sal) OF emp
GROUP BY deptno;
CREATE OR REPLACE PROCEDURE refresh_mv_emp
AS
BEGIN
DBMS_MVIEW. REFRESH ('MV_EMP');
END;
BEGIN
DBMS_SCHEDULER. CREATE_JOB
(
job_name = > 'MY_MVIEW_REFRESH ',.
job_type = > 'PLSQL_BLOCK ',.
job_action = > 'REFRESH_MV_EMP ',.
number_of_arguments = > 0,
start_date = > SYSTIMESTAMP,
repeat_interval = > 'FREQ = DAILY;',
End_date = > NULL,
enabled = > TRUE,
auto_drop = > FALSE,
Comments = > 'refresh MV_EMP daily job. "
);
END;

I'm surprised that it worked with the value TRUE. Apparently oracle encapsulates job action in BEGIN END during the performance of work in a separate session. In any case, change of employment to procedure_stockee type:

SQL > CREATE MATERIALIZED VIEW mv_emp
2 BUILD IMMEDIATE
3 REFRESH FORCE ON REQUEST
4. TURN ON QUERY REWRITE
5 AS
6. SELECT deptno, SUM (sal) sum_sal FROM emp
7 GROUP BY deptno;

Materialized view created.

SQL >

SQL > CREATE OR REPLACE PROCEDURE refresh_mv_emp
2 AS
3 BEGIN
DBMS_MVIEW 4. REFRESH ('MV_EMP');
5 END;
6.

Created procedure.

SQL > START
2 DBMS_SCHEDULER. CREATE_JOB
3 (
job_name 4-online "MY_MVIEW_REFRESH."
job_type 5-online 'Procedure_stockee', 'PLSQL_BLOCK ',.
6 job_action => 'REFRESH_MV_EMP. "
7 number_of_arguments-online 0
start_date 8-online SYSTIMESTAMP.
repeat_interval 9-online 'FREQ = all DAYS;',
10-online NULL end_date,
11 active => TRUE,
12 auto_drop => FALSE,
13 comments => "this job refresh MV_EMP every day.
14 );
15 END;
16.

PL/SQL procedure successfully completed.

SQL > exec DBMS_SCHEDULER. RUN_JOB ('MY_MVIEW_REFRESH', TRUE);

PL/SQL procedure successfully completed.

SQL > exec DBMS_SCHEDULER. RUN_JOB ('MY_MVIEW_REFRESH', FALSE);

PL/SQL procedure successfully completed.

SQL >

SY.

Add the date and time in DBMS_SCHEDULER. Name of the job CREATE_JOB
Hello
I have a JDeveloper application that needs to create

'DBMS_SCHEDULER. CREATE_JOB ().

The problem which I am facing is that I might need to create two jobs that may be waiting at the same time. When this happens, I get an error saying that the name of this work already exists.

So I tried to create the name of the task so that it has the data and the time that the job was created, which will give it a unique identifier. But when I tried the following I have an invalid name for the database object error.

Start
DBMS_SCHEDULER. () CREATE_JOB
"EmailJobDefinition" | TO_CHAR (SYSDATE, "DD-MM-YY HH24:MI:SS) |".
"PLSQL_BLOCK,"
"BEGIN EMAIL. SEND_LONG_MAIL('','','','') END '.
0,
TO_DATE (March 12, 2009 09:30 ',' MM/DD/YYYY HH24:MI:SS'),
NULL,
NULL,
"DEFAULT_JOB_CLASS,"
FAKE-WHAT IS TRUE?
TRUE,
'Comments');
end;

Is it possible to integrate the name of employment, the date and time?

Thank you
Steve
Try this way:

"EmailJobDefinition" | TO_CHAR (sysdate, 'YYYYMMDDHH24MISS') | ".

Max

DBMS_SCHEDULER send E-mail

Hello
I have a scenario where I have to send the email notification to multiple recipients via DBMS_Scheduler. The problem is that the list is in a table. Is this possible via DBMS_Scheduler? Could you please send me some tips on this?
Thank you
Shifa.

Well,.

The add_job_email_notification is supposed to send emails on the events of employment, such as "labor", "the work has", 'work has ceased', etc.

If this procedure is on the changes of State jobs, and there is not much that you can customize in the body of the email.

I don't know if that's what you're looking for.

If you are looking for a procedure to send mails at a time fixed and not based on job events, then I guess you can find many examples of procedures sends messages via PL/SQL. Once you have a job, you can program it via the Planner to your desired schedule.

Basically, it would look like this (example of daily at 07:00):

DBMS_SCHEDULER. Create_Job (job_name-online 'Send_Mail_Job',

job_type-online "procedure_stockee."

job_ation-online "your_mailing_procedure."

repeat_interval => ' FREQ = DAILY; BYHOUR = 7,

enabled-TRUE online

);

Once your procedure is ready, I can help you with planning it

DBMS_SCHEDULER job does not

Hi gurus of the oracle
I created a scheduler job to GATHER_STATS. but it's not not running.

BEGIN

DBMS_SCHEDULER. () CREATE_JOB

job_name = > 'GATHER_SCHEMA_STATS ',.

job_type = > 'PLSQL_BLOCK ',.

job_action = > ' START

DBMS_STATS. GATHER_SCHEMA_STATS ("RING_TEST");

END;',

start_date = > 11 July 2014 04.28.00AM AMERICA/New_York '.

repeat_interval = > 'FREQ = WEEKLY'.

enabled = > TRUE,

Comments = > "Collection of statistics from schema");

END;

/

I could run this work manually, but its starts not at all, nothing is there in the alert also log.
Thanks in advance
Concerning
REDA

Hi reda,.

I guess that's normal because you specified a start_date in July 2014, while labour will not start before that.

DBMS_SCHEDULER. CREATE. JOBS... SP2-02734
Hello
I m confused. In the past, I guess I could call a program (in the database) by running create_job start_date = sysdate.

show my program, he calls a shell script.
SELECT the owner, program_name, program_action from dba_scheduler_programs where program name = "MY_PROGRAM";
.......

Start the program now.
User myuser has the right SCHEDULER_ADMIN.

# > sqlplus myuser/pass@instance.

SQL > DBMS_SCHEDULER. CREATE_JOB (job_name = > 'CALL_MY_PROGRAM_NOW', program_name = > "MY_PROGRAM", start_date = > sysdate, active = > TRUE);
..... SP2-0734: unknown command "DBMS_SCHED" ab... »...

?.
I think that I did in the past without error :-(
Can anyone help?
Thank you
* T

Published by: tbrinkmann on May 24, 2011 12:30 AM
I think in the past, you put your code between begin and end.

# > sqlplus myuser/pass@instance
Start
DBMS_SCHEDULER. CREATE_JOB (job_name => "CALL_MY_PROGRAM_NOW", program_name => "MY_PROGRAM", start_date-online sysdate, active => TRUE);
end;
/

Why ORA-06512: at "SYS." DBMS_SCHEDULER', line 1794
Hi, I do the following

-creation of a beginning of program
BEGIN
() dbms_scheduler.create_program
program name = > "MAINTAIN_DDI_PROGRAM"
program_type = > 'procedure_stockee ',.
program_action = > 'MAINTAIN_DDI ',.
number_of_arguments = > 1,
activated = > FALSE,
Comments = > 'MAINTAIN_DDI');
END;
/
-creation of a program end

-set the program argument starts
BEGIN
() dbms_scheduler.define_program_argument
program name = > "MAINTAIN_DDI_PROGRAM"
argument_name = > 'p_User ',.
argument_position = > 1,
argument_type = > 'VARCHAR2 ',.
default_value = > 'SYSTEM');
END;
/
-end of the argument to define program

-creation of schedules departure
Start
() DBMS_SCHEDULER.create_schedule
schedule_name = > "MAINTAIN_DDI_SCHEDULE"
start_date = > SYSTIMESTAMP,
repeat_interval = > ' FREQ = DAILY; BYHOUR = 0',
End_date = > ",
Comments = > 'MAINTAIN_DDI_SCHEDULE_COMMENTS');
end;
/

-creation of end times

-creation of the beginning of the task
Start

DBMS_SCHEDULER. () CREATE_JOB
job_name = > 'MAINTAIN_DDI_JOB ',.
program name = > "MAINTAIN_DDI_PROGRAM"
schedule_name = > 'MAINTAIN_DDI_SCHEDULE');

() DBMS_SCHEDULER.set_attribute
name = > 'MAINTAIN_DDI_JOB ',.
attribute = > "job_class"
value = > "daily_job_class");

end;
/
-activation of the start of work
SQL > exec DBMS_SCHEDULER. SELECT ("MAINTAIN_DDI_JOB");
DBMS_SCHEDULER BEGIN. SELECT ("MAINTAIN_DDI_JOB"); END;

*
ERROR on line 1:
ORA-27486: insufficient privileges
ORA-06512: at "SYS." DBMS_ISCHED', line 2751
ORA-06512: at "SYS." DBMS_SCHEDULER', line 1794
ORA-06512: at line 1
-end of jobs

---

-> Why don't I have this error?

SQL > select distinct privilege of user_sys_privs;

PRIVILEGE
----------------------------------------
CREATE JOBS
UNLIMITED TABLESPACE
MANAGE SCHEDULER

= > cannot be doesn't have enough privileges listed in the Administrator's Guide to Oracle database on pg 27-2

to turn on work, I just need to own.

SELECT job_name, job_type, job_action, owner, system, activated from all_scheduler_jobs;

OWNER JOB_NAME J JOB_ACTION SYSTEM ENABL
-------- ----------------------- - ------------------------------ ----- -----
PROCMASK MAINTAIN_DDI_JOB_2 TRUE FALSE
PROCMASK MAINTAIN_DDI_JOB FALSE FALSE

So I created another job using a program named with the same name of program but no schedule_name

BEGIN
DBMS_SCHEDULER. () CREATE_JOB
job_name = > 'MAINTAIN_DDI_JOB_2 ',.
program name = > "MAINTAIN_DDI_PROGRAM"
repeat_interval = > ' FREQ = DAILY; BYHOUR = 12',
Comments = > "every day at noon");
END;
/

DBMS_SCHEDULER exec. SELECT ("MAINTAIN_DDI_JOB_2");

Why am I able to allow a job created a program called aid, but not able to allow a job using a program named creation and a calendar of name?

Thank you very much!

Published by: oraclewannabe2 on September 23, 2008 20:55
Hello

You probably need to grant access to the owner of the task running on the job class.

Login as SYS or the creator of the category of jobs and

Grant execute on sys.daily_job_class to job_owner;

Hope this helps,
Ravi.

Running a file IS in Windows using DBMS_SCHEDULER
My Oracle db is on a Windows machine, and I try to call a file BACK BAT using DBMS_SCHEDULER

I am new to Oracle, but the code that I have worked so far is:

BEGIN
DBMS_SCHEDULER.drop_job ("testjob");
DBMS_SCHEDULER. () CREATE_JOB
job_name = > 'testjob. "
job_type = > 'EXECUTABLE. "
job_action = > "c:\windows\system32\cmd.exe /c c:\test.bat > zero".
auto_drop = > false,
enabled = > TRUE
);
DBMS_SCHEDULER.run_job ("testjob");
END;

And I have permission to CREATE a TASK EXTERNAL to my user.

The test BAT file I call deletes all just another file (just to prove the concept that I can actually run the BAT file). The code above seems to work very well (with SQL Developer) but the BAT file doesn't seem to actually do anything. If I run the BAT file manually (by double-clicking), it removes the target file. But where through Oracle he never did.

If I change the name of test.bat in the code above into a file that does not exist, I get an error - prove that at least Oracle is to find the BAT file.

Any ideas? Anyone got something similar to work on a Windows machine?

using Oracle job e-mail notification

Hello
I am trying to configure a job e-mail notification using Oracle 11 GR 2. By documnetation online, I made the following configuration, but email notification work is a failure. If you guys have any ideas, please help.
Step 1:
BEGIN
DBMS_SCHEDULER.set_scheduler_attribute ('email_server', 'oracle.kotaise.com:25');
DBMS_SCHEDULER.set_scheduler_attribute ('email_sender', ' [email protected]');
END;
/
Step 2:
BEGIN
() DBMS_SCHEDULER.create_job
job_name = > 'email_notification_job ',.
job_type = > 'PLSQL_BLOCK ',.
job_action = > ' NULL BEGIN; END;',
start_date = > SYSTIMESTAMP,
repeat_interval = > ' freq = minutely; BYSECOND = 0',
enabled = > TRUE);
END;
/
Step 3:
BEGIN
DBMS_SCHEDULER. () ADD_JOB_EMAIL_NOTIFICATION
job_name = > 'email_notification_job ',.
recipients = > ' [email protected] ',
sender = > ' [email protected] ',
subject = > 'Scheduler Job Notification-%job_owner%.%job_name%-%event_type%. "
body = > ' event_type % occurred at % event_timestamp. ERROR_MESSAGE %'.
events = > "JOB_FAILED, JOB_BROKEN, JOB_DISABLED, JOB_SCH_LIM_REACHED");
END;
/
Step 4:
I created the following post that runs a package that runs a package "test_package.pdata". This package is not created yet, because I wanted to see if the email notification works or not. As expected the 'TEST_JOB' failed due to missing package. But notification email '' email_notification_job' ' work, which takes place every minute, cannot send an e-mail notification.
BEGIN
SYS. DBMS_SCHEDULER. CREATE_JOB
(
job_name = > 'test_job '.
, start_date = > SYSTIMESTAMP
, repeat_interval = > ' freq = minutely; BYSECOND = 0'
, end_date = > NULL
, job_class = > 'DEFAULT_JOB_CLASS '.
, job_type = > 'PLSQL_BLOCK '.
, job_action = > ' BEGIN test_package.pdata; END; »
, comments = > NULL
enabled = > TRUE
);
end;
/
I questioned the DBA_SCHEDULER_NOTIFICATIONS table, and I see that email notification work has not begun.
JOB_NAME EVENT RECIPIENT
EMAIL_NOTIFICATION_JOB [email protected] JOB_FAILED
EMAIL_NOTIFICATION_JOB [email protected] JOB_BROKEN
EMAIL_NOTIFICATION_JOB [email protected] JOB_SCH_LIM_REACHED
EMAIL_NOTIFICATION_JOB [email protected] JOB_DISABLED
Thank you

OK, now I understand your lack of understanding

The ADD_JOB_EMAIL_NOTIFICATION procedure relates to employment that you specify in the parameter job_name. In your case, e-mail notifications will be sent against your email_notification_job, no test_job. You must use the ADD_JOB_EMAIL_NOTIFICATION for all the jobs you are interested in the result. So if you are interested in the results of running TEST_JOB, then you must specify this work for the ADD_JOB_EMAIL_NOTIFICATION procedure.

simple external task works in windows 7 Enterprise, but not windows 2008 R2, Enterprise Edition.

SQL * more: 11.2.0.1.0 output
widows 7 sp1 and company 2008 sp1
The task runs without error on both environments of windows 7, but the job fails on windows 2008 with:
Error 255
"EXTERNAL_LOG_ID ="job_89424_68834 ",
ORA-27369: jobs of type EXECUTABLE failed with exit code: extended attributes are incompatible.
"
I know that's not the credentials that I can replace it with another undefined user and it will tell me the username and/or password is not valid.
I create a directory specified with the user in question and checked I can read/write in it.
without arguments to cmd.exe job, I still get the error.
Joe can run the cmd.exe without problem.
Is there some slight difference in windows 7 and 2008 server (security?) that would explain this?
the user joe is a member of local administrators and ora_dba on all servers groups
employment and identification information defined as follows:
BEGIN
() sys.dbms_scheduler.create_credential
username = > 'joe. "
password = > joespassword,
database_role = > NULL,
windows_domain = > NULL,
Comments = > NULL,
credential_name = > ""DBREP"". "" Joe' "
);
END;
BEGIN
SYS. DBMS_SCHEDULER. () CREATE_JOB
job_name = > "'BLAH'". "test" ', "
job_type = > 'EXECUTABLE. "
job_action = > "C:\Windows\System32\cmd.exe"
number_of_arguments = > 0,
start_date = > NULL,
repeat_interval = > NULL,
End_date = > NULL,
job_class = > ' 'SYS '. ' ' DEFAULT_JOB_CLASS ' ',
activated = > FALSE,
auto_drop = > FALSE,
Comments = > ",
credential_name = > "'BLAH'". "" Joe' ',
destination_name = > NULL);
SYS. DBMS_SCHEDULER. () SET_JOB_ARGUMENT_VALUE
job_name = > "'BLAH'". "test" ', "
argument_position = > 1,
argument_value = > ' / c ');
SYS. DBMS_SCHEDULER. () SET_JOB_ARGUMENT_VALUE
job_name = > "'BLAH'". "test" ', "
argument_position = > 2,
argument_value = > 'dir');
SYS. DBMS_SCHEDULER. () SET_JOB_ARGUMENT_VALUE
job_name = > "'BLAH'". "test" ', "
argument_position = > 3,
argument_value = > 'c:\temp');
SYS. DBMS_SCHEDULER. SET_ATTRIBUTE)
name = > ' 'BLAH '. "' test ' ',
attribute = > 'logging_level', value = > DBMS_SCHEDULER. LOGGING_FULL);
SYS. (DBMS_SCHEDULER). Enable
name = > ' 'BLAH '. ("' test ' ');
END;
/

Thank you Greg,.

I appreciate it.

Job - planning with a commit records fit

Hi Experts,
Oracle DB 11g XE - Version
I planned a work using dbms_scheduler that will insert a record in table T for every minute. I does not COMMIT inside my procedure but records are committed after each successful run. How is it possible.
Here is my code.

SQL > create table t (empno number, creation_date date);

Table created

SQL > create or replace procedure test_proc
2 is
3
4 start
5
6 insert into t values (1, sysdate);
7
8 end;
9.

Procedure created

SQL > START
2 DBMS_SCHEDULER. () CREATE_JOB
job_name 3 = > "test_job"
job_type 4 = > "PLSQL_BLOCK"
5 job_action = > ' BEGIN test_proc; END;',
6 = start_date > cast (sysdate as timestamp with time zone).
7 repeat_interval = > ' FREQ = MINUTELY ",
8 = end_date > cast (sysdate + 1 as a timestamp with time zone).
9 license = > TRUE,
10 comments = > 'insert record into table t');
11 END;
12.

PL/SQL procedure successfully completed

SQL > select * from t;

EMPNO CREATION_DATE
---------- -------------
11/12/2013 1, 11
11/12/2013 1, 11
11/12/2013 1, 11
11/12/2013 1, 11
11/12/2013 1, 12
11/12/2013 1, 12

11/12/2013 1, 12
11/12/2013 1, 12
11/12/2013 1, 12

9 selected lines

See you soon,.
Suri

Suri wrote:

Hello

Here my question is not related to commit / rollback when the session completes normal/abnormal. My question is related to the job in Oracle.

See you soon,.

Suri

In fact, it's what is talking about your question.

When you schedule a task to run, it does not work in your current session, but in a session created for this work at the same time that it runs. When the work is done, the session is 'exit' and by default, the pending transactions are committed. The same goes if you do with DBMS_JOB and DBMS_SCHEDULER.

The difference with DBMS_JOB and DBMS_SCHEDULER, is when you actually submit the work with DBMS_SCHEDULER, appeal procedure issues a commit of your current session, submit a job with DBMS_JOB does not validate your current session.

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. Question CREATE_JOB

Similar Questions

Maybe you are looking for