Troubleshoot connectivity issues
Learn about some common issues you may encounter with connections and how to address them.
Troubleshoot connectivity issues with Oracle AI Database
Learn to troubleshoot connectivity issues in OCI GoldenGate for on-premises databases or third-party cloud databases.
Connectivity issues are among the most common errors encountered in OCI GoldenGate. If you experience an issue connecting to your on-premises database or a database running in a third-party cloud, the following tips may help you troubleshoot:
-
Ensure you review the instructions to Create a connection to Oracle AI Database.
-
In the Network connectivity section, if you selected Dedicated endpoint for Traffic routing method:
-
For Real-Application Cluster (RAC) databases using Single Client Access Name (SCAN), you must select Redirect for Session mode, and then enter the SCAN listener FQDN.
-
For non-RAC databases, you can enter any FQDN (fully qualified database name). It doesn't have to be the name of a database. It does, however, have to be unique within the Compartment and in a valid format. For example,
somehost.example.com. -
You must refer to the FQDN entered in the Database connection string field, for example,
somehost.example.com:1521/myservicenameexample
If you enter an IP address, OCI GoldenGate converts it to an FQDN. For example, if you enter 10.0.1.43, OCI GoldenGate converts it to
ip-10-0-1-43.ociggsvc.oraclevcn.comand ensures that it's resolvable within the selected subnet.Note: If you don’t refer to the FQDN provided in the Database connection string, then OCI GoldenGate won’t be able to connect to the database, and you may encounter the following error messages:
- Error - OGG-08110 Login failed. OCI Error ORA (status = 12170-ORA-12170: TNS:Connect timeout occurred)
- Error - OGG-08110 Login failed. OCI Error ORA (status = 12154-ORA-12154: TNS:could not resolve the connect identifier specified)
-
-
You can connect to databases outside of Oracle Cloud Infrastructure (OCI) using a private network connection.
-
Ensure that you select Dedicated endpoint, which allows connectivity from OCI GoldenGate to the database node's private IP.
-
(Oracle Databases only) Select the appropriate Session mode. Choose Direct to use the local listener running on a single database node, or Redirect to use the SCAN listener used in RAC deployments.
-
Select a subnet that has access to the FQDN that you provided (optional for RAC databases). OCI GoldenGate creates a reverse connection private endpoint in that subnet to access your database.
Note: If you’re trying to connect to an on-premises database or a database running in a third-party cloud, you must ensure that you configure OCI Networking to enable access from the subnet you provided into the network where the database resides. OCI offers different ways to achieve this, including FastConnect or IPSec VPN.
-
You must create security rules that allow ingress from the subnet provided for port 1521, or whatever port you're trying to access. If you don't create this security rule, then OCI blocks traffic to this port.
-
-
After creating the connection, review its details. Observe the Ingress IPs field. It may contain one or more IP addresses. The connection to the database from OCI GoldenGate originates from one of these IP addresses. You must ensure that the appropriate subnet security rules are in place to allow connectivity from these IP addresses into the database node's private IP.
-
If you selected Shared endpoint for Routing method, the connection from OCI GoldenGate originates from the Ingress IPs listed in the Assigned deployments table section.
-
If you selected Dedicated endpoint for Routing method, the connection from OCI GoldenGate originates from the Ingress IPs listed in the Connection information section.
-
Troubleshoot issues with Data Transforms connections
Learn how to address connectivity issues with connections in OCI GoldenGate Data Transforms.
If you encounter Test connection errors when you attempt to create a connection in the OCI GoldenGate Data Transforms deployment console, then ensure that you create and assign a Generic connection type to the Data Transforms deployment for each connection you use in OCI GoldenGate Data Transforms.
Learn more about Supported connection types for Data Transforms.
Resolve FQDN conflicts in connection assignment validation
OCI GoldenGate validates connection assignments and connection updates to prevent conflicting fully qualified domain names (FQDNs) from creating ambiguous network routing within a deployment.
You can assign a connection using Dedicated endpoint routing to a deployment only when no other connection assigned to that deployment uses the same FQDN. Multiple connections using Shared endpoint routing can use the same FQDN.
Review assigned connections for repeated FQDNs before adding assignments and changing connection hostnames or routing methods. To resolve conflicts, change affected connections to Shared endpoint routing when the network configuration permits.
Validation also applies to connection updates. Changes to a hostname-bearing property, such as the connection string, bootstrap servers, or Traffic Routing Method, introduce conflicts and are rejected.
You’re permitted to update a connection from dedicated to shared endpoint routing when another dedicated connection uses that FQDN.
| Operation involving the same FQDN | Validation outcome |
|---|---|
| Assign a connection using a dedicated endpoint when another assigned connection uses that FQDN | Rejected |
| Assign multiple connections with a shared endpoint using that FQDN | Permitted |
| Update a connection using dedicated endpoint routing to shared endpoint routing | Permitted, including when a connection with a dedicated endpoint uses that FQDN |
| Change a connection’s traffic routing method to Dedicated endpoint when another assigned connection uses the same FQDN | Rejected |
| Change connection hostnames so that the update introduces a conflict | Rejected |
In API and SDK configurations, the corresponding routing values are DEDICATED_ENDPOINT and SHARED_DEPLOYMENT_ENDPOINT. See the connection reference for more information.
Why is this validation needed?
A connection using a dedicated endpoint has its own network infrastructure. When conflicting connections use the same FQDN within a deployment, traffic can use a different connection’s network path. The originating ingress IPs can therefore be unpredictable, and the intended dedicated path may remain unused.
This validation prevents assignments and updates that would create this ambiguity.
Different port numbers do not remove an FQDN conflict. For example, two dedicated connections using db.example.com still share the same FQDN even if they specify different ports.
Check whether your configuration is affected
Review the deployment’s assigned connections and identify any repeated FQDNs involving dedicated endpoint routing.
Compare the hostnames in the connection settings, including each hostname in connection strings or server lists. Different connection names, database service names, or ports do not establish that the FQDNs are different.
For existing overlapping connection assignments, assess the configuration before removing or recreating an assignment. Reassignment is subject to validation and can be rejected if the conflict remains.
Prepare for shared endpoint routing
Where the network design permits it, migrate conflicting dedicated endpoint connections to shared endpoint routing.
Shared connections use the assigned deployment’s private endpoint and ingress IPs and inherit the deployment’s network security group settings. Before changing the routing method, verify that:
- The deployment’s subnet can resolve and reach the source or target.
- Network routes and security rules permit the required traffic.
- Source or target access controls allow the deployment’s ingress IPs.
A dedicated endpoint connection can use a subnet in a different VCN from the deployment. Connectivity through its existing path therefore does not prove that shared endpoint routing will work. See OCI GoldenGate connectivity for more information.
If the connection is assigned to multiple deployments, review each deployment’s connectivity before changing it. Plan the change around the affected replication workloads.
Update and verify the connection
Make connection changes in the Oracle Cloud Console. Changes synchronize to assigned deployments. Do not edit the connection through the deployment console’s Credentials screen:
- Follow Edit a connection. Set Traffic routing method to Shared endpoint, and save the changes.
- After the update completes, follow Test connections for each assigned deployment.
- Check the affected Extracts and Replicats and confirm that replication is progressing normally.
Connection changes synchronize to assigned deployments. Do not edit the connection through the deployment console’s Credentials screen. See Manage connections for more details.
After the update is completed, run Test connection from the deployment’s Assigned connections list. Then check the affected Extracts and Replicats and confirm that replication is progressing successfully.
If dedicated endpoint routing remains necessary, review the conflicting endpoint configuration before retrying the assignment. Changing a port or connection display name does not resolve the FQDN restriction.
For more information on how to peer VCNs when the deployment’s subnet and conflicting dedicated connection’s subnet are in different VCNs, see Local VCN Peering using Local Peering Gateways.