Get Autonomous Database Result
A collection of values returned by getAutonomousDatabase.
Constructors
Properties
The current amount of storage in use for user and system data, in terabytes (TB).
The amount of storage currently allocated for the database tables and billed for, rounded up. When auto-scaling is not enabled, this value is equal to the dataStorageSizeInTBs
value. You can compare this value to the actualUsedDataStorageSizeInTBs
value to determine if a manual shrink operation is appropriate for your allocated storage.
The client IP access control list (ACL). This feature is available for Autonomous Database Serverless (https://docs.oracle.com/en/cloud/paas/autonomous-database/index.html) and on Exadata Cloud@Customer. Only clients connecting from an IP address included in the ACL may access the Autonomous Database instance. If arePrimaryWhitelistedIpsUsed
is 'TRUE' then Autonomous Database uses this primary's IP access control list (ACL) for the disaster recovery peer called standbywhitelistedips
.
The database OCID.
Indicates if auto scaling is enabled for the Autonomous Database CPU core count.
Indicates if auto scaling is enabled for the Autonomous Database storage.
List of Oracle Database versions available for a database upgrade. If there are no version upgrades available, this list is empty.
Retention period, in days, for backups.
The character set for the autonomous database.
The compute amount (CPUs) available to the database.
The number of CPU cores to be made available to the database. When the ECPU is selected, the value for cpuCoreCount is 0. For Autonomous Database on Dedicated Exadata infrastructure, the maximum number of cores is determined by the infrastructure shape. See Characteristics of Infrastructure Shapes for shape details.
The quantity of data in the database, in gigabytes.
The maximum storage that can be allocated for the database, in terabytes.
The DB node storage size in, in gigabytes.
The user-friendly name for the Autonomous Database. The name does not have to be unique.
Indicates the number of seconds of data loss for a Data Guard failover.
The area assigned to In-Memory tables in Autonomous Database.
Information about the current lifecycle state.
Parameter that allows users to select an acceptable maximum data loss limit in seconds, up to which Automatic Failover will be triggered when necessary for a Local Autonomous Data Guard
Indicates whether the Autonomous Database has local (in-region) Data Guard enabled. Not applicable to cross-region Autonomous Data Guard associations, or to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
The amount of memory (in GBs) enabled per ECPU or OCPU.
Specifies if the Autonomous Database requires mTLS connections.
The national character set for the autonomous database. The default is AL16UTF16. Allowed values are: AL16UTF16 or UTF8.
The date and time when the next long-term backup would be created.
The list of OCIDs of standby databases located in Autonomous Data Guard remote regions that are associated with the source database. Note that for Autonomous Database Serverless instances, standby databases located in the same region as the source primary database do not have OCIDs.
Indicates if the Autonomous Database version is a preview version with service terms accepted.
The private endpoint for the resource.
The private endpoint Ip address for the resource.
The private endpoint label for the resource.
An array of CPU values that an Autonomous Database can be scaled to.
Indicates whether the Autonomous Database has Cross Region Data Guard enabled. Not applicable to Autonomous Databases using dedicated Exadata infrastructure or Exadata Cloud@Customer infrastructure.
The URL of the Service Console for the Autonomous Database.
The URL of the SQL web developer.
The list of regions that support the creation of an Autonomous Database clone or an Autonomous Data Guard standby database.
The date and time the Autonomous Database was created.
The date and time the Autonomous Data Guard role was switched for the Autonomous Database. For databases that have standbys in both the primary Data Guard region and a remote Data Guard standby region, this is the latest timestamp of either the database using the "primary" role in the primary Data Guard region, or database located in the remote Data Guard standby region.
The date and time the Always Free database will be automatically deleted because of inactivity. If the database is in the STOPPED state and without activity until this time, it will be deleted.
The date and time that Autonomous Data Guard was enabled for an Autonomous Database where the standby was provisioned in the same region as the primary database.
The date and time when maintenance will begin.
The date and time when maintenance will end.
The timestamp of the last failover operation.
The date and time when last refresh happened.
The refresh point timestamp (UTC). The refresh point is the time to which the database was most recently refreshed. Data created after the refresh point is not included in the refresh.
The timestamp of the last switchover operation for the Autonomous Database.
The date and time the Always Free database will be stopped because of inactivity. If this time is reached without any database activity, the database will automatically be put into the STOPPED state.
The storage space consumed by Autonomous Database in GBs.
The amount of storage that has been used, in terabytes.
The ID to an Azure Resource Manager vnet resource.