The OCID of the compartment.
Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The name of the current infrastruture component that is getting patched.
Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Description of the maintenance run.
The user-friendly name for the maintenance run.
The estimated start time of the next infrastruture component patching operation.
The OCID of the maintenance run.
If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
Additional information about the current lifecycle state.
The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
Maintenance sub-type.
Maintenance type.
Contain the patch failure count. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier {@code ru_patch_19.9.0.0_201030} is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
The time when the patching operation ended.
Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT*: Non-rolling infrastructure patching involves system down time. See [Oracle-Managed Infrastructure Maintenance Updates](https://docs.cloud.oracle.com/iaas/Content/Database/Concepts/examaintenance.htm#Oracle) for more information.
The time when the patching operation started.
The status of the patching operation.
The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
The target software version for the database server patching operation.
The ID of the target resource on which the maintenance run occurs.
The type of the target resource on which the maintenance run occurs.
The target Cell version that is to be patched to.
The date and time the maintenance run was completed.
The date and time the maintenance run is scheduled to occur.
The date and time the maintenance run starts.
Details of a maintenance run.