How to execute stored procedures in Oracle regularly
In enterprise-level applications, we cannot just rely on users to manually perform operations to achieve the required functionality. Therefore, scheduled tasks are essential, which are especially useful for performing background processing and data loading. Oracle database provides stored procedures and scheduled tasks to simplify the work of developers and administrators. In this article, we will focus on the method of using Oracle scheduled tasks to execute stored procedures regularly.
Oracle scheduled tasks
Scheduled tasks in the Oracle database can be created using the DBMS_SCHEDULER package. This package allows us to create jobs with complex scheduling requirements. It can support various frequencies such as hourly, daily, weekly, monthly, yearly, etc. Scheduled tasks can also be executed on a specific date and time, or even in different time zones. The following types of objects can be created using the DBMS_SCHEDULER package.
- Job (job): A task unit created when executing the DBMS_SCHEDULER.CREATE_JOB function, scheduled by the scheduler regularly or on request.
- Job class: A group of related tasks that share the same resource consumption limit rule.
- Resource consumption limit: Resource consumption rules used to control jobs and job classes.
- Chain: A sequence of jobs in which the completion of one job triggers the execution of another job.
- Session: The process associated with a job execution. Sessions can be logged and monitored to understand job execution.
In this article, we will focus on how to use DBMS_SCHEDULER to create a job and bind it to the stored procedure we want to execute.
Create a stored procedure
We first need to create a stored procedure to perform the task operation we want to complete. Below is a simple example of a stored procedure that will insert the current time into a table.
CREATE OR REPLACE PROCEDURE INSERT_TIME AS BEGIN INSERT INTO TIME_LOG (LOG_TIME) VALUES (SYSDATE); COMMIT; END INSERT_TIME;
Create job
With the stored procedure, we next need to create a job to schedule its execution. The job we are going to create will insert the current time every morning at 6 o'clock. Below is an example of using the DBMS_SCHEDULER.CREATE_JOB function to create this job.
BEGIN DBMS_SCHEDULER.CREATE_JOB ( job_name => 'INSERT_TIME_JOB', job_type => 'STORED_PROCEDURE', job_action => 'INSERT_TIME', start_date => SYSTIMESTAMP, repeat_interval => 'FREQ=DAILY; BYHOUR=6;', enabled => TRUE, comments => 'Insert current time every day at 6 AM'); END;
When using the CREATE_JOB function to create a job, we need to follow the following parameter description:
- job_name: The name of the job, which must be unique.
- job_type: The type of job, usually "STORED_PROCEDURE".
- job_action: The name of the stored procedure, package or executable file to be executed by the job.
- start_date: The start time of the job, which can be a date or a timestamp. If not specified, it defaults to the current time.
- repeat_interval: Specify the execution frequency and time interval of the job. In this example, "FREQ=DAILY; BYHOUR=6;" means that it is executed every day at 6 o'clock in the morning. Other options include hourly, weekly, monthly, yearly, etc. We can also use this parameter to specify the days on which the job should be executed, such as every Monday, Tuesday, and Thursday.
- enabled: Indicates whether the job is enabled.
- comments: A short description of the assignment.
Bind job to stored procedure
In the above example, we created a job and specified the stored procedure for its execution. Now, we need to bind this job to our stored procedure so that it executes the operation at the specified time. We can use the DBMS_SCHEDULER.SET_ATTRIBUTE function to accomplish this task.
BEGIN DBMS_SCHEDULER.SET_ATTRIBUTE ( name => 'INSERT_TIME_JOB', attribute => 'program_action', value => 'INSERT_TIME;'); END;
In this example, we use the SET_ATTRIBUTE function to set the "program_action" attribute of the job "INSERT_TIME_JOB" to "INSERT_TIME". This will tell DBMS_SCHEDULER to call the INSERT_TIME stored procedure at a specific time.
We have learned how to use the DBMS_SCHEDULER package to create scheduled jobs and bind tasks in stored procedures. Now, we can wait for the scheduled task to execute and view the records in the TIME_LOG table.
Conclusion
Using the scheduled task function of the Oracle database can help us easily perform background processing tasks. The DBMS_SCHEDULER package provides many options to meet our specific application needs, such as repeated execution, parallel execution, failure recovery, etc. Additionally, it has the ability to execute jobs across different time zones, dates, weeks, months, etc., which makes scheduled tasks very flexible. In this article, we focus on how to use Oracle's scheduled tasks to execute stored procedures regularly. We hope this article can provide you with useful guidance and help you better understand the use and operation principles of scheduled tasks based on Oracle database.
The above is the detailed content of How to execute stored procedures in Oracle regularly. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The article explains how to create users and roles in Oracle using SQL commands, and discusses best practices for managing user permissions, including using roles, following the principle of least privilege, and regular audits.

The article discusses methods for performing online backups in Oracle with minimal downtime using RMAN, best practices for reducing downtime, ensuring data consistency, and monitoring backup progress.

The article outlines steps to configure Transparent Data Encryption (TDE) in Oracle, detailing wallet creation, enabling TDE, and data encryption at various levels. It also discusses TDE's benefits like data protection and compliance, and how to veri

The article explains how to use Oracle's AWR and ADDM for database performance optimization. It details generating and analyzing AWR reports, and using ADDM to identify and resolve performance bottlenecks.

Article discusses using Oracle's flashback technology to recover from logical data corruption, detailing steps for implementation and ensuring data integrity post-recovery.

The procedures, functions and packages in OraclePL/SQL are used to perform operations, return values and organize code, respectively. 1. The process is used to perform operations such as outputting greetings. 2. The function is used to calculate and return a value, such as calculating the sum of two numbers. 3. Packages are used to organize relevant elements and improve the modularity and maintainability of the code, such as packages that manage inventory.

The article discusses creating and managing Oracle database objects like tables, views, and indexes using SQL commands. It covers best practices for performance optimization, ensuring data integrity and security, and using tools for automation.

The article details procedures for switchover and failover in Oracle Data Guard, emphasizing their differences, planning, and testing to minimize data loss and ensure smooth operations.
