DBMS_JOB.SUBMIT 建立job定時排程
SUBMIT Procedure
This procedure submits a new job. It chooses the job from the sequence sys.jobseq.
Syntax
DBMS_JOB.SUBMIT ( job OUT BINARY_INTEGER, what IN VARCHAR2, next_date IN DATE DEFAULT sysdate, interval IN VARCHAR2 DEFAULT 'null', no_parse IN BOOLEAN DEFAULT FALSE, instance IN BINARY_INTEGER DEFAULT any_instance, force IN BOOLEAN DEFAULT FALSE);
Parameters
Table 78-9 SUBMIT Procedure Parameters
Parameter | Description |
---|---|
job |
Number of the job being run. |
what |
PL/SQL procedure to run. |
next_date |
Next date when the job will be run. |
interval |
Date function that calculates the next time to run the job. The default is NULL. This must evaluate to a either a future point in time or NULL. |
no_parse |
A flag. The default is FALSE. If this is set to FALSE, then Oracle parses the procedure associated with the job. If this is set to TRUE, then Oracle parses the procedure associated with the job the first time that the job is run. For example, if you want to submit a job before you have created the tables associated with the job, then set this to TRUE. |
instance |
When a job is submitted, specifies which instance can run the job. |
force |
If this is TRUE, then any positive integer is acceptable as the job instance. If this is FALSE (the default), then the specified instance must be running; otherwise the routine raises an exception. |
Usage Notes
-
You must issue a COMMIT statement immediately after the statement.
-
The parameters instance and force are added for job queue affinity. Job queue affinity gives users the ability to indicate whether a particular instance or any instance can run a submitted job.
Example
This submits a new job to the job queue. The job calls the procedure DBMS_DDL.ANALYZE_OBJECT to generate optimizer statistics for the table DQUON.ACCOUNTS. The statistics are based on a sample of half the rows of the ACCOUNTS table. The job is run every 24 hours:
VARIABLE jobno number; BEGIN DBMS_JOB.SUBMIT(:jobno, 'dbms_ddl.analyze_object(''TABLE'', ''DQUON'', ''ACCOUNTS'', ''ESTIMATE'', NULL, 50);' SYSDATE, 'SYSDATE + 1'); COMMIT; END; / Statement processed. print jobno JOBNO ---------- 14144
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29477587/viewspace-1154618/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Oracle:建立JOB定時執行儲存過程Oracle儲存過程
- Oracle透過job定時建立表Oracle
- job 執行時間比排程間隔時間長
- Spring使用Quartz定時排程Job無法Autowired注入Service的解決方案Springquartz
- Linux 定時任務排程Linux
- Java定時任務排程詳解Java
- Crontab定時任務排程介紹
- Android 中的定時任務排程Android
- Spring排程定時任務的方式Spring
- 使用Java實現定時任務排程Java
- 定時排程系列之Quartz.Net詳解quartz
- 利用排程任務定時刪除分割槽
- 用海豚排程器定時排程從Kafka到HDFS的kettle任務指令碼Kafka指令碼
- 3 分鐘建立 Serverless Job 定時獲取新聞熱搜!Server
- 3 分鐘建立 Serverless Job 定時獲取新聞熱搜Server
- micro-job分散式任務排程框架更新分散式框架
- 基於Azkaban的任務定時排程實踐
- laravel框架任務排程(定時執行任務)Laravel框架
- NET作業排程(定時任務)-Quartz.Netquartz
- dbms_job 定時計劃
- 分散式任務排程平臺XXL-JOB分散式
- Elastic-job實戰(分散式作業排程框架)AST分散式框架
- 深入 Java Timer 定時排程器實現原理Java
- Oracle資料庫定時器JobOracle資料庫定時器
- 詳解 MySQL 用事件排程器 Event Scheduler 建立定時任務MySql事件
- 詳解MySQL用事件排程器Event Scheduler建立定時任務MySql事件
- plsql建立jobSQL
- oracle建立job並執行jobOracle
- Oracle無法自動排程DBMS_JOB&DBMS_SCHEDULER案例分析Oracle
- 軟中斷排程時機
- oracle建立定時任務之dbms_jobOracle
- Oracle使用DBMS_JOB建立的資料庫作業,遇到資料庫關閉狀態的排程Oracle資料庫
- 使用JOB定時備份資料庫資料庫
- 採用job定時執行recover datafile
- Flink排程之排程器、排程策略、排程模式模式
- [原始碼分析] 定時任務排程框架 Quartz 之 故障切換原始碼框架quartz
- 深入 Java Timer 定時任務排程器實現原理Java
- 在Spring中使用JDK定時器實現排程任務SpringJDK定時器