The provider being used is deprecated

[matteol_isp]

Hi all,

We have just upgraded our SSAS instances to 2022 version. After the upgrade, we started to get the following error on our models (compatibility level 1400) with Oracle connections already deployed before the upgrade.

Failed to save modifications to the server. Error returned: 'Errore OLE DB o ODBC: [DataSource.Error] Si è verificato un errore durante la lettura dei dati dal provider: 'Il provider in uso è deprecato: 'System.Data.OracleClient'. Per installare il provider supportato, vedere https://go.microsoft.com/fwlink/p/?LinkID=272376.'.

Does anyone know which is the issue? I already read some similar posts on the blog and the reason could be an older and not supported version of the Oracle client installed on SSAS server. However, the error doesn't specify a specific version needed in order to get the connection to Oracle databases. Then, we don't always get this error. Some times we get it, other times not (with a sort of casuality).

Thanks.

[AnalyticPulse · Accepted solution]

To resolve this issue, you should consider upgrading to a supported Oracle provider. The error message provides a link that you can follow to find the supported provider. In this case, the link is:

https://go.microsoft.com/fwlink/p/?LinkID=272376

Additionally, here are a few steps you can take to troubleshoot and resolve the issue:

1. Oracle Client Version: Ensure that you have a compatible and supported version of the Oracle client installed on your SSAS server. Check the documentation for your SSAS version to find the recommended Oracle client version.

2. SSAS Compatibility Level: Make sure that your SSAS database compatibility level is appropriate for the version you have upgraded to (in this case, SSAS 2022). It's possible that there are compatibility issues if the database is still using an older compatibility level.

3. Intermittent Error: If the error is intermittent, it might be related to specific queries or data loads. Check if there's a pattern to when the error occurs. You may need to investigate the queries causing the issue and the data being processed during those times.

4. SSAS Logs: Examine SSAS logs for more detailed error information. This can provide additional context about the nature of the error and help in troubleshooting.

If this helped, Subscribe AnalyticPulse on YouTube for future updates:
https://www.youtube.com/@AnalyticPulse
https://instagram.com/analytic_pulse
https://analyticpulse.blogspot.com/

subscribe to Youtube channel For fun facts:
https://www.youtube.com/@CogniJourney