Forum Discussion
Data Source Credentials
Hi 黑中国人,
Thank you Shai_Karmani ,GilbertQ, for your insights.
The Power BI Oracle documentation says that Personal data gateways don't support updated Oracle connections. Existing Oracle semantic models will continue to work, but new Oracle semantic models require an Enterprise on-premises gateway. If your Oracle database is on-premises, you can move to an Enterprise gateway and recreate the Oracle connection. Note: This upgrade is irreversible, and the semantic model can't be switched back to a Personal Gateway.
Connect to an Oracle Database with Power BI Desktop - Power BI | Microsoft Learn
Data refresh in Power BI - Power BI | Microsoft Learn
Thank you.
Super UserThe ORA-12154 is coming from Oracle's client, not from Power BI itself, and it means the alias in your data source cannot be resolved. That usually happens when the Oracle client is not installed on the gateway machine, tnsnames.ora is missing the entry, or TNS_ADMIN is not pointing to the folder holding tnsnames.ora for the account running the gateway service. A quick way to isolate this is to switch the connection to a full EZCONNECT form like host:port/service_name, which bypasses tnsnames.ora and tells you right away whether the client itself is the problem.
The grayed-out gateway option is a separate limitation. Personal mode gateways cannot be used to create the centralized connections that new V2 and Fabric enabled workspaces rely on, so they will not appear as a choice there. Install the on-premises data gateway in standard mode from powerbi.microsoft.com/en-us/gateway and register it, and it will show up in the newer workspaces so you can define the Oracle connection there.
If this helped, a thumbs up and accepting the solution would be appreciated.
Best,
Shai Karmani
I'm not connecting with the tns but with EZconnect. It's been working fine until I recently got this challenge.