Type of Collection this Exadata Fleet Update Cycle belongs to.
Compartment Identifier.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Exadata Fleet Update Cycle display name.
OCID identifier for the Action that is currently in execution, if applicable.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
OCID identifier for the Collection ID the Exadata Fleet Update Cycle is assigned to.
OCID identifier for the Exadata Fleet Update Cycle.
List of bug numbers to ignore.
Ignore all patches between the source and target homes during patching.
Ensure that services of administrator-managed Oracle RAC or Oracle RAC One databases are running on the same instances before and after the move operation.
The latest Action type that was completed in the Exadata Fleet Update Cycle. No value would indicate that the Cycle has not completed any Action yet.
A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state.
The current state of the Exadata Fleet Update Cycle.
Service drain timeout specified in seconds. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
In this array all the possible actions will be listed. The first element is the suggested Action.
Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
The date and time the Exadata Fleet Update Cycle was created, as described in RFC 3339, section 14.29.
The date and time the Exadata Fleet Update Cycle was finished, as described in RFC 3339.
The date and time the Exadata Fleet Update Cycle was updated, as described in RFC 3339, section 14.29.
Patch Exadata Fleet Update Cycle resource details.