Execute dbms_scheduler

Hi,
I have declared a job and schedule
BEGIN
DBMS_SCHEDULER.CREATE_SCHEDULE(
schedule_name => 'BACKUP_RMAN_SCHEDULE',
start_date => trunc(sysdate)+11/24,
repeat_interval => 'FREQ=DAILY; BYDAY=MON,TUE,WED,THU,FRI,SAT,SUN; BYHOUR=11',
comments => 'Every day at 10 am');
END;
BEGIN
DBMS_SCHEDULER.CREATE_JOB (
job_name => 'BACKUP_RMAN_JOB',
job_type => 'EXECUTABLE',
job_action => '/usr/bin/ksh',
schedule_name => 'BACKUP_RMAN_SCHEDULE',
number_of_arguments => 2);
DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(
job_name => 'BACKUP_RMAN_JOB',
argument_position => 1,
argument_value => '/home/oracle/BackupDatabaseViaRMAN.ksh');
DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(
job_name => 'BACKUP_RMAN_JOB',
argument_position => 2,
argument_value => 'RSAPROD2');
END;
When the job run i have an error
ORA-27369: echec du travail de type EXECUTABLE avec le code sortie : Key has exp
ired
STANDARD_ERROR="/usr/bin/ksh: line 1: /home/oracle/BackupDatabaseViaRMAN.ksh: no
t found"
When i run this job without schedule all is right.
I d'ont understand why.
Regards

Check following MOS note.
DBMS_SCHEDULER job fails on RHEL5 with ORA-27369-...Key has expired (Doc ID 739402.1)

Similar Messages

Error executing DBMS_SCHEDULER

I am getting the following error ::
select log_date,additional_info from user_scheduler_job_run_details where log_date = (select max(log_date) from user_scheduler_job_run_details);
LOG_DATE
ADDITIONAL_INFO
11-JAN-07 05.34.00.23434 AM -8:00
STANDARD_ERROR="/dev/fd/0: uname: not found
/dev/fd/0: test: argument expected
Can anybody suggest some solution to this?
Thanks in advance.

I cant paste scripts as they are developed for companies client.
Message was edited by:
SarangKale

Q: Impact of use_current_session parameter of dbms_scheduler.run_job

On the 11g db that I have access to, I'm seeing different systimestamp value while running plsql block using
dbms_scheduler.run_job with use_current_session = true and false.
My job looks like following.
dbms_scheduler.create_job(
job_name => 'tk2timestamp_test',
job_type => 'PLSQL_BLOCK',
job_action => 'begin insert into tktest values (systimestamp, to_char(sysdate, ''DD-MON-YYYY HH24:MI:SS''), current_timestamp, localtimestamp, dbtimezone, sessiontimezone); end;',
enabled => true,
auto_drop => false);
I see that UTC time was returned as systimestamp if it is called with true and PST if it is called with false.
In the same session, I get following result with select statement.
select systimestamp, current_timestamp, localtimestamp, dbtimezone, sessiontimezone from dual;
SYSTIMESTAMP CURRENT_TIMESTAMP LOCALTIMESTAMP DBTIMEZONE SESSIONTIM
27-MAR-13 04.05.59.914647 PM +00:00 27-MAR-13 09.05.59.914650 AM -07:00 27-MAR-13 09.05.59.914650 AM +00:00 -07:00
Can any one let me know why this is happening? Why systimestamp value is not PST if use_current_session = true?

