Forum Discussion
Oracle connection error
ORA-12154 typically indicates that Oracle cannot resolve the service name, TNS alias, or connection identifier being used, rather than an issue with the username or password. Even if the gateway is up to date and the credentials are correct, Power BI and the gateway must be able to resolve the Oracle alias specified in the connection string.
A few things to check:
- Verify that the server/database value in the Power BI data source exactly matches an entry in the tnsnames.ora file.
- Confirm that the Oracle client and gateway are using the same tnsnames.ora file and Oracle Home.
- If you're using a TNS alias, test the connection directly from the gateway server using SQL*Plus or another Oracle tool.
- Consider using an EZConnect string (for example, host:port/service_name) instead of a TNS alias if your environment supports it.
- After making any changes, restart the On-premises Data Gateway service and try updating the credentials again.
Since the error specifically says it cannot find the alias in DataSources or EZConnect, I would focus on validating the Oracle network configuration and TNS name resolution on the gateway machine rather than the Power BI credentials themselves.
Resolver IIORA-12154 typically indicates that Oracle cannot resolve the service name, TNS alias, or connection identifier being used, rather than an issue with the username or password. Even if the gateway is up to date and the credentials are correct, Power BI and the gateway must be able to resolve the Oracle alias specified in the connection string.
A few things to check:
- Verify that the server/database value in the Power BI data source exactly matches an entry in the tnsnames.ora file.
- Confirm that the Oracle client and gateway are using the same tnsnames.ora file and Oracle Home.
- If you're using a TNS alias, test the connection directly from the gateway server using SQL*Plus or another Oracle tool.
- Consider using an EZConnect string (for example, host:port/service_name) instead of a TNS alias if your environment supports it.
- After making any changes, restart the On-premises Data Gateway service and try updating the credentials again.
Since the error specifically says it cannot find the alias in DataSources or EZConnect, I would focus on validating the Oracle network configuration and TNS name resolution on the gateway machine rather than the Power BI credentials themselves.