Autonomous Database Entity Details

You can mount additional catalogs from other Autonomous Databases in the same tenancy.

Before selecting whether or not to mount a catalog, you can browse the databases using the catalog to get additional information about each one.

Click All filter from the top and select Autonomous Database from OCI faceted filter panel in the left.

Selecting the above options lists all the autonomous databases in your tenancy.

You can view details about the database and launch the following applications from the Database actions drop-down field in the Autonomous Database Entity dialog box:

• Database Transforms

• Intelligent Data Lake

• Graph Studio

• APEX

• Machine learning notebook

• Machine learning user management

• Mongo Database

• ORDS

• SQL Developer

You can hover over the autonomous database whose details you want to view.

Click Actions next to the Autonomous Database entity and select View Details to view the following details:

General

The General tab displays the tenancy details, backup and recovery information, and network and maintenance details of the selected autonomous database.

Under General Information, you can view:

• Database Name: You set the database name when you provision a database or when you rename a database.

• Workload Type: The Autonomous Database supports different workload types, including: Data Warehouse, Transaction Processing, JSON Database, and APEX Service.

• Compartment: When creating a compartment, you must provide a name for it (maximum 100 characters, including letters, numbers, periods, hyphens, and underscores) that is unique within its parent compartment. Oracle will also assign the compartment a unique ID called an Oracle Cloud ID.

• OCID: It displays the Oracle Cloud ID. See Resource Identifiers for more information.

• Created: Displays the date when the autonomous database was created.

• License type: The License type field shows on the Autonomous Database Information tab when you enable the Bring Your Own License (BYOL) option. This field shows your license and Oracle Database Edition.

• Database Version: Specifies the version of the Database.

• Lifecycle State: You can view availability information for an autonomous database instance in this field.

• Instance type: You can view the instance details of the autonomous database.

• Character Set: The Autonomous Database default database character set is Unicode AL32UTF8 and the default national character set is AL16UTF16. When you provision a database, depending on the workload type, you can select a database character set and a national character set.

• Mode: You can select any of the following autonomous database operation modes:

  • Read/Write

  • Read-Only

  • Restricted

  The default mode is Read/Write.

Under Resources you can view:

• Compute: This field displays the autonomous database instance ECPU count (OCPU count if your database uses OCPUs).

Under APEX you can view, instance name that displays the autonomous database instance you use to create an APEX Service instance using an OCI.

Under Data Safe you can view, Status field that displays if you have registered the autonomous database with Oracle Data Safe. Oracle Data Safe, which is included with Autonomous Database, provides a unified control center that helps you manage the day-to-day security and compliance requirements of Oracle Databases.

Under Disaster Recovery, you can view:

• Role: Each autonomous database has a designated role: primary, standby, or snapshot standby.

• Local: If there is a local peer database, Autonomous Data Guard standby, this field shows the local standby’s availability domain. See Use Standby Databases with Autonomous Data Guard for Disaster Recovery for more information.

• Cross-region: Displays if cross-region Autonomous Data Guard is enabled by provisioning a remote standby instance.

Under Backup, you can view:

• Automatic backup retention period: The backup retention period specifies how many days automatic backups are retained and the period for which you are billed for the automatic backups that are retained. If you change the backup retention period to a shorter period and automatic backups exist that are older, you are no longer billed for the automatic backups with timestamps beyond the specified retention period.

• Total backup storage: Displays the total storage being billed, including for automatic backups and if there are long-term backups, this also includes the long term backup storage.

• Last Automatic backup: Shows the timestamp of the last automatic backup.

• Next long term backup: When you configure scheduled long-term backups, this field displays the timestamp for the next long-term backup.

• Long term backup schedule: Displays the long-term backup schedule, with links to edit or delete a long-term backup schedule.

Under Network, you can view:

• Access type: Displays the specified access type for the Autonomous Database instance.

• Access control list: This field displays if Access Control Lists (ACLs) of an Autonomous Database Instance are defined. It can display the following two values:

  • Enabled: The field displays Enabled when ACLs of the Autonomous Database Instance are defined.

  • Disabled: The field displays Disabled when ACLs of the Autonomous Database Instance are not defined.

• Mutual TLS(mTLS) authentication: Displays if your Autonomous Database instance is configured to only allow mTLS connections.

Under Maintenance, you can view:

• Patch level:You can view Autonomous Database patch information.

• Next maintenance: This field in the Oracle Cloud Infrastructure Console reflects a maintenance window date and time based on the patch level.

• Customer contacts: When customer contacts are set, Oracle sends notifications to the specified email addresses for Autonomous Database service-related issues.

Under Encryption, you can view the Encryption key field that displays the master encryption key the Oracle Autonomous Database creates.

Lineage

Lineage displays all known information about the upstream dependencies of the entity, and therefore how the entity was created and how it is linked to other entities.

For example, for an autonomous database that you create, the lineage is just the cloud. For an autonomous database you create from cloud storage, the lineage includes the ingest directive for the load and the cloud object store path that is the source of the database.

Pointing to the name of an item in the lineage displays the database name, the application that created it, the type of entity, the path to it, and the schema it is in.

Arrows point from an entity to the entity that it derives from.

You can increase or decrease the size of the displayed objects by using the + (plus) and - (minus) keys. You can reposition the objects by grabbing a blank spot in the display and dragging vertically or horizontally.

Impact

Impact shows all known information about the downstream use of an entity, and therefore how a change in the definition of an entity may affect other entities that depend on it.

Click Actions next to the Autonomous Database entity and select + Create Database Link to create database links from the Autonomous Database. See Load Data from Oracle and Non-Oracle Databases using Database Links.

Click Actions next to the Autonomous Database entity and select Create Share Recipient to create share recipient from the Autonomous Database. See Create Share Recipient to create a share recipient from the Autonomous Database.