Thank you again for your response.
I've got following result.
SQL> SELECT SYSTIMESTAMP FROM dual;
SYSTIMESTAMP
28-MAR-13 07.13.08.556079 PM +00:00
SQL> SELECT SYSTIMESTAMP AT TIME ZONE 'PDB' FROM dual;
SELECT SYSTIMESTAMP AT TIME ZONE 'PDB' FROM dual
ERROR at line 1:
ORA-01882: timezone region not found
SQL> SELECT SESSIONTIMEZONE,CURRENT_TIMESTAMP, LOCALTIMESTAMP FROM dual;
SESSIONTIM CURRENT_TIMESTAMP LOCALTIMESTAMP
-07:00 28-MAR-13 12.13.41.196653 PM -07:00 28-MAR-13 12.13.41.196653 PM
BTW, I have two instances returns the result like this if this information helps.
I've created following table in order to help proving something is changing whether I pass true or false to use_current_session parameter when calling dbms_scheduler.run_job.
create table tktest (tksystimestamp timestamp(6), tktocharsysdate varchar2(100), tkcurrent_timestamp timestamp(6), tklocaltimestamp timestamp(6), tldbtimezone varchar2(100), tksessiontimezone varchar2(100));
Then I created job as following. This job inserts systimestamp,sysdate,current_timestamp,localtimestamp,dbtimezone, and sessiontimezone to above table.
begin
dbms_scheduler.create_job(
job_name => 'tk2timestamp_test',
job_type => 'PLSQL_BLOCK',
job_action => 'begin insert into tktest values (systimestamp, to_char(sysdate, ''DD-MON-YYYY HH24:MI:SS''), current_timestamp, localtimestamp, dbtimezone, sessiontimezone); end;',
enabled => true,
auto_drop => false);
exception
when others then
null;
end;
Run the job using run_job procedure.
exec dbms_scheduler.run_job(job_name => 'tk2timestamp_test',use_current_session => true);
Above inserts following record in tktest.
SYSTIMESTAMP SYSDATE CURRENT_TIMESTAMP LOCALTIMESTAMP DBTZ SESSIONTZ
28-MAR-13 07.04.58.227616 PM 28-MAR-2013 19:04:58 28-MAR-13 07.04.58.227617 PM 28-MAR-13 07.04.58.227617 PM +00:00 +00:00
Run the job using run_job procedure again but use 'use_current_session => false' this time.
Above inserts following record in tktest.
SYSTIMESTAMP SYSDATE CURRENT_TIMESTAMP LOCALTIMESTAMP DBTZ SESSIONTZ
28-MAR-13 12.05.24.150817 PM 28-MAR-2013 12:05:24 28-MAR-13 12.05.24.150819 PM 28-MAR-13 12.05.24.150819 PM +00:00 -07:00
I also run following from the same session.
SQL> select systimestamp, current_timestamp, localtimestamp, dbtimezone, sessiontimezone from dual;
SYSTIMESTAMP CURRENT_TIMESTAMP LOCALTIMESTAMP DBTZ SESSIONTZ
28-MAR-13 07.05.40.640499 PM +00:00 28-MAR-13 12.05.40.640503 PM -07:00 28-MAR-13 12.05.40.640503 PM +00:00 -07:00
So why executing dbms_scheduler.run_job with 'use_current_session => false' causes SEESSIONTIMEZONE to be PST8PDT?
I have an another instance pointing all the time based on UTC and my question is why only above instance is showing result like above and what causes it.
thx.

Oracle 10g R2 dbms_scheduler ora-00054

Hi,
I am using dbms_scheduler in Oracle 10g R2 to process a list of requests in a table queue. I am using job chains in my package. I realize that, at times, one of the chain step can fail with Ora-00054 error. Can we rectify the situation by adding a chain rule that if job failed due to Ora-00054 error, execute 'dbms_scheduler.alter_running_chain(jobname,stepname,'STATE','NOT_STARTED') and expect the job to run again?

Hi,
It is possible to do this. Let the step which fails be step-x You would need to create a new step e.g. rerun-step-x which points to a program that would do an alter running chain to set both step-x and rerun-step-x to not _started.
In the rule you would check if ':step-x:state=''FAILED'' and :step-x.error_code=54' and if so start rerun-step-x .
You can see the exact syntax supported here
http://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_sched.htm#CHDBAFJE
Hope this helps,
Ravi.

Got ORA error when trying to execute external file using scheduler

