Table: oci_database_db_home - Query OCI Database DB Homes using SQL

A DB Home is a directory where Oracle Database software is installed. It can contain multiple databases and has specific directory structures and files. Within a DB System, you can have multiple DB Homes and each DB Home can run a different version of the Oracle Database software.

Table Usage Guide

The oci_database_db_home table provides insights into DB Homes within Oracle Cloud Infrastructure Database service. As a Database administrator or a Cloud engineer, explore DB Home-specific details through this table, including its lifecycle state, compartment ID, and associated DB system ID. Utilize it to uncover information about DB Homes, such as their software version, time created, and the last patch history entry.

Examples

Basic info

Explore the lifecycle state and creation time of your Oracle Cloud Infrastructure databases to understand their current status and longevity. This can help in managing and planning resources effectively.

select
  id,
  display_name,
  lifecycle_state,
  time_created
from
  oci_database_db_home;

select
  id,
  display_name,
  lifecycle_state,
  time_created
from
  oci_database_db_home;

List db homes that are not available

Discover the database homes that are not currently available. This can be useful in identifying potential issues or disruptions in your database services.

select
  id,
  display_name,
  lifecycle_state,
  time_created
from
  oci_database_db_home
where
  lifecycle_state <> 'AVAILABLE';

select
  id,
  display_name,
  lifecycle_state,
  time_created
from
  oci_database_db_home
where
  lifecycle_state <> 'AVAILABLE';

Schema for oci_database_db_home

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
compartment_id	text	=	The OCID of the compartment in Tenant in which the resource is located.
database_software_image_id	text		The database software image OCID.
db_home_location	text		The location of the oracle database home.
db_system_id	text	=	The OCID of the DB system.
db_version	text	=	The oracle database version.
defined_tags	jsonb		Defined tags for resource. Defined tags are set up in your tenancy by an administrator. Only users granted permission to work with the defined tags can apply them to resources.
display_name	text	=	The user-friendly name for the database home. It does not have to be unique.
freeform_tags	jsonb		Free-form tags for resource. This tags can be applied by any user with permissions on the resource.
id	text	=	The OCID of the database home.
kms_key_id	text		The OCID of the key container that is used as the master encryption key in database transparent data encryption (TDE) operations.
last_patch_history_entry_id	text		The OCID of the last patch history.
lifecycle_details	text		Additional information about the current lifecycle state.
lifecycle_state	text	=	The current state of the database home.
one_off_patches	jsonb		List of one-off patches for database homes.
region	text		The OCI region in which the resource is located.
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
tags	jsonb		A map of tags for the resource.
tenant_id	text	=, !=, ~~, ~~, !~~, !~~	The OCID of the Tenant in which the resource is located.
tenant_name	text		The name of the Tenant in which the resource is located.
time_created	timestamp with time zone		The date and time the database home was created.
title	text		Title of the resource.
vm_cluster_id	text	=	The OCID of the VM cluster.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- oci

You can pass the configuration to the command with the --config argument:

steampipe_export_oci --config '<your_config>' oci_database_db_home