Home > SQL Developer Dialog Boxes ... > Create/Edit Job
This interface is used for creating a new Oracle Scheduler job or editing an existing job. For more information about job scheduling, see Scheduling Jobs Using SQL Developer.
(To create a job, SQL Developer internally uses the DBMS_SCHEDULER.CREATE_JOB procedure, which is documented in Oracle Database PL/SQL Packages and Types Reference.)
Job Details
Job Name: Name of the job.
Enabled: If this option is specified, validity checks will be made and the job will be created enabled if all the checks are successful. If this option is not specified, the job is not created enabled.
Description: Optional text string that can be used to describe the job.
Job Class: Name of the job class to which this job belongs.
Type of Job: Type of object to be executed by the job: PL/SQL Block, Chain, Stored Procedure, Named Program, or Executable.
When to Execute Job: When to execute the job: Immediate (immediately on creation, and once only), Once (once, at a specified time), Repeating, Queue, File Watcher, Schedule (using a named schedule object). If you specify anything other than Immediate, you are prompted for additional information.
Destination
Local (local system), Remote (the database destination for a remote database job, or external destination for a remote external job), or Multiple (the job runs on all destinations).
Depending on what destination you selected for the job, select the local credential, the remote credential and destination, or the multiple group.
Job Arguments
If the job expects arguments to be passed, the Name and Data Type of each argument are listed. For each input or input/output argument, specify the appropriate Value.
Notification
Select Job Events for which to send notification email messages. For each message, you can specify recipient email addresses and the sender (or no sender), and you can modify the body of the message.
Properties
Auto Drop: Determines whether the job is to be automatically dropped after it has completed or has been automatically disabled.
Restartable: Determines whether the job can be restarted in case of failure.
Stop on Window Close: If the schedule of a job is a window or a window group, TRUE causes the job to stop once the associated window is closed, and fALSE causes the job to continue after the window closes. (Note that if the job is allowed to continue, its resource allocation will probably change because closing a window generally also implies a change in resource plans.)
Follow Default Time Zone: Determines whether if the job start date is null, then when the default time zone scheduler attribute is changed, the Scheduler recomputes the next run date and time for this job so that it is in accordance with the new time zone.
Parallel Instances: For an event-based job, determined what happens if an event is raised and the event-based job that processes that event is already running. FALSE
causes the new event to be ignored. TRUE
causes an instance of the job to be started for every instance of the event, and each job instance is a lightweight job so multiple instances of the same event-based job can run in parallel.
Job Style: Style of the job being created: REGULAR
(regular job) or LIGHTWEIGHT
(lightweight job). A lightweight must reference a program object. Use lightweight jobs when you have many short-duration jobs that run frequently. Under certain circumstances, using lightweight jobs can deliver a small performance gain.
Job Priority: The priority of this job relative to other jobs in the same class as this job. If multiple jobs within a class are scheduled to be executed at the same time, the job priority determines the order in which jobs from that class are picked up for execution by the job coordinator. It can be a value from 1 through 5, with 1 being the first to be picked up for job execution.
Job Weight: (Do not change the value. Shown only for connections to Oracle Database releases before 11.2.)
Logging Level: Determines how much information is logged: DBMS_SCHEDULER.LOGGING_OFF (no logging), DBMS_SCHEDULER.LOGGING_FAILED_RUNS (only jobs that failed, with the reason for failure), DBMS_SCHEDULER.LOGGING_RUNS (all runs of each job in this class), or DBMS_SCHEDULER.LOGGING_FULL (all operations performed on all jobs).
However, if the job class has a higher (more detailed) logging level than the level specified for the job, the job class logging level is used.
Max Runs: The maximum number of consecutive scheduled runs of the job.
Max Failures: The number of times a job can fail on consecutive scheduled runs before it is automatically disabled.
Instance ID: In an Oracle Real Application Clusters environment., the instance ID of the instance that the job must run on.
Raise Events: Determines at what stages of the job execution to raise events. (See the DBMS_SCHEDULER.SET_ATTRIBUTE documentation in Oracle Database PL/SQL Packages and Types Reference for details.)
Max Run Duration: Maximum amount of time that the job should be allowed to run. Its data type is INTERVAL DAY TO SECOND. If this attribute is set to a nonzero and non-null value, and job duration exceeds this value, the Scheduler raises an event of type JOB_OVER_MAX_DUR. It is then up to your event handler to decide whether or not to allow the job to continue.
Schedule Limit: Maximum delay time between scheduled and actual job start before a program run is canceled.
Store Output: If set to TRUE
, then for job runs that are logged, all job output and error messages are stored in the *_JOB_RUN_DETAILS views. If set to FALSE
, then the output and messages are not stored.
Reset to Defaults: Resets all properties to their default values.
Summary/SQL
May include a summary in hierarchical form or the PL/SQL statement that will be used to implement your specifications, or both.
Related Topics