The CHANGE stored procedure modifies the fields set in a job.
Applicability
This topic applies only to OceanBase Database Enterprise Edition. OceanBase Database Community Edition provides only the MySQL mode.
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. You can query this ID from the JOB column of the USER_JOBS or DBA_JOBS view. |
| what | The PL stored procedure to run. |
| next_date | The next date for running the job. |
| interval | The interval at which the job runs. |
| zone | The zone where the job runs, which can be specified when you submit the job. Default value: NULL, indicating that the zone association is not modified. |
| force | If you set this parameter to TRUE, a validity check is performed for the specified zone. Otherwise, validity check is not performed for the zone. |
Considerations
Before a job is submitted, it cannot be handled by the job queue in the background.
The
zoneandforceparameters are added to the job queue so that you can specify whether the specified zone can run the submitted job.If the value
NULLis specified for thewhat,next_date, orintervalparameter, the NULL value is retained.
Examples
BEGIN
DBMS_JOB.CHANGE(10100, null, null, 'next_day(sysdate,''TUESDAY'')');
COMMIT;
END;
