Description
This article discusses the error where Fully Managed Oracle CDC connector fails to connect to oracle database and gives error like below.
1. “Could not connect to the database. Please make sure the database connection configuration are correct and the database is accessible by the connector.”
2. “Could not connect to database. Please make sure the database connection configuration are correct and the database is accessible by the connector.”
3. “Could not connect to the database: 'ORA-01017: invalid username/password; logon denied'. Please make sure the database user credentials are valid.“
4. “Could not connect to the database: 'ORA-12528, TNS:listener: all appropriate instances are blocking new connections'. The connector will continue to retry but if the error persists then please contact the database administrator to check the status of the instances.”
Applies To
Oracle CDC source Connector
Confluent Cloud
Cause
These errors are mostly due to incorrect mode of database startup or incorrect use of connection string in the connector configuration. Incorrect connection details can lead to authentication errors.
Resolution
To resolve this error, we should be more careful about the connection string and use the correct connection details. Here are a few things that you may pay attention to.
-
Verify Credentials: Double-check that you are using the correct username and password. Ensure there are no typos and that the credentials match those configured in the database.
-
Check Case Sensitivity: Oracle usernames and passwords are case-sensitive. Make sure you are entering them exactly as configured.
-
Database Access: Ensure that the user has the necessary permissions to log in to the database. Sometimes, users might be locked out or their accounts may be expired.
-
- Create and configure your Oracle database system in Oracle Cloud Infrastructure (OCI).
- Ensure ports like 22 (SSH) and 1521 (SQL*Net) are open.
- Create the multitenant database system and the required tnsnames.ora configurations for your Oracle listener.
Connection String: Verify that the connection string you are using is correct, including the service name, host, port, and SID. If the database is a pluggable database, use the correct service name to make connection to the correct pluggable database. While setting up multitenant Oracle Database in OCI.
- Networking Considerations : In case if private networking is required for fully-managed connectors, make sure to set up the proper networking beforehand. Depending on service environment, there my exist some network access limitations. You may want to have PrivateLink, VPC (Virtual Private Cloud) Peering, or configuring private DNS records to ensure the connector can reach the required Oracle database. For details, refer Manage Networking for Confluent Cloud Connectors.
- Public egress IP address are used to securely establish outbound connections to endpoints of external data sources and sink over the secure public endpoints. To use a set of public egress IP addresses, visit Public Egress IP Addresses for Confluent Cloud Connectors.
- For private networking connectivity IP address details, refer to Egress IP address ranges.
- Refer this blog discussing on How to Securely Connect Confluent Cloud with Services on Amazon Web Services (AWS), Azure, and Google Cloud Platform (GCP)