Hi All,
I have executed the below program. In the log i have seen the error like below
BEGIN
dbms_scheduler.create_job('"TEST_JOB_EXE2"',
job_type=>'EXECUTABLE', job_action=>
'/home/upncommon/pub/test123'
, number_of_arguments=>0,
start_date=>TO_TIMESTAMP_TZ('23-AUG-2013 05.35.27.557242000 AM -04:00','DD-MON-RRRR HH.MI.SSXFF AM TZR','NLS_DATE_LANGUAGE=english'), repeat_interval=>
'freq = minutely;'
, end_date=>TO_TIMESTAMP_TZ('24-AUG-2013 05.35.27.000000000 AM ASIA/CALCUTTA','DD-MON-RRRR HH.MI.SSXFF AM TZR','NLS_DATE_LANGUAGE=english'),
job_class=>'"DEFAULT_JOB_CLASS"', enabled=>FALSE, auto_drop=>FALSE,comments=>
'Job to test use of dbms_scheduler'
dbms_scheduler.set_attribute('"TEST_JOB_EXE2"','credential_name',
'"EXECUTABLE"');
dbms_scheduler.enable('"TEST_JOB_EXE2"');
COMMIT;
END;
"EXTERNAL_LOG_ID="job_196709_23673",
ORA-27369: job of type EXECUTABLE failed with exit code: Input/output error
STANDARD_ERROR="Launching external job failed: Login executable not setuid-root""

my version details are:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
"CORE 11.2.0.3.0 Production"
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production

Dbms_scheduler and state

Hi,
I am using dbms_scheduler to do some of my jobs.
Some times I observed that, the job goes in 'SCHEDULED' state, I would like to know the reason behind it.
The machine I want to run the job has free space/memory, so I don't think that could be the reason.
Any inputs?
Thanks

In your creation you did not specify start_date,repeat interval attributes...
Also there is no attribute by name 'destination' corresponds to job.
Reference:
http://download-uk.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_sched.htm#CIHCIDII
My workout may help you to understand
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - 64bi
PL/SQL Release 10.1.0.4.0 - Production
CORE 10.1.0.4.0 Production
TNS for Solaris: Version 10.1.0.4.0 - Production
NLSRTL Version 10.1.0.4.0 - Production
SQL>
SQL> ed
Wrote file afiedt.buf
1 begin
2 dbms_scheduler.create_job (job_name => 'test_job', job_type => 'plsql_block
',job_action => 'insert into dept select * from dept;',auto_drop => false, enabl
ed => false);
3* end;
SQL> /
PL/SQL procedure successfully completed.
SQL> select job_name,state,start_date,next_run_date from dba_scheduler_jobs
2 where job_name='TEST_JOB';
JOB_NAME STATE
START_DATE
NEXT_RUN_DATE
TEST_JOB DISABLED
Now I tried to enabled the job, but enabled column said FALSE.
SQL> execute dbms_scheduler.enable('TEST_JOB');
PL/SQL procedure successfully completed.
SQL> select job_name,state,start_date,next_run_date,enabled from dba_scheduler_j
obs
2 where job_name='TEST_JOB';
JOB_NAME STATE
START_DATE
NEXT_RUN_DATE
ENABL
TEST_JOB SUCCEEDED
FALSE
SQL>
I think it is because, there is no start_date, no interval. Observe I got SUCCEEDED in state column.
I got the error as follows by setting 'destination' attribute...
SQL> execute dbms_scheduler.set_attribute('TEST_JOB','destination','hosted:12345
BEGIN dbms_scheduler.set_attribute('TEST_JOB','destination','hosted:12345'); END
ERROR at line 1:
ORA-03001: unimplemented feature
ORA-06512: at "SYS.DBMS_ISCHED", line 814
ORA-06512: at "SYS.DBMS_SCHEDULER", line 1209
ORA-06512: at line 1
Moreover you cannot run a job which is disabled...
SQL> execute dbms_scheduler.run_job('TEST_JOB');
BEGIN dbms_scheduler.run_job('TEST_JOB'); END;
ERROR at line 1:
ORA-27460: cannot execute disabled job "DCP.TEST_JOB"
ORA-06512: at "SYS.DBMS_ISCHED", line 148
ORA-06512: at "SYS.DBMS_SCHEDULER", line 374
ORA-06512: at line 1
I don't know how you are using it for your work...
See the following, there is a purge job which got scheduled and has next run date...
SQL> select state,job_name,next_run_date from dba_scheduler_jobs where job_name=
'PURGE_LOG';
STATE JOB_NAME
NEXT_RUN_DATE
SCHEDULED PURGE_LOG
15-MAR-07 03.00.00.200000 AM +00:00
SQL>

ORA-27369: job of type EXECUTABLE failed with exit code:No such file or dir

Hi all,
i am new with DBMS_SCHEDULER and my need is to create a job, without program and schedule, that i can call in an Apex app.
This job run a window *.bat* file via cmd.exe
I test the .bat with doubleclick and it work.
I test window run with the string c:\windows\system32\cmd.exe/c C:/mycompletepath/myfilename.bat > nul and it work.
I execute the following execute DBMS_SCHEDULER.create_job (
               job_name=>'EIM_JOB',
               job_type=>'EXECUTABLE',
               job_action=>'c:\windows\system32\cmd.exe',
               number_of_arguments=>1,
               auto_drop=>FALSE,
               enabled=>FALSE,
               comments=>'Job Lancio EIM'
          ); and the job is created.
I execute this execute DBMS_SCHEDULER.set_job_argument_value('EIM_JOB',1,' /c C:/mycompletepath/myfilename.bat > nul');
execute DBMS_SCHEDULER.enable('EIM_JOB');
execute DBMS_SCHEDULER.PURGE_LOG(job_name=>'EIM_JOB');
execute DBMS_SCHEDULER.run_job('EIM_JOB');but the error ORA-27369: job of type EXECUTABLE failed with exit code: No such file or directory is raised
The argument is uge and reading about it here https://forums.oracle.com/forums/thread.jspa?threadID=701740 here https://forums.oracle.com/forums/thread.jspa?threadID=555102 and here http://www.oracle-base.com/articles/11g/SchedulerEnhancements11gR1.php_ i suppose that my problem is quite about credentials but i need some help or tips to clearly identify, verify and solve the problem.
Any kind of help will be appreciated.
Thanks
Alex

Hi Ravi,
thank you for your helpful reply.
I am changing my script in order to meet your advices but when i run this execute DBMS_SCHEDULER.CREATE_CREDENTIAL (
   credential_name=>'SIECRMWIN',
   username=>'myusername',
   password=>'mypassword',
   database_role=>NULL,
   windows_domain=>'SIECRM',
   comments=>'Windows credential to run job'); the error PLS-00302: component 'CREATE_CREDENTIAL' must be declared is raised.
My DB is Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE     10.2.0.5.0     Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.5.0 - Productio
NLSRTL Version 10.2.0.5.0 - ProductionWhich is my mistakes?
Searchibg the internet i found this OracleJobScheduler Windows service, how i can verify if service exist and start it on my server?
Thanks again for any kind of help.
Edited by: OraclePSP on 23-mar-2012 5.59

"can not start a job" issue in AWM

Hi ALL,
I am maintaining my cube from PLSQL with following options
1. buildtype = "BACKGROUND"
2. trackstatus = "true"
3. maxjobqueues = 3
i get following error when i see the "olapsys.xml_load_log" table
***Error Occured: Failed to Build(Refresh) DB_OWNER.MY_ANALYTICAL_WORKSPACE Analytic Workspace. Can not start a job.
Can anybody explain when and why this error occurs? I have wasted a lot of time searching for this issue, but have found no person facing such issue.
Hi Keith, it will be great if you can answer this one.
My database version is 10.2.0.4.0 and AWM version is also 10.2.0.3.0
Kind Regards,
QQ
Message was edited by:
dwh_10g

Applies to:
Oracle OLAP - Version: 10.1 to 11.1
This problem can occur on any platform.
Symptoms
- We have an AW maintenance / refresh script or procedure that contains BuildType="BACKGROUND", so that the AW maintenance task will be sent to the Oracle Job queue.
- When we execute the AW maintenance / refresh script or procedure, we do not get any errors in the foreground, the script/procedure has been executed successfully.
- However when we look into the build/refresh log (see <Note 351688.1> for details) we see that the maintenance/refresh task failed with:
13:29:39 Failed to Submit a Job to Build(Refresh) Analytic Workspace <schema>.<AW Name>.
13:29:39 ***Error Occured in BUILD_DRIVER
- In the generated SQL trace for the session of the user who launches the AW build/refresh script or procedure, we see that ORA-27486 insufficient privileges error occurred at creation of the job.
We see from the relevant bit of the SQL trace that err=27486 occured while executing the #20 statement which is 'begin DBMS_SCHEDULER.CREATE_JOB ...', and the statement is parsed and tried to be executed as user having uid=91:
PARSING IN CURSOR #20 len=118 dep=2 uid=91 oct=47 lid=91 tim=1176987702199571
hv=1976722458 ad='76dd8bcc'
begin
DBMS_SCHEDULER.CREATE_JOB(:1, 'plsql_block', :2, 0, null, null, null,
'DEFAULT_JOB_CLASS', true, true, :3); end;
END OF STMT
PARSE
#20:c=1000,e=1100,p=0,cr=0,cu=0,mis=1,r=0,dep=2,og=1,tim=1176987702199561
EXEC #20:c=65990,e=125465,p=10,cr=1090,cu=3,mis=1,r=0,dep=2,og=1,tim=
1176987702325167
ERROR #20:err=27486 tim=465202984
Cause
User who tries to create a job (executes DBMS_SCHEDULER.CREATE_JOB() procedure) does not have the sufficient privileges.
Solution
1. Identify the user under which the job is supposed to be created. This user is not necessarily the same as the user who launched AW build/refresh script or procedure. Get the corresponding username from one of the %_USERS views e.g. from ALL_USERS.
e.g.
SELECT user_id,username FROM all_users WHERE user_id=91;
2. Identify the system privileges currently assigned to the user by connecting as the user whom the privileges need to be determined, and execute:
SELECT * FROM SESSION_PRIVS ORDER BY PRIVILEGE;
3. Ensure that the CREATE JOB privilege is listed.
The CREATE JOB privilege can be granted in various ways to a user:
- via role OLAP_USER or via role OLAP_DBA (see view ROLE_SYS_PRIVS for what privs are assigned to a role):
GRANT OLAP_USER TO <username>;
- explicitly
GRANT CREATE JOB TO <username>;

Error when calling to create_file_watcher on 11.2.03

I am having some problem on using the dbms_scheduler on 11.2.0 on I try it on a new installation of 11.2.03. Now the same code that runs on the other server causes errors on this server.
SQL> grant execute on user_oracle to ot;
Grant succeeded.
SQL> connect ot/ama9zon
Connected.
SQL> begin
dbms_scheduler.create_file_watcher( file_watcher_name => 'W_1',
directory_path => '/home/oracle/ot',
file_name => '*.txt',
credential_name => 'USER_ORACLE',
steady_state_duration => interval '0 00:00:01.00' day to second );
end; 2 3 4 5 6 7
8 /
begin
ERROR at line 1:
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_ISCHED", line 3703
ORA-06512: at "SYS.DBMS_SCHEDULER", line 2633
ORA-06512: at line 2
The user OT has the following privs: connect, resource, create job, create external job, execute dbms_scheduler.
Any advice is greately appreciated.
Vu

Mea culpa.
While repeating the commands on multiple terminal tothe two servers, I accidentall created the credential USER_ORACLE under the SYS schema instead of the testing user's. So the error was really the credential USR_ORACLE was not found.
Sorry for such a mess.
Vu

Scheduling Job

Hi Users,
I have a pl/sql block say "create-table-interface.sql" which will query and insert records into another table.
The requirement is to run the above .sql file every SATURDAY at 8 AM.
In Oracle 10g, there are many DBMS_job functions and I am confused which one to use to meet the requirement as I have never used this before.
Should I use DBMS_JOB.Schedule or DBMS_JOB.submit or should I use JOB_SUBMIT and JOB_RUN.
Can anyone please guide me in this?
Thanks.

Hi,
As PhoenixBai said, if you're on 10g, you'd better use DBMS_SCHEDULER instead of DBMS_JOB.
The Oracle Scheduler can run external program, for example something like "sqlplus <connect_string> @create-table-interface.sql" would be interesting.
But in your case, it's better to wrap your PL/SQL block in a stored procedure and let the scheduler run it :
DBMS_SCHEDULER.create_job(
job_name => 'CREATE_TABLE_INTERFACE',
job_type => 'STORED_PROCEDURE',
job_action => 'YOUR_PROC_NAME',
start_date => sysdate,
repeat_interval => 'FREQ=WEEKLY;BYDAY=SAT;BYHOUR=8',
enabled => true,
auto_drop => false
comments => 'Runs every saturday at 8AM'
);or directly declare the PL/SQL block to execute :
DBMS_SCHEDULER.create_job(
job_name => 'CREATE_TABLE_INTERFACE',
job_type => 'PLSQL_BLOCK',
job_action => 'DECLARE ... BEGIN ... END;',
start_date => sysdate,
repeat_interval => 'FREQ=WEEKLY;BYDAY=SAT;BYHOUR=8',
enabled => true,
auto_drop => false
comments => 'Runs every saturday at 8AM'
);See the link provided above for a complete reference.

Error on 11g 2 during external job execution using credential

Hi,
I need a help from you.
I am getting below error on 11g 2 during external job execution using credentials -
EXTERNAL_LOG_ID="job_805812_412409",
ORA-27369: job of type EXECUTABLE failed with exit code: Arg list too long
STANDARD_ERROR="Launching external job failed: Invalid username or password"
Find credentials creation & other required details -
EXECUTE DBMS_SCHEDULER.create_credential(credential_name =>'SYS.SCRIPTS',username =>'scripts',password => 'u5342222');
BEGIN
DBMS_SCHEDULER.CREATE_JOB(
job_name => 'AUTOLOAD_JOB',
job_type => 'EXECUTABLE',
job_action => '/qpshell/dev/scripts/autoload.sh',
repeat_interval => 'freq=MINUTELY;interval=5;byhour=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22;',
enabled => true,
auto_drop => false,
credential_name => 'SYS.SCRIPTS');
end;
-rw-r--r-- 1 root oinstall 1571 Nov 11 14:42 /u01/app/oracle/product/11.2.0/dbhome_1/rdbms/admin/externaljob.ora
content of externaljob.ora -
run_user = nobody
run_group = nobody
run_user=scripts
run_group=qvcscript
-rwsr-x--- 1 root oinstall 3068424 Nov 11 13:13 extjob
-rwxr-xr-x 1 oracle oinstall 3068424 Nov 11 13:13 extjobo
root@knudwdbs2:/u01/app/oracle/product/11.2.0/dbhome_1/bin> ls -ltr extjob*
-rwx------ 1 oracle oinstall 3068424 Nov 11 12:45 extjoboO
-rwsr-x--- 1 root oinstall 3068424 Nov 11 12:45 extjobO
-rwxr-xr-x 1 oracle oinstall 3068424 Nov 11 13:13 extjobo
-rwsr-x--- 1 root oinstall 3068424 Nov 11 13:13 extjob
Kindly suggest how it can be fixed. Early response much appreciated.
Thanks
Ajay
--

Hi,
When you are logged in to the OS, can you do an "su" to the "scripts" user using this exact password (passwords are case-sensitive) ?
Also make sure that you have libpam.so located somewhere in $LD_LIBRARY_PATH and that it points to a real file.
external jobs with credentials use jssu, but I don't think permissions on jssu are the problem here (it should be setuid to root).
Hope this helps,
Ravi.

To grant privileges to user or/and group

Hi,
I need information about to grant privileges on content area and folders.
For example, if I grant privilege to view content on Content area and I grant privilege of Manage Items on folder. Can the users or group add items to folder? Or can they view the content?
Thank you for information,
Noel

I changed the file (sudo vi $ORACLE_HOME/rdbms/admin/externaljob.ora) to read run_user = oracle and run_group = dba. The error remains the same - also after restart of dbconsole. Anyway, the file has note: The user and group specified here should be a lowly privileged user and group for your platform. For Linux this is nobody and nobody. Which it was, and I changed it back to that.
Btw:
SQL> SELECT owner, credential_name, username FROM dba_scheduler_credentials;
no rows selected
SQL> execute DBMS_SCHEDULER.CREATE_CREDENTIAL('oracle','oracle','password');
After the above I was able to select "sys.oracle" as the credential name pull-down menu of the scheduler job edit mode.
And the job succeeded: EXTERNAL_LOG_ID="job_73826_863", USERNAME="oracle"
How does one set credentials if not in the "preferred credential setup" in dbconsole EM?
Edited by: Dude on Jan 14, 2011 2:11 PM

Error in documentation for DBMS Scheduler - Chapter 93

Sub question: Document display error, URL not found (please include details below)
Comment: I found what appears to be an error in your
online documentation. Following is the path to
the error.
Web address:
http://download.oracle.com/docs/cd/B19306_01/appde
v.102/b14258/d_sched.htm#i1000363
Chapter 93 DBMS_SCHEDULER
Heading Hierarchy:
Using DBMS_SCHEDULER
Operational Notes
Calendaring Syntax
Part Number B14258-02
THIS SYNTAX SEEMS TO HAVE AN ERROR:
bymonth_clause = "BYMONTH" "=" monthlist
monthlist = monthday ( "," monthday)*
month = numeric_month | char_month
numeric_month = 1 | 2 | 3 ... 12
char_month = "JAN" | "FEB" | "MAR" | "APR"
| "MAY" | "JUN" |
"JUL" | "AUG" | "SEP" | "OCT" | "NOV" |
"DEC"
IT SHOULD PROBABLY READ (monthday changed to
month):
bymonth_clause = "BYMONTH" "=" monthlist
monthlist = month ( "," month)*
month = numeric_month | char_monthd
numeric_month = 1 | 2 | 3 ... 12
char_month = "JAN" | "FEB" | "MAR" | "APR"
| "MAY" | "JUN" |
"JUL" | "AUG" | "SEP" | "OCT" | "NOV" |
"DEC"

Hi Salman and ashahide,
thanks for your answers.
I've changed the syntax like this:
execute DBMS_SCHEDULER.CREATE_SCHEDULE(repeat_interval => 'FREQ=DAILY;BYHOUR=10;BYMINUTE=30'', start_date => to_timestamp_tz('2013-03-11 Europe/Berlin', 'YYYY-MM-DD TZR'), schedule_name => 'FULLBACKUP_DAILY');
But now im getting a new error:
ERROR:
ORA-01756: quoted string not properly terminated
Regards,
David
EDIT: I'm sorry for spaming. I'm so blind: 'FREQ=DAILY;BYHOUR=10;BYMINUTE=30'' => there is just one ' to much. Now it works! Thanks a lot for help!
Regards,
David
Edited by: David_Pasternak on 11.03.2013 02:54

Problems with DBMS_JOB - not running jobs

Hello,
for some reason our Database (after night restart - shutdown at 23:00, startup at 0:20) stopped to run jobs from DBMS_JOB. I've enabled them manually (DBMS_JOB.RUN(2334)) - but they still not run after reaching the NEXT_DATE,NEXT_SEC time.
I've noticed that:
select * from dba_scheduler_global_attribute where ATTRIBUTE_NAME='CURRENT_OPEN_WINDOW';
ATTRIBUTE_NAME VALUE
CURRENT_OPEN_WINDOW TUESDAY_WINDOW
Current day of week is wednesday not tuesday - and I think that is the reason.
I've tried this statement:
SQL> execute DBMS_SCHEDULER.CLOSE_WINDOW(WINDOW_NAME => 'TUESDAY_WINDOW');
BEGIN DBMS_SCHEDULER.CLOSE_WINDOW(WINDOW_NAME => 'TUESDAY_WINDOW'); END;
ERROR at line 1:
ORA-00449: background process '' unexpectedly terminated with error
ORA-06512: at "SYS.DBMS_ISCHED", line 347
ORA-06512: at "SYS.DBMS_SCHEDULER", line 968
ORA-06512: at line 1
Is there any other way to fix this problem without restart of database?
Thank you for any help
Best regards

Manually execute the job and let it run itself beginning next Tuesday.

Oracle Scheduler: create different schedule time per day

Hi,
Is it possible to create different schedule times based on the day?
Example I've schedule a backup-job to run every day @ 23h
So i configured my job as :
   execute dbms_scheduler.set_attribute(name=>'DAILY_BACKUP_JOB',attribute=>'repeat_interval',value=>'FREQ=DAILY;BYHOUR=23;BYMINUTE=00');
But now I want to fine tune this and I like to start the job every sunday @ 21h.
is this possible to configure this is the same job? Or do I have to create 2 separate jobs for it? One for MON - SAT @ 23h and another for SUN @ 21h?
Kind regards,

Hi,
You can create 2 schedules and assign them to your job:
BEGIN
-- week days
dbms_scheduler.create_schedule('week_days_sched', repeat_interval => 'FREQ=DAILY;BYDAY=MON,TUE,WED,THU,FRI,SAT;BYHOUR=23');
-- sunday
dbms_scheduler.create_schedule('sunday_sched', repeat_interval => 'FREQ=DAILY;BYDAY=SUN;BYHOUR=21');
END;
Now specify these 2 schedules for your job:
BEGIN
dbms_scheduler.set_attribute( name => 'YOUR_JOB', attribute => 'repeat_interval', value => 'week_days_sched,sunday_sched');
END;

Execute dbms_scheduler

Similar Messages

Maybe you are looking for