Attribute | Recommended content |
---|---|
program_name | Name of the Program. This name should not include any embedded characters or '-' character according to Oracle object naming conventions. |
comments | A short description of the program. This is useful for searching the program. |
enabled | Set to true to enable this program to be used by the scheduler. |
program_type | Specify the PL/SQL Block as the type of program for the Oracle Scheduler Interface. |
program_action | Specify the interface commands line for the execution. You may include any overrides, if desired, at this time. For optimization purpose, only specify the parameters that are not inherited from the global options or are not defaulted on the batch control. It is recommended to specify the Batch Control to avoid issues in submission. An example of a simple command line is: begin OUAF_BATCH.Submit_Job(batch_code => 'BATCH01'); end; |
Interface | Method of Definition |
---|---|
PL/SQL | Use the DBMS_SCHEDULER.CREATE_PROGRAM procedure using the above parameters to define the program object. |
SQL Developer | Use the New Program menu item of the Scheduler tree to define the new program using a right click action on the Program node. |
Enterprise Manager | Using the Administration, Oracle Scheduler, Programs menu item, specify the program information as above. Use the Source field to hold the PL/SQL command line for the interface. |
Attribute | Recommended content |
---|---|
job_class_name | Name of the Job Class. This name should not include any embedded characters or '-' character according to Oracle object naming conventions. |
comments | A short description of the job class. This is useful for searching for the job class. |
resource_consumer_name | Name of the resource consumer group associated with jobs in this job class. Optional. |
service | Name of database service associated with this job class name. Optional. |
logging_level | Sets the level of logging is performed by the Oracle Scheduler. Optional. |
log_history | Sets the retention period, in days, log history is retained by the Oracle Scheduler. Optional. |
Interface | Method of Definition |
---|---|
PL/SQL | Use the DBMS_SCHEDULER.CREATE_JOB_CLASS procedure using the above parameters to define the job class object. |
SQL Developer | Use the New Job Class menu item of the Scheduler tree to define the new job class using a right click action on the Scheduler node. |
Enterprise Manager | Using the Administration, Oracle Scheduler, Job Class menu item, specify the class information as above. |
Attribute | Recommended Content |
---|---|
schedule_name | Name of the schedule. This name should not include any embedded characters or '-' character according to Oracle object naming conventions. |
comments | A short description of the schedule. This is useful for searching the schedule. |
start_date | Optional start date and time when the schedule becomes valid. If not populated, then the date jobs or windows are activated is used. |
repeat_interval | This specifies how often the schedule repeats. It uses the Calendaring Syntax supported by the Oracle Scheduler. Even schedules decide the repeat interval for checking the event. |
end_date | Optional date and time after jobs and windows allocated to this schedule will not execute. |
Interface | Method of Definition |
---|---|
PL/SQL | Use the DBMS_SCHEDULER.CREATE_SCHEDULE procedure using the above parameters to define the schedule object. This interface is recommended for complex Calendaring Syntax support. |
SQL Developer | Use the New Credential menu item of the Scheduler tree to define the new schedule using a right click action on the Schedule node. |
Enterprise Manager | Using the Administration, Oracle Scheduler, Schedules menu item, specify the schedule information as above. |
Attribute | Recommended Content |
---|---|
credential_name | Name of the credential. This name should not include any embedded characters or '-' character according to Oracle object naming conventions. |
comments | This attribute is not used by the DBMS_SCHEDULER package but can be provided for documentation purposes. |
username | The userid to be used for connection. This attribute is required and is case sensitive. |
password | The password associated with the username. This value is stored in obfuscated format and is not available in Oracle Scheduler views. |
database_role | This is the database role associated with this user. This is not used for product jobs but is required for any DBA tasks requiring privilege access. |
windows_domain | For Windows Server implementations only. This is the windows domain for the user to connect to. |
Interface | Method of Definition |
---|---|
PL/SQL | Use the DBMS_CREDENTIAL.CREATE_CREDENTIAL procedure using the above parameters to define the credential object. |
SQL Developer | Use the New Credential menu item of the Scheduler tree to define the new credential using a right click action on the Credentials node. Oracle SQL Developer uses DBMS_CREDENTIAL for credential management. |
Enterprise Manager | Oracle Enterprise Manager uses its own security system for credentials. Refer to the Enterprise Manager Cloud Control Security Guide for more details. |
Attribute | Recommended Content |
---|---|
destination_name | Name of the destination. This name should not include any embedded characters or '-' character according to Oracle object naming conventions. |
comments | This attribute is not used by the DBMS_SCHEDULER package but can be provided for documentation purposes. |
agent | The agent name as specified in the agent configuration file. |
tns_name | Oracle service name as documented in the TNS file attached to the configuration file. This is used to connect from the scheduler database to the remote database. |
Interface | Method of Definition |
---|---|
PL/SQL | Use the DBMS_CREDENTIAL.CREATE_DATABASE_DESTINATION procedure using the above parameters to define the credential object. |
SQL Developer | Use the New Database Destination menu item of the Scheduler tree to define the new destination using a right click action on the Database Destinations node. |
Enterprise Manager | Oracle Enterprise Manager uses its own security system for destinations. Refer to the Enterprise Manager Cloud Control Security Guide for more details. |
Attribute | Recommended content |
---|---|
job_name | Name of the job. This name should not include any embedded characters or '-' character according to Oracle object naming conventions. It is recommended to replace '-' in Batch Controls with '_' to avoid naming issues. |
comments | Description of Job. Useful for finding jobs. |
job_type | If programs have been used, then the type STORED_PROCEDURE should be used. If programs are not used, then specify PLSQL_BLOCK with the action containing the source PL/SQL command. |
job_action | Value depends on the specification of the job_type: • If job_type is STORED_PROCEDURE, then this will contain the fully qualified name of the program to execute. • If job_type is PLSQL_BLOCK, then this will contain the PL/SQL command to execute the OUAF_BATCH interface. |
start_date | Optional start date and time when the schedule becomes valid. If not populated, then the date jobs or windows are activated is used. If schedule_name is specified, then this date and time may be null to inherit the value from the schedule or chain. |
repeat_interval | Optional. Definition of how often the job will repeat. It uses the Calendaring Syntax supported by the Oracle Scheduler. Even schedules decide the repeat interval for checking the event. If schedule_name is specified, then this value may be null to inherit the value from the schedule or chain. |
schedule_name | Optional. Name of schedule object dictating the schedule for this job. |
job_class | Optional. Name of job class allocated to this job. |
end_date | Optional date and time after jobs and windows allocated to this job will not execute. If schedule_name is specified, then this date and time may be null to inherit the value from the schedule or chain. |
credential_name | Optional. Name of credential to use for remote invocation for this job. |
destination_name | Optional. Name of destination to use for remote invocation for this job. For remote product jobs this must be the location of the product database. |
enabled | Whether this job is enabled or not. Only enabled jobs (true) are executed. |
auto_drop | Whether after execution of this job, the job definition will be dropped. This is typically set to true for temporary jobs only. It is recommended to set to false for all regular product jobs. |
Interface | Method of Definition |
---|---|
PL/SQL | Use the DBMS_SCHEDULER.CREATE_JOB procedure using the above parameters to define the job object. |
SQL Developer | Use the New Job menu item of the Scheduler tree to define the new job using a right click action on the Jobs node. |
Enterprise Manager | Using the Administration, Oracle Scheduler, Jobs menu item, specify the job information as above. |
Interface | Method of Definition |
---|---|
PL/SQL | Refer to Creating and Managing Job Chains for the sequence of statements to execute. |
SQL Developer | Use the New Chain menu item of the Scheduler tree to define the new chain using a right click action on the Chains node. |
Enterprise Manager | Using the Administration, Oracle Scheduler, Chains menu item, specify the chain information. |