Unable to connect oracle autonomous database to on-premises gateway

[jh1233]

Hello,

I was able to connect my database on the desktop app and import the necessary tables. However, I have been unable to connect my on-premises gateway to the database. Because of this, when I publish my report all the data goes away. This is the error message I get when trying to connect on the website:

Unable to create connection for the following reason: Unable to connect to the data source. Either the data source is inaccessible, a connection timeout occurred, or the data source credentials are invalid. Please verify the data source configuration and contact a data source administrator to troubleshoot this issue.

Details: PowerBI Gateway: Oracle: ORA-12154: TNS:could not resolve the connect identifier specified

Thanks for any help resolving this problem.

[v-zhangti · Accepted solution]

Hi, @jh1233 

The error message suggests that the On-premises data gateway is unable to resolve the connect identifier specified for the data source. This could be due to a number of reasons such as incorrect configuration settings, network connectivity issues, or incorrect credentials. You can try the following steps to troubleshoot the issue:

1. Check the configuration settings of the On-premises data gateway and ensure that they are correct. Make sure that the data source is configured correctly and that the credentials are valid.

2. Check the network connectivity between the On-premises data gateway and the data source. Ensure that the network connection is stable and there are no network issues.

3. Check the firewall settings on the On-premises data gateway and ensure that the required ports are open.

4. Check the TNSNames.ora file on the On-premises data gateway and ensure that the connect identifier specified for the data source is correct.

5. Restart the On-premises data gateway and try to connect again.

Note that ORA-12154 error is related to the Oracle client not being able to resolve the connect identifier specified. This could be due to incorrect configuration settings or network connectivity issues. 

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.