Home > SQL Developer Dialog Boxes ... > Create/Edit Program
This dialog box is used for creating or editing an Oracle Scheduler program, which can include creating a new program using details from an existing program (Create Like). For more information about job scheduling, see Scheduling Jobs Using SQL Developer.
(To create a program, SQL Developer internally uses the DBMS_SCHEDULER.CREATE_PROGRAM procedure.)
Name: Name of the program. The name has to be unique in the SQL namespace. For example, a program cannot have the same name as a table in a schema.
Enabled: If this option is specified, validity checks will be made and the program will be created enabled if all the checks are successful. If this option is not specified, the program is not created enabled.
Description: Optional text string that can be used to describe the program.
Type of program:
PL/SQL Block: The program is a PL/SQL block. Job or program arguments are not supported when the job or program type is PLSQL_BLOCK. In this case, the number of arguments must be 0. Enter or paste in the complete PL/SQL code, or edit the existing code.
Stored Procedure: The program is a PL/SQL or Java stored procedure, or an external C subprogram. Only procedures, not functions with return values, are supported. PL/SQL procedures with INOUT or OUT arguments are not supported.
Schema: Schema of the stored procedure. I not specified, the schema of the job is assumed.
Procedure: Name of the stored procedure.
Arguments: For each argument: name, data type, default value, and whether it is an input, output, or input/output argument.
Remote Stored Procedure: The program is a remote stored procedure. You specify the procedure name and any arguments.
Procedure: Name of the stored procedure.
Arguments: For each argument: name, data type, default value, and whether it is an input, output, or input/output argument.
Executable: The program is external to the database. External programs implies anything that can be executed from the operating system's command line. AnyData arguments are not supported.
Executable: Name of the external executable, including the full path name, but excluding any command-line arguments. If the action starts with a single question mark ('?'), the question mark is replaced by the path to the Oracle home directory for a local job or to the Scheduler agent home for a remote job. If the action contains an at-sign ('@') and the job is local, the at-sign is replaced with the SID of the current Oracle instance.
Arguments: For each argument: name, data type, default value, and whether it is an input, output, or input/output argument
Script: The program is a SQL Script (SQL*Plus statements), Backup Script (RMAN commands), or External Script (operating system commands). Enter or paste the script text in the box.
Properties tab
Enables you to set program properties. For most properties the default is null, but you can check the box to specify a value.
Detached: TRUE if the program is a detached job; otherwise, FALSE. Use a detached job to start a script or application that runs in a separate process, independently and asynchronously to the Scheduler. A detached job typically starts another process and then exits. Upon exit (when the job action is completed) a detached job remains in the running state. The running state indicates that the asynchronous process that the job started is still active. When the asynchronous process finishes its work, it must connect to the database and call DBMS_SCHEDULER.END_DETACHED_JOB_RUN, which ends the job.
Max Runs: Maximum number of runs before the program is marked as completed.
Max Failures: Maximum number of failures tolerated before the program is marked as broken.
Max Run Duration: Maximum run duration of the program.
Schedule Limit: Maximum delay time between scheduled and actual job start before a program run is canceled.
Related Topics