The OCID of the compartment in which the job resides.
The subtype of the Oracle Database where the job has to be executed. Applicable only when managedDatabaseGroupId is provided.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}
The description of the job.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {@code {"Department": "Finance"}}
The OCID of the job.
The lifecycle state of the job.
The OCID of the Managed Database Group where the job has to be executed.
The OCID of the Managed Database where the job has to be executed.
The details of the Managed Databases where the job has to be executed.
The display name of the job.
The OCID of the Named Credentials containing password secret.
The SQL operation type.
The role of the database user. Indicates whether the database user is a normal user or sysdba.
The schedule type of the job.
The SQL text to be executed in the job. This is a mandatory field for the EXECUTE_SQL operationType.
The type of SQL. This is a mandatory field for the EXECUTE_SQL operationType.
The error message that is returned if the job submission fails. Null is returned in all other scenarios.
System tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. System tags can be viewed by users, but can only be created by the system.
Example: {@code {\"orcl-cloud\": {\"free-tier-retained\": \"true\"}}}
The date and time when the job was created.
The date and time when the job was last updated.
The job timeout duration, which is expressed like "1h 10m 15s".
The database user name used to execute the SQL job. If the job is being executed on a Managed Database Group, then the user name should exist on all the databases in the group with the same password.
The details of the SQL job.