getting "oracle.dataaccess.client",

[EmadBsb_1]

Dear all,

I am a beginner in using Power BI Tool

i have a problem in connecting to an Oracle Database

i have Oracle Database version 9.2.0.1.0  installed on windows server 2003

i installed Power BI Desktop tool version 64x on my PC which is also 64x

when pressing home>get data> more > Oracle Database

it gives me that error

"The recommended provider ('Oracle.DataAccess.Client') is not installed. You can continue with your current provider, however it has been deprecated and may not work properly."

so what i can do exactly

what is wrong

please explain in details as i am still beginner

Thanks

[amitchandak]

You need to install the oracle client.

Refer

https://docs.microsoft.com/en-us/power-bi/desktop-connect-oracle-database

This is the client.

https://www.oracle.com/database/technologies/odac-downloads.html

After installing, please make sure you Add Path in the environment variable path, otherwise you will keep on getting this error.

These are my locations, Change as per need

[EmadBsb_1]

i don't know which version should i install

from that link

https://www.oracle.com/database/technologies/odac-downloads.html

also should I install this on my PC (the host of Power BI Desktop) or on the server side

Thanks

[Icey]

Hi @EmadBsb_1 ,

Here are some posts may help you:

Unable to Install Oracle Client for use in Power BI desktop;

Installing Oracle Client.

Best Regards,

Icey

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

[Anonymous]

These guys/gals are sending you on a wild goose chase as this fixes the general issue people have with this error.

Your problem is a bit different. Oracle Database versions below 10 are not compatible with the the minimum version instant client MS checks for.

That's not to say that there aren't work arounds to make it work. In fact, I have gotten it to work by installing both clients and copying the old driver file into the newer instant client folder but renaming it to match the current version. This is completely a Your Mileage May Vary thing, and I don't condone this method of driver tomfoolery - but it has worked for me in the past when trying to maintain compatability after database upgrades.