Can't connect to Oracle 19 through on prem gateway

[lanman1]

We have the 3000.89.6 version of the on prem gateway and are trying to connect to oracle using the 64bit 19.3 ODAC and get the following message when trying to add the datasource.

The provider being used is deprecated: 'System.Data.OracleClient requires Oracle client software version 8.1.7 or greater.'

We have followed the instructions in the git at Oracle ODAC 18 is supported with additional steps · Issue #2147 · MicrosoftDocs/powerbi-docs · GitHu... and made sure there was no space between the colon in the .NET version.  Any help would be appreciated.

We are able to successfully connect from Power BI Desktop installed on the gateway server.  The OS is x64, the gateway services should be x64 as well, correct?

[lanman1]

As further information, it does appear as we have the ODAC components registered properly.  We're at a loss as to where to go next.  

ODP.NET, Unmanaged Driver Oracle Data Provider for .NET, Unmanaged Driver Oracle.DataAccess.Client Oracle.DataAcces...

[v-easonf-msft]

Hi,  @lanman1 

If OS is x64, the gateway services should be x64 as well.

After completing these configurations, have you restarted the gateway service?

Hope these related document could help:

Desktop-connect-oracle-database 

service-gateway-onprem-manage-oracle 

Best Regards,
Community Support Team _ Eason

[lanman1]

Thank you for the reply and your input.  Yes, we did restart the gateway service boith with the gateway applucation interface and the OS services.  We also restarted the server multiple times.  We did use those links to get where we are but even though the PowerBI desktop works and Powershell shows the ODAC as registered, the gateway still reports an incorrect version.   

[v-easonf-msft]

Hi, @lanman1 

If you still have no idea about your problem, you can open a support ticket with MSFT to seek technical support , usually they will have better suggestions.

Best Regards,
Community Support Team _ Eason

[lanman1]

I have.  Their solution is to switch to ODBC.  I have asked for any information tracking this issue.

[amoren]

Did you ever get this resolved without resorting to ODBC?