Try SpotterFetches details about one or multiple DbSystem resources in Oracle Cloud Infrastructure
| "added in version" 2.9.0 of oracle.oci"
Authors: Oracle (@oracle)
preview | supported by community
Install with ansible-galaxy collection install oracle.oci:==5.0.0
collections:
- name: oracle.oci
version: 5.0.0Fetches details about one or multiple DbSystem resources in Oracle Cloud Infrastructure
Lists the DB systems in the specified compartment. You can specify a `backupId` to list only the DB systems that support creating a database using this backup in this compartment.
**Note:** Deprecated for Exadata Cloud Service systems. Use the L(new resource model APIs,https://docs.cloud.oracle.com/iaas/Content/Database/Concepts/exaflexsystem.htm#exaflexsystem_topic-resource_model) instead.
For Exadata Cloud Service instances, support for this API will end on May 15th, 2021. See L(Switching an Exadata DB System to the New Resource Model and APIs,https://docs.cloud.oracle.com/iaas/Content/Database/Concepts/exaflexsystem_topic-resource_model_conversion.htm) for details on converting existing Exadata DB systems to the new resource model.
If I(db_system_id) is specified, the details of a single DbSystem will be returned.
- name: Get a specific db_system
oci_database_db_system_facts:
# required
db_system_id: "ocid1.dbsystem.oc1..xxxxxxEXAMPLExxxxxx"
- name: List db_systems
oci_database_db_system_facts:
# required
compartment_id: "ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx"
# optional
backup_id: "ocid1.backup.oc1..xxxxxxEXAMPLExxxxxx"
sort_by: TIMECREATED
sort_order: ASC
lifecycle_state: PROVISIONING
availability_domain: Uocm:PHX-AD-1
display_name: display_name_example
region:
description:
- The Oracle Cloud Infrastructure region to use for all OCI API requests. If not set,
then the value of the OCI_REGION variable, if any, is used. This option is required
if the region is not specified through a configuration file (See C(config_file_location)).
Please refer to U(https://docs.us-phoenix-1.oraclecloud.com/Content/General/Concepts/regions.htm)
for more information on OCI regions.
type: str
sort_by:
choices:
- TIMECREATED
- DISPLAYNAME
description:
- The field to sort by. You can provide one sort order (`sortOrder`). Default order
for TIMECREATED is descending. Default order for DISPLAYNAME is ascending. The
DISPLAYNAME sort order is case sensitive.
- '**Note:** If you do not include the availability domain filter, the resources are
grouped by availability domain, then sorted.'
type: str
tenancy:
description:
- OCID of your tenancy. If not set, then the value of the OCI_TENANCY variable, if
any, is used. This option is required if the tenancy OCID is not specified through
a configuration file (See C(config_file_location)). To get the tenancy OCID, please
refer U(https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm)
type: str
api_user:
description:
- The OCID of the user, on whose behalf, OCI APIs are invoked. If not set, then the
value of the OCI_USER_ID environment variable, if any, is used. This option is required
if the user is not specified through a configuration file (See C(config_file_location)).
To get the user's OCID, please refer U(https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm).
type: str
auth_type:
choices:
- api_key
- instance_principal
- instance_obo_user
- resource_principal
- security_token
default: api_key
description:
- The type of authentication to use for making API requests. By default C(auth_type="api_key")
based authentication is performed and the API key (see I(api_user_key_file)) in
your config file will be used. If this 'auth_type' module option is not specified,
the value of the OCI_ANSIBLE_AUTH_TYPE, if any, is used. Use C(auth_type="instance_principal")
to use instance principal based authentication when running ansible playbooks within
an OCI compute instance.
type: str
backup_id:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the backup. Specify a backupId to list only the DB systems or DB homes that support
creating a database using this backup in this compartment.
type: str
sort_order:
choices:
- ASC
- DESC
description:
- The sort order to use, either ascending (`ASC`) or descending (`DESC`).
type: str
cert_bundle:
description:
- The full path to a CA certificate bundle to be used for SSL verification. This will
override the default CA certificate bundle. If not set, then the value of the OCI_ANSIBLE_CERT_BUNDLE
variable, if any, is used.
type: str
auth_purpose:
choices:
- service_principal
description:
- The auth purpose which can be used in conjunction with 'auth_type=instance_principal'.
The default auth_purpose for instance_principal is None.
type: str
db_system_id:
aliases:
- id
description:
- The DB system L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm).
- Required to get a specific db_system.
type: str
display_name:
aliases:
- name
description:
- A filter to return only resources that match the entire display name given. The
match is not case sensitive.
type: str
compartment_id:
description:
- The compartment L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm).
- Required to list multiple db_systems.
type: str
lifecycle_state:
choices:
- PROVISIONING
- AVAILABLE
- UPDATING
- TERMINATING
- TERMINATED
- FAILED
- MIGRATED
- MAINTENANCE_IN_PROGRESS
- NEEDS_ATTENTION
- UPGRADING
description:
- A filter to return only resources that match the given lifecycle state exactly.
type: str
api_user_key_file:
description:
- Full path and filename of the private key (in PEM format). If not set, then the
value of the OCI_USER_KEY_FILE variable, if any, is used. This option is required
if the private key is not specified through a configuration file (See C(config_file_location)).
If the key is encrypted with a pass-phrase, the C(api_user_key_pass_phrase) option
must also be provided.
type: str
availability_domain:
description:
- A filter to return only resources that match the given availability domain exactly.
type: str
config_profile_name:
description:
- The profile to load from the config file referenced by C(config_file_location).
If not set, then the value of the OCI_CONFIG_PROFILE environment variable, if any,
is used. Otherwise, defaults to the "DEFAULT" profile in C(config_file_location).
type: str
api_user_fingerprint:
description:
- Fingerprint for the key pair being used. If not set, then the value of the OCI_USER_FINGERPRINT
environment variable, if any, is used. This option is required if the key fingerprint
is not specified through a configuration file (See C(config_file_location)). To
get the key pair's fingerprint value please refer U(https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm).
type: str
config_file_location:
description:
- Path to configuration file. If not set then the value of the OCI_CONFIG_FILE environment
variable, if any, is used. Otherwise, defaults to ~/.oci/config.
type: str
api_user_key_pass_phrase:
description:
- Passphrase used by the key referenced in C(api_user_key_file), if it is encrypted.
If not set, then the value of the OCI_USER_KEY_PASS_PHRASE variable, if any, is
used. This option is required if the key passphrase is not specified through a configuration
file (See C(config_file_location)).
type: str
realm_specific_endpoint_template_enabled:
description:
- Enable/Disable realm specific endpoint template for service client. By Default,
realm specific endpoint template is disabled. If not set, then the value of the
OCI_REALM_SPECIFIC_SERVICE_ENDPOINT_TEMPLATE_ENABLED variable, if any, is used.
type: bool
db_systems:
contains:
availability_domain:
description:
- The name of the availability domain that the DB system is located in.
returned: on success
sample: Uocm:PHX-AD-1
type: str
backup_network_nsg_ids:
description:
- A list of the L(OCIDs,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the network security groups (NSGs) that the backup network of this DB system
belongs to. Setting this to an empty array after the list is created removes
the resource from all NSGs. For more information about NSGs, see L(Security
Rules,https://docs.cloud.oracle.com/Content/Network/Concepts/securityrules.htm).
Applicable only to Exadata systems.
returned: on success
sample: []
type: list
backup_subnet_id:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the backup network subnet the DB system is associated with. Applicable
only to Exadata DB systems.
- '**Subnet Restriction:** See the subnet restrictions information for **subnetId**.'
returned: on success
sample: ocid1.backupsubnet.oc1..xxxxxxEXAMPLExxxxxx
type: str
cluster_name:
description:
- The cluster name for Exadata and 2-node RAC virtual machine DB systems. The
cluster name must begin with an alphabetic character, and may contain hyphens
(-). Underscores (_) are not permitted. The cluster name can be no longer
than 11 characters and is not case sensitive.
returned: on success
sample: cluster_name_example
type: str
compartment_id:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the compartment.
returned: on success
sample: ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx
type: str
cpu_core_count:
description:
- The number of CPU cores enabled on the DB system.
returned: on success
sample: 56
type: int
data_collection_options:
contains:
is_diagnostics_events_enabled:
description:
- Indicates whether diagnostic collection is enabled for the VM cluster/Cloud
VM cluster/VMBM DBCS. Enabling diagnostic collection allows you to receive
Events service notifications for guest VM issues. Diagnostic collection
also allows Oracle to provide enhanced service and proactive support for
your Exadata system. You can enable diagnostic collection during VM cluster/Cloud
VM cluster provisioning. You can also disable or enable it at any time
using the `UpdateVmCluster` or `updateCloudVmCluster` API.
returned: on success
sample: true
type: bool
is_health_monitoring_enabled:
description:
- Indicates whether health monitoring is enabled for the VM cluster / Cloud
VM cluster / VMBM DBCS. Enabling health monitoring allows Oracle to collect
diagnostic data and share it with its operations and support personnel.
You may also receive notifications for some events. Collecting health
diagnostics enables Oracle to provide proactive support and enhanced service
for your system. Optionally enable health monitoring while provisioning
a system. You can also disable or enable health monitoring anytime using
the `UpdateVmCluster`, `UpdateCloudVmCluster` or `updateDbsystem` API.
returned: on success
sample: true
type: bool
is_incident_logs_enabled:
description:
- Indicates whether incident logs and trace collection are enabled for the
VM cluster / Cloud VM cluster / VMBM DBCS. Enabling incident logs collection
allows Oracle to receive Events service notifications for guest VM issues,
collect incident logs and traces, and use them to diagnose issues and
resolve them. Optionally enable incident logs collection while provisioning
a system. You can also disable or enable incident logs collection anytime
using the `UpdateVmCluster`, `updateCloudVmCluster` or `updateDbsystem`
API.
returned: on success
sample: true
type: bool
description:
- ''
returned: on success
type: complex
data_storage_percentage:
description:
- The percentage assigned to DATA storage (user data and database files). The
remaining percentage is assigned to RECO storage (database redo logs, archive
logs, and recovery manager backups). Accepted values are 40 and 80. The default
is 80 percent assigned to DATA storage. Not applicable for virtual machine
DB systems.
returned: on success
sample: 56
type: int
data_storage_size_in_gbs:
description:
- The data storage size, in gigabytes, that is currently available to the DB
system. Applies only for virtual machine DB systems.
returned: on success
sample: 56
type: int
database_edition:
description:
- The Oracle Database edition that applies to all the databases on the DB system.
returned: on success
sample: STANDARD_EDITION
type: str
db_system_options:
contains:
storage_management:
description:
- The storage option used in DB system. ASM - Automatic storage management
LVM - Logical Volume management
returned: on success
sample: ASM
type: str
description:
- ''
returned: on success
type: complex
defined_tags:
description:
- Defined tags for this resource. Each key is predefined and scoped to a namespace.
For more information, see L(Resource Tags,https://docs.cloud.oracle.com/Content/General/Concepts/resourcetags.htm).
returned: on success
sample:
Operations:
CostCenter: US
type: dict
disk_redundancy:
description:
- The type of redundancy configured for the DB system. NORMAL is 2-way redundancy.
HIGH is 3-way redundancy.
returned: on success
sample: HIGH
type: str
display_name:
description:
- The user-friendly name for the DB system. The name does not have to be unique.
returned: on success
sample: display_name_example
type: str
domain:
description:
- The domain name for the DB system.
returned: on success
sample: domain_example
type: str
fault_domains:
description:
- List of the Fault Domains in which this DB system is provisioned.
returned: on success
sample: []
type: list
freeform_tags:
description:
- 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 L(Resource
Tags,https://docs.cloud.oracle.com/Content/General/Concepts/resourcetags.htm).
- 'Example: `{"Department": "Finance"}`'
returned: on success
sample:
Department: Finance
type: dict
hostname:
description:
- The hostname for the DB system.
returned: on success
sample: hostname_example
type: str
id:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the DB system.
returned: on success
sample: ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
type: str
iorm_config_cache:
contains:
db_plans:
contains:
db_name:
description:
- The database name. For the default `DbPlan`, the `dbName` is `default`.
returned: on success
sample: db_name_example
type: str
flash_cache_limit:
description:
- The flash cache limit for this database. This value is internally
configured based on the share value assigned to the database.
returned: on success
sample: flash_cache_limit_example
type: str
share:
description:
- The relative priority of this database.
returned: on success
sample: 56
type: int
description:
- An array of IORM settings for all the database in the Exadata DB system.
returned: on success
type: complex
lifecycle_details:
description:
- Additional information about the current `lifecycleState`.
returned: on success
sample: lifecycle_details_example
type: str
lifecycle_state:
description:
- The current state of IORM configuration for the Exadata DB system.
returned: on success
sample: BOOTSTRAPPING
type: str
objective:
description:
- The current value for the IORM objective. The default is `AUTO`.
returned: on success
sample: LOW_LATENCY
type: str
description:
- ''
- Returned for get operation
returned: on success
type: complex
kms_key_id:
description:
- The OCID of the key container that is used as the master encryption key in
database transparent data encryption (TDE) operations.
returned: on success
sample: ocid1.kmskey.oc1..xxxxxxEXAMPLExxxxxx
type: str
last_maintenance_run_id:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the last maintenance run.
returned: on success
sample: ocid1.lastmaintenancerun.oc1..xxxxxxEXAMPLExxxxxx
type: str
last_patch_history_entry_id:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the last patch history. This value is updated as soon as a patch operation
starts.
returned: on success
sample: ocid1.lastpatchhistoryentry.oc1..xxxxxxEXAMPLExxxxxx
type: str
license_model:
description:
- The Oracle license model that applies to all the databases on the DB system.
The default is LICENSE_INCLUDED.
returned: on success
sample: LICENSE_INCLUDED
type: str
lifecycle_details:
description:
- Additional information about the current lifecycle state.
returned: on success
sample: lifecycle_details_example
type: str
lifecycle_state:
description:
- The current state of the DB system.
returned: on success
sample: PROVISIONING
type: str
listener_port:
description:
- The port number configured for the listener on the DB system.
returned: on success
sample: 56
type: int
maintenance_window:
contains:
custom_action_timeout_in_mins:
description:
- Determines the amount of time the system will wait before the start of
each database server patching operation. Custom action timeout is in minutes
and valid value is between 15 to 120 (inclusive).
returned: on success
sample: 56
type: int
days_of_week:
contains:
name:
description:
- Name of the day of the week.
returned: on success
sample: MONDAY
type: str
description:
- Days during the week when maintenance should be performed.
returned: on success
type: complex
hours_of_day:
description:
- The window of hours during the day when maintenance should be performed.
The window is a 4 hour slot. Valid values are - 0 - represents time slot
0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents
time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC
- 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot
20:00 - 23:59 UTC
returned: on success
sample: []
type: list
is_custom_action_timeout_enabled:
description:
- If true, enables the configuration of a custom action timeout (waiting
period) between database server patching operations.
returned: on success
sample: true
type: bool
is_monthly_patching_enabled:
description:
- If true, enables the monthly patching option.
returned: on success
sample: true
type: bool
lead_time_in_weeks:
description:
- Lead time window allows user to set a lead time to prepare for a down
time. The lead time is in weeks and valid value is between 1 to 4.
returned: on success
sample: 56
type: int
months:
contains:
name:
description:
- Name of the month of the year.
returned: on success
sample: JANUARY
type: str
description:
- Months during the year when maintenance should be performed.
returned: on success
type: complex
patching_mode:
description:
- Cloud Exadata infrastructure node patching method, either "ROLLING" or
"NONROLLING". Default value is ROLLING.
- '*IMPORTANT*: Non-rolling infrastructure patching involves system down
time. See L(Oracle-Managed Infrastructure Maintenance Updates,https://docs.cloud.oracle.com/iaas/Content/Database/Concepts/examaintenance.htm#Oracle)
for more information.'
returned: on success
sample: ROLLING
type: str
preference:
description:
- The maintenance window scheduling preference.
returned: on success
sample: NO_PREFERENCE
type: str
weeks_of_month:
description:
- Weeks during the month when maintenance should be performed. Weeks start
on the 1st, 8th, 15th, and 22nd days of the month, and have a duration
of 7 days. Weeks start and end based on calendar dates, not days of the
week. For example, to allow maintenance during the 2nd week of the month
(from the 8th day to the 14th day of the month), use the value 2. Maintenance
cannot be scheduled for the fifth week of months that contain more than
28 days. Note that this parameter works in conjunction with the daysOfWeek
and hoursOfDay parameters to allow you to specify specific days of the
week and hours that maintenance will be performed.
returned: on success
sample: []
type: list
description:
- ''
returned: on success
type: complex
memory_size_in_gbs:
description:
- Memory allocated to the DB system, in gigabytes.
returned: on success
sample: 56
type: int
next_maintenance_run_id:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the next maintenance run.
returned: on success
sample: ocid1.nextmaintenancerun.oc1..xxxxxxEXAMPLExxxxxx
type: str
node_count:
description:
- The number of nodes in the DB system. For RAC DB systems, the value is greater
than 1.
returned: on success
sample: 56
type: int
nsg_ids:
description:
- The list of L(OCIDs,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
for the network security groups (NSGs) to which this resource belongs. Setting
this to an empty list removes all resources from all NSGs. For more information
about NSGs, see L(Security Rules,https://docs.cloud.oracle.com/Content/Network/Concepts/securityrules.htm).
**NsgIds restrictions:** - A network security group (NSG) is optional for
Autonomous Databases with private access. The nsgIds list can be empty.
returned: on success
sample: []
type: list
os_version:
description:
- The most recent OS Patch Version applied on the DB system.
returned: on success
sample: os_version_example
type: str
point_in_time_data_disk_clone_timestamp:
description:
- The point in time for a cloned database system when the data disks were cloned
from the source database system, as described in L(RFC 3339,https://tools.ietf.org/rfc/rfc3339).
returned: on success
sample: '2013-10-20T19:20:30+01:00'
type: str
reco_storage_size_in_gb:
description:
- The RECO/REDO storage size, in gigabytes, that is currently allocated to the
DB system. Applies only for virtual machine DB systems.
returned: on success
sample: 56
type: int
scan_dns_name:
description:
- The FQDN of the DNS record for the SCAN IP addresses that are associated with
the DB system.
returned: on success
sample: scan_dns_name_example
type: str
scan_dns_record_id:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the DNS record for the SCAN IP addresses that are associated with the DB
system.
returned: on success
sample: ocid1.scandnsrecord.oc1..xxxxxxEXAMPLExxxxxx
type: str
scan_ip_ids:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the Single Client Access Name (SCAN) IP addresses associated with the DB
system. SCAN IP addresses are typically used for load balancing and are not
assigned to any interface. Oracle Clusterware directs the requests to the
appropriate nodes in the cluster.
- '**Note:** For a single-node DB system, this list is empty.'
returned: on success
sample: []
type: list
shape:
description:
- The shape of the DB system. The shape determines resources to allocate to
the DB system. - For virtual machine shapes, the number of CPU cores and memory
- For bare metal and Exadata shapes, the number of CPU cores, storage, and
memory
returned: on success
sample: shape_example
type: str
source_db_system_id:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the DB system.
returned: on success
sample: ocid1.sourcedbsystem.oc1..xxxxxxEXAMPLExxxxxx
type: str
sparse_diskgroup:
description:
- True, if Sparse Diskgroup is configured for Exadata dbsystem, False, if Sparse
diskgroup was not configured.
returned: on success
sample: true
type: bool
ssh_public_keys:
description:
- The public key portion of one or more key pairs used for SSH access to the
DB system.
returned: on success
sample:
- ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAQEAz...
type: list
storage_volume_performance_mode:
description:
- The block storage volume performance level. Valid values are `BALANCED` and
`HIGH_PERFORMANCE`. See L(Block Volume Performance,https://docs.cloud.oracle.com/Content/Block/Concepts/blockvolumeperformance.htm)
for more information.
returned: on success
sample: BALANCED
type: str
subnet_id:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the subnet the DB system is associated with.
- '**Subnet Restrictions:** - For bare metal DB systems and for single node
virtual machine DB systems, do not use a subnet that overlaps with 192.168.16.16/28.
- For Exadata and virtual machine 2-node RAC DB systems, do not use a subnet
that overlaps with 192.168.128.0/20.'
- These subnets are used by the Oracle Clusterware private interconnect on the
database instance. Specifying an overlapping subnet will cause the private
interconnect to malfunction. This restriction applies to both the client subnet
and backup subnet.
returned: on success
sample: ocid1.subnet.oc1..xxxxxxEXAMPLExxxxxx
type: str
time_created:
description:
- The date and time the DB system was created.
returned: on success
sample: '2013-10-20T19:20:30+01:00'
type: str
time_zone:
description:
- The time zone of the DB system. For details, see L(DB System Time Zones,https://docs.cloud.oracle.com/Content/Database/References/timezones.htm).
returned: on success
sample: time_zone_example
type: str
version:
description:
- The Oracle Database version of the DB system.
returned: on success
sample: version_example
type: str
vip_ids:
description:
- The L(OCID,https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
of the virtual IP (VIP) addresses associated with the DB system. The Cluster
Ready Services (CRS) creates and maintains one VIP address for each node in
the DB system to enable failover. If one node fails, the VIP is reassigned
to another active node in the cluster.
- '**Note:** For a single-node DB system, this list is empty.'
returned: on success
sample: []
type: list
zone_id:
description:
- The OCID of the zone the DB system is associated with.
returned: on success
sample: ocid1.zone.oc1..xxxxxxEXAMPLExxxxxx
type: str
description:
- List of DbSystem resources
returned: on success
sample:
- availability_domain: Uocm:PHX-AD-1
backup_network_nsg_ids: []
backup_subnet_id: ocid1.backupsubnet.oc1..xxxxxxEXAMPLExxxxxx
cluster_name: cluster_name_example
compartment_id: ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx
cpu_core_count: 56
data_collection_options:
is_diagnostics_events_enabled: true
is_health_monitoring_enabled: true
is_incident_logs_enabled: true
data_storage_percentage: 56
data_storage_size_in_gbs: 56
database_edition: STANDARD_EDITION
db_system_options:
storage_management: ASM
defined_tags:
Operations:
CostCenter: US
disk_redundancy: HIGH
display_name: display_name_example
domain: domain_example
fault_domains: []
freeform_tags:
Department: Finance
hostname: hostname_example
id: ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
iorm_config_cache:
db_plans:
- db_name: db_name_example
flash_cache_limit: flash_cache_limit_example
share: 56
lifecycle_details: lifecycle_details_example
lifecycle_state: BOOTSTRAPPING
objective: LOW_LATENCY
kms_key_id: ocid1.kmskey.oc1..xxxxxxEXAMPLExxxxxx
last_maintenance_run_id: ocid1.lastmaintenancerun.oc1..xxxxxxEXAMPLExxxxxx
last_patch_history_entry_id: ocid1.lastpatchhistoryentry.oc1..xxxxxxEXAMPLExxxxxx
license_model: LICENSE_INCLUDED
lifecycle_details: lifecycle_details_example
lifecycle_state: PROVISIONING
listener_port: 56
maintenance_window:
custom_action_timeout_in_mins: 56
days_of_week:
- name: MONDAY
hours_of_day: []
is_custom_action_timeout_enabled: true
is_monthly_patching_enabled: true
lead_time_in_weeks: 56
months:
- name: JANUARY
patching_mode: ROLLING
preference: NO_PREFERENCE
weeks_of_month: []
memory_size_in_gbs: 56
next_maintenance_run_id: ocid1.nextmaintenancerun.oc1..xxxxxxEXAMPLExxxxxx
node_count: 56
nsg_ids: []
os_version: os_version_example
point_in_time_data_disk_clone_timestamp: '2013-10-20T19:20:30+01:00'
reco_storage_size_in_gb: 56
scan_dns_name: scan_dns_name_example
scan_dns_record_id: ocid1.scandnsrecord.oc1..xxxxxxEXAMPLExxxxxx
scan_ip_ids: []
shape: shape_example
source_db_system_id: ocid1.sourcedbsystem.oc1..xxxxxxEXAMPLExxxxxx
sparse_diskgroup: true
ssh_public_keys:
- ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAQEAz...
storage_volume_performance_mode: BALANCED
subnet_id: ocid1.subnet.oc1..xxxxxxEXAMPLExxxxxx
time_created: '2013-10-20T19:20:30+01:00'
time_zone: time_zone_example
version: version_example
vip_ids: []
zone_id: ocid1.zone.oc1..xxxxxxEXAMPLExxxxxx
type: complex