Connect to Oracle Autonomous Databases

Learn to create a connection to Oracle Autonomous Transaction Processing or Autonomous Data Warehouse to use as sources and targets for OCI GoldenGate.

Related Topics

Before you begin

Ensure that you:

Connect to Autonomous Database

Note:

For Autonomous Database Shared connections with remote peers configured with Data Guard, failover automatically occurs from the primary to the standby database, so long as you configure your network to resolve the standby database's host name from the primary database's subnet. You can select the database or manually enter the database details when you create the connection. If you manually enter the database details, ensure that you enter the database connection string of both the primary and standby databases.
To create an Autonomous Database connection:
  1. From the OCI GoldenGate Overview page, click Connections.
    You can also click Create Connection under the Get started section and skip to step 3.
  2. On the Connections page, click Create Connection.
  3. On the Create Connection page, complete the fields as follows:
    1. For Name, enter a name for the connection.
    2. (Optional) For Description, enter a description that helps you distinguish this connection from others.
    3. For Compartment, select the compartment in which to create the connection.
    4. For Type, select Oracle Autonomous Database.
    5. For Database details, you can choose:
      • Select database to select from a list of existing Autonomous Databases in the selected compartment, and then select a password secret from the dropdown or click Change compartment to choose a password secret in a different compartment.

        Note:

        When you select an existing Autonomous Database, a private endpoint is created automatically.
      • Enter database information and then manually complete the following fields:
        • If not uploading a database wallet, enter the Database connection string.
        • If you don't enter a Database connection string, you must upload the Database wallet.

          Note:

          To use Wallet secrets, ensure that you select Use secrets in vault in the Settings tab under Advanced Options, located at the bottom of this form.
    6. For Database username, enter the username to connect to the database with.
    7. For Database user password, enter the database password.

      Note:

      To use password secrets, ensure that you select Use secrets in vault in the Settings tab under Advanced Options, located at the bottom of this form.
    8. For Network connectivity, select a Traffic routing method:
      • Shared endpoint, to share an endpoint with the assigned deployment. You must allow connectivity from the deployment's ingress IP.
      • Dedicated endpoint, for network traffic through a dedicated endpoint in the assigned subnet in your VCN. You must allow connectivity from this connection's ingress IPs.

        Then, select a Session mode:

        • Direct, to use the local listener running on a single database node, and then select your subnet.
        • Redirect, to use the SCAN listener used in Oracle Real Application Cluster (RAC) deployments, and then select your subnet.

          Note:

          When you configure a dedicated connection, the subnet configuration depends on the access mode of the database:
          • If it's a private database, then its subnet will be used. The connection's private endpoint, and thus its ingress IPs, will be located in the same subnet as the database's private endpoint.
          • If it's a public database, then you must specify a subnet in which the connection's private endpoint is created. See GoldenGate connectivity.

        Note:

        If a dedicated connection remains unassigned for seven days, then the service converts it to a shared connection.
    9. Expand Show advanced options. You can configure the following options:
      • Security:
        • Select Use Oracle-managed encryption key to leave all encryption key management to Oracle.
        • Select Use customer-managed encryption key to select a specific encryption key stored in your OCI Vault to encrypt your connection credentials.
      • Settings:
        • Select Use vault secrets to use a password secret for your connection.
      • Tags: Add tags to organize your resources.
  4. Click Create.
After the connection is created, it appears in the Connections list. Ensure that you assign the connection to a deployment to use it as a source or target in a replication.

Known issues

Action required for Autonomous Databases that use mTLS Authentication

When an Autonomous Database wallet is rotated, the OCI GoldenGate connection to this database must be refreshed to retrieve the latest wallet information.

For more information see, My Oracle Support (MOS) Document 2911553.1.

To refresh an Autonomous Database connection: Edit and save the connection to the Autonomous Database (Autonomous Transaction Processing or Autonomous Data Warehouse). Saving the connection automatically downloads and refreshes the wallet. No other changes to the connection is needed.

To verify:

  1. Launch the deployment console for a deployment that uses the Autonomous Database connection.
  2. In the deployment console, open the navigation menu, and then click Configuration.
  3. On the Credentials screen, observe the Autonomous Database connection string.

    Before the wallet is refreshed, the connection string looks like the following:

    ggadmin@(DESCRIPTION=(TRANSPORT_CONNECT_TIMEOUT=3)(CONNECT_TIMEOUT=60)(RECV_TIMEOUT=120)(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=adb.us-phoenix-1.oraclecloud.com))(CONNECT_DATA=(COLOCATION_TAG=ogginstance)(FAILOVER_MODE=(TYPE=SESSION)(METHOD=BASIC)(OVERRIDE=TRUE))(service_name=<adb-servicename>_low.adb.oraclecloud.com))(security=(MY_WALLET_DIRECTORY=“/u02/connections/ocid1.goldengateconnection.oc1.phx.<ocid>/wallet”)(SSL_SERVER_DN_MATCH=TRUE)(ssl_server_cert_dn=“CN=adwc.uscom-east-1.oraclecloud.com,
        OU=Oracle BMCS US, O=Oracle Corporation, L=Redwood City, ST=California,
        C=US”)))

    After the wallet is refreshed, the connection string is updated to look like the following:

    ggadmin@(DESCRIPTION=(TRANSPORT_CONNECT_TIMEOUT=3)(CONNECT_TIMEOUT=60)(RECV_TIMEOUT=120)(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=adb.us-phoenix-1.oraclecloud.com))(CONNECT_DATA=(COLOCATION_TAG=ogginstance)(FAILOVER_MODE=(TYPE=SESSION)(METHOD=BASIC)(OVERRIDE=TRUE))(service_name=<adb-servicename>_low.adb.oraclecloud.com))(security=(MY_WALLET_DIRECTORY=“/u02/connections/ocid1.goldengateconnection.oc1.phx.<ocid>/wallet”)(SSL_SERVER_DN_MATCH=TRUE)(ssl_server_dn_match=yes)))