Verify the tnsnames connect descriptor. Confirm the listener and port are reachable. Install the Oracle client on the gateway and test in Power BI Desktop.

Where does this Power BI refresh error appear?

It appears in a Power BI semantic model's refresh history when a scheduled or on-demand refresh fails.

Connectivity

Oracle TNS error (ORA-12154 / ORA-12514 / ORA-12541)

Power BI dataset refresh error: what it means and how to fix it.

What this means

Oracle TNS errors (ORA-12154/12514/12541/12170/12504): a bad connect identifier, or the listener/port is down or firewalled.

How to fix it

Verify the tnsnames connect descriptor.
Confirm the listener and port are reachable.
Install the Oracle client on the gateway and test in Power BI Desktop.

View on Microsoft Learn

Frequently asked questions

What does the "Oracle TNS error (ORA-12154 / ORA-12514 / ORA-12541)" error mean?: Oracle TNS errors (ORA-12154/12514/12541/12170/12504): a bad connect identifier, or the listener/port is down or firewalled.
How do I fix it?: Verify the tnsnames connect descriptor. Confirm the listener and port are reachable. Install the Oracle client on the gateway and test in Power BI Desktop.
Where does this Power BI refresh error appear?: It appears in a Power BI semantic model's refresh history when a scheduled or on-demand refresh fails.

Related connectivity errors

Catch this automatically

RefreshRadar monitors every Power BI dataset refresh and emails you when one fails, with the likely cause and the fix, so you are not hearing about a broken refresh from your stakeholders first.

See a live board, no login Start free