The OCID of the compartment.
List of one-off patches for Database Homes.
List of one-off patches for Database Homes.
The database version with which the database software image is to be built.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
The user-friendly name for the database software image. The name does not have to be unique.
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 database software image.
To what shape the image is meant for.
The type of software image. Can be grid or database.
The patches included in the image and the version of the image.
True if this Database software image is supported for Upgrade.
Detailed message for the lifecycle state.
The current state of the database software image.
The output from the OPatch lsInventory command, which is passed as a string.
The PSU or PBP or Release Updates. To get a list of supported versions, use the {@link #listDbVersions(ListDbVersionsRequest) listDbVersions} operation.
The date and time the database software image was created.
The Database service supports the creation of database software images for use in creating and patching DB systems and databases.
To use any of the API operations, you must be authorized in an IAM policy. If you are not authorized, talk to an administrator. If you are an administrator who needs to write policies to give users access, see [Getting Started with Policies](https://docs.cloud.oracle.com/Content/Identity/Concepts/policygetstarted.htm).
For information about access control and compartments, see [Overview of the Identity Service](https://docs.cloud.oracle.com/Content/Identity/Concepts/overview.htm).
*Warning:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.