The OCID of the compartment.
A message describing the status of the database connection of this resource. For example, it can be used to provide actionable information about the permission and content validity of the database connection.
The user-friendly name for the database. The name does not have to be unique.
The hostnames for the database.
The OCID of the database.
The database name. The database name is unique within the tenancy.
OCI database resource type
Operations Insights internal representation of the database type.
The version of the database.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
The OCID of the database insight resource.
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 database.
The OCID of the OPSI private endpoint
The OCID of the VM Cluster or DB System ID, depending on which configuration the resource belongs to.
Processor count. This is the OCPU count for Autonomous Database and CPU core count for other database types. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The OCID of the root resource for a composite target. e.g. for ExaCS members the rootId will be the OCID of the Exadata Infrastructure resource.
Indicates the status of a database insight in Operations Insights
System tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
The time the the database insight was first enabled. An RFC3339 formatted datetime string
The time the database insight was updated. An RFC3339 formatted datetime string
Summary of a database insight resource.