Scheduling Jobs with DBMS_SCHEDULER 

Glad it was helpful!

@@dbagenesis I tested the program and It worked. I have a nice scheduling running everyday. Thank you!!

@@chiaracustodi8710 Hi, Can u pls tell me where u mention the procedure name.

You are welcome

You are welcome!

You are most welcome

Noted

Glad it was helpful!

Noted! Added your requested topic to our list.

Glad you liked it

Glad to hear that

Most welcome!

By querying DBA_SCHEDULER_JOB_LOG

yes, you can use it.

Thank you!

Check this link: support.dbagenesis.com/knowledge-base/automate-rman-backups-using-shell-scripts/

I think for that you have to use log script where you will get the error msg

From other forums: Although dbms_job still exists in 10g and 11g, Oracle recommends the use of dbms_scheduler in releases 10g and up. No new features are being added to dbms_job and you will likely quickly run into its limitations. dbms_scheduler is more robust and fully-featured than dbms_job and includes the following features that dbms_job does not have : logging of job runs (job history) simple but powerful scheduling syntax (similar to but more powerful than cron syntax) running of jobs outside of the database on the operating system resource management between different classes of jobs use of job arguments including passing of objects into stored procedures privilege-based security model for jobs naming of jobs and comments in jobs stored, reusable schedules Features in releases after 10g Release 1 include : dependencies between job units (10gR2 and up) scheduling based on financial calendars and fiscal quarters (10gR2 and up) event based jobs which run when an event is received (10gR2 and up) running of jobs on remote machines (11gR1 and up) e-mail notifications on job events of interest (10gR2 and up) starting a job based on arrival of a file (10gR2 and up)

An email notification is associated with a job using the ADD_JOB_EMAIL_NOTIFICATION procedure. The events parameter determines which job events fire a notification, while the filer_condition parameter can reduce the notifications by filtering out those events that do not meet specific criteria, based on the SCHEDULER$_EVENT_INFO Object Type. SQL> exec dbms_scheduler.set_scheduler_attribute('email_server','192.168.1.100'); The smtp_out_server parameter should also be set as follows. SQL> alter system set smtp_out_server='192.168.1.10' scope=both sid='*'; After this process we can add notifications with DBMS_SCHEDULER.ADD_JOB_EMAIL_NOTIFICATION procedure BEGIN DBMS_SCHEDULER.ADD_JOB_EMAIL_NOTIFICATION ( job_name => 'JOB_NAME', recipients => 'jobnotification@test.com, x@test.com', sender => 'do_not_reply@test.com', subject => 'Job Notification-%job_owner%.%job_name%-%event_type%', body => '%event_type% occured on %event_timestamp%. %error_message%', events => 'JOB_FAILED, JOB_BROKEN, JOB_DISABLED, JOB_SCH_LIM_REACHED'); END; /

Every Job is evergreen if you are willing to learn new features as they come

Kindly post it on www.forum.dbagenesis.com/