The CHANGE stored procedure is used to modify the fields set by the user in the Job.
Applicability
This topic applies only to OceanBase Database Enterprise Edition. OceanBase Database Community Edition does not support this feature.
Syntax
DBMS_JOB.CHANGE (
job IN BINARY_INTEGER,
what IN VARCHAR2,
next_date IN DATE,
interval IN VARCHAR2,
zone IN VARCHAR2 DEFAULT NULL,
force IN BOOLEAN DEFAULT FALSE);
Parameters
| Parameter | Description |
|---|---|
| job | The unique ID of the job to be modified. To find this ID, query the JOB column of the USER_JOBS or DBA_JOBS view. |
| what | The PL stored procedure to be executed. |
| next_date | The next date on which the job will run. |
| interval | The time interval for the job. |
| zone | Specifies which zone can run the job when submitting it. The default value is NULL, indicating that the zone association remains unchanged. |
| force | If TRUE, a validity check is performed on the specified zone. Otherwise, no validity check is performed. |
Considerations
Before submission, the job will not be processed by the background job queue.
The job queue has been added with the associated parameters
zoneandforce, allowing users to specify whether the submitted job can run in the specified zone.If the parameters
what,next_date, orintervalareNULL, their values will remain unchanged.
Examples
BEGIN
DBMS_JOB.CHANGE(10100, null, null, 'next_day(sysdate,''TUESDAY'')');
COMMIT;
END;