The database software image OCID
The OCID of the DB system.
A valid Oracle Database version. For a list of supported versions, use the ListDbVersions operation.
This cannot be updated in parallel with any of the following: licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel, adminPassword, whitelistedIps, isMTLSConnectionRequired, openMode, permissionLevel, dbWorkload, privateEndpointLabel, nsgIds, isRefreshable, dbName, scheduledOperations, dbToolsDetails, isLocalDataGuardEnabled, or isFreeTier.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
The user-provided name of the Database Home.
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\"}}
If true, the customer acknowledges that the specified Oracle Database software is an older release that is not currently supported by OCI.
Indicates whether unified autiding is enabled or not. Set to True to enable unified auditing on respective DBHome.
The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
The OCID of the key container version that is used in database transparent data encryption (TDE) operations KMS Key can have multiple key versions. If none is specified, the current key version (latest) of the Key Id is used for the operation. Autonomous Database Serverless does not use key versions, hence is not applicable for Autonomous Database Serverless instances.
Note that a valid {@code dbSystemId} value must be supplied for the {@code CreateDbHomeWithDbSystemId} API operation to successfully complete.