Obtain Tenancy Details

When you file a service request or when you need Autonomous Database tenancy details for other reasons you can obtain these details for your instance. Tenancy details for an instance are available on the Oracle Cloud Infrastructure Console or you can obtain these details by querying the database.

If you need to file a service request use Oracle Cloud Support or contact your support representative and provide the first five of the following items (service requests do not require that you supply the outbound IP address or the availability domain):

If you are connected to the database you can obtain tenancy details by querying the CLOUD_IDENTITY column of the V$PDBS view.

For example, running the following:

SELECT cloud_identity FROM v$pdbs;

CLOUD_IDENTITY
-----------------------------------------------------------------
{
  "DATABASE_NAME" : "DBxxxxxxxxxxxx",
  "REGION" : "us-phoenix-1",
  "TENANT_OCID" : "OCID1.TENANCY.REGION1..ID1",
  "DATABASE_OCID" : "OCID1.AUTONOMOUSDATABASE.OC1.IAD.ID2",
  "COMPARTMENT_OCID" : "ocid1.tenancy.region1..ID3"
  "OUTBOUND_IP_ADDRESS" : 
  [
       "192.0.2.254"
  ]
  "AVAILABILITY_DOMAIN" : "SoSC:region-1-AD-1"
}

If your Autonomous Database instance was created before the tenancy details feature was added and has not been restarted, then this query does not return tenancy details. In this case, as a one-time operation, restart your instance and run the query again. You can restart your instance from the Oracle Cloud Infrastructure console or using the restart API.

Public IP Address Ranges for Autonomous Database

Oracle Cloud Infrastructure provides information about public IP address ranges for Autonomous Databases that are deployed in Oracle Cloud Infrastructure.

See IP Address Ranges for more information.

Database Name

You set the database name when you provision a database or when you rename a database.

The Oracle Cloud Infrastructure Console shows the database name on the Autonomous Database Details page under General Information in the Database Name field.

Region

The Oracle Cloud Infrastructure Console shows the region on the console, in the Regions area.

Tenancy OCID

The tenancy details page shows the tenancy OCID.

See Managing the Tenancy for information on accessing the Tenancy Details page.

See Resource Identifiers for information on Oracle Cloud Identifiers.

Database OCID

The Oracle Cloud Infrastructure Console shows the database OCID on the Autonomous Database Details page under General Information in the OCID field.

See Resource Identifiers for information on Oracle Cloud Identifiers.

Compartment OCID

See Managing Compartments for more information on compartments.

See Resource Identifiers for information on Oracle Cloud Identifiers.

Outbound IP Address

The OUTBOUND_IP_ADDRESS is the outbound IP address of your Autonomous Database instance. You can use the OUTBOUND_IP_ADDRESS when you create a database link to another Autonomous Database instance that uses ACLs to restrict access. In this case, you need to allow the specified outbound IP address to connect to the target Autonomous Database and then create the database link.

The OUTBOUND_IP_ADDRESS shows the outbound IP address in the following cases:

  • When your Autonomous Database instance uses a Public Endpoint.

  • When your Autonomous Database instance uses a Private Endpoint and the database property ROUTE_OUTBOUND_CONNECTIONS is set to '' (the default value).

Note:

When your Autonomous Database instance uses a Private Endpoint and you set the database property ROUTE_OUTBOUND_CONNECTIONS to 'PRIVATE_ENDPOINT', outbound connections go through the private endpoint. See Enhanced Security for Outbound Connections with Private Endpoints for more information.

See Create Database Links from Autonomous Database to a Publicly Accessible Autonomous Database with a Wallet (mTLS) for information on creating database links.

See Configuring Network Access with Access Control Rules (ACLs) for information on configuring access control rules.

Availability Domain

You can view the Availability Domain of your Autonomous Database instance.

This is useful when you need to deploy your Application Servers when your Autonomous Database instance resides in a multi-Availability Domain region. In order to reduce latency as much as possible you would want to deploy your Application Server and database in the same Availability Domain.

See Regions and Availability Domains for more information on Availability Domains.