This topic gives an overview of connecting a client to an Autonomous Database and describes how to obtain the credentials and information you need to create a connection.
Applications and tools connect to Autonomous Databases by using Oracle Net Services (also known as SQL*Net). SQL*Net supports a variety of connection types to Autonomous Databases, including Oracle Call Interface (OCI), ODBC drivers, JDBC OC, and JDBC Thin Driver.
To support connections of any type, you'll need to download the client security credentials and network configuration settings required to access your database. You'll also need to supply the applicable TNS names or connection strings for a connection, depending on the client application or tool, type of connection, and service level. You can view or copy the TNS names and connection strings in the DB Connection dialog for your Autonomous Database. For detailed information about the TNS names, see Predefined Database Service Names for Autonomous Transaction Processing and Predefined Database Service Names for Autonomous Data Warehouse.
Connecting from a VCN
To connect to Autonomous Databases from a VCN, the VCN must be configured with one of the following gateways:
- internet gateway: For access from a public subnet in the VCN
- service gateway: For access from a private subnet in the VCN
The client credentials .zip that you download contains the following files:
- cwallet.sso - Oracle auto-login wallet
- ewallet.p12 - PKCS #12 wallet file associated with the auto-login wallet
- sqlnet.ora - SQL*Net profile configuration file that includes the wallet location and TNSNAMES naming method
- tnsnames.ora - SQL*Net configuration file that contains network service names mapped to connect descriptors for the local naming method
- Java Key Store (JKS) files - Key store files for use with JDBC Thin Connections
Wallet files, along with the database user ID and password, provide access to data in your Autonomous Database. Store wallet files in a secure location. Share wallet files only with authorized users. If wallet files are transmitted in a way that might be accessed by unauthorized users (for example, over public email), transmit the wallet password separately and securely.
Before You Begin
The Autonomous Database is preconfigured to support Oracle Net Services (a TNS listener is installed and configured to use secure TCPS and client credentials.) The client computer must be prepared to use Oracle Net Services to connect to the Autonomous Database. Preparing your client includes downloading the client credentials. See the following links for steps you might have to perform before you access the client credentials and connection information for your Autonomous Database
- Open the navigation menu. Under Database, click Autonomous Transaction Processing or Autonomous Data Warehouse.
- Choose your Compartment.
- In the list of Autonomous Databases, click on the display name of the database you are interested in.
- Click DB Connection.
To obtain the client credentials, click Download.
You will be prompted to provide a password to encrypt the keys inside the wallet. The password must be at least 8 characters long and must include at least 1 letter and either 1 numeric character or 1 special character.
Save the client credentials zip file to a secure location. See About Downloading Client Credentials for information about the files included in the download.
- Take note of or copy the TNS names or connection strings you need for your connection. See About Connecting to Autonomous Databases for information about making connections.
Using the API
Use the GenerateAutonomousDatabaseWallet API operation to download the client credentials for your Autonomous Database.
For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.