Process Tabular model

[S_S_A]

I am having trouble to connect Analysis services to Oracle database. The issue comes in when a Tabular model is being processed from SSMS. I installed Oracle 19C client as well as CODAC64 on the AS server. Any ideas will be appreciated. If anyone has the correct setup to share will it help a lot.

[Ritaf1983 · Accepted solution]

Hi @S_S_A 

Short answer: Processing happens on the SSAS server, not on your SSMS box. The Oracle client and networking files must be correctly installed and visible to the SSAS service account on the AS server.

Checklist to fix:

Install Oracle client x64 on the SSAS server

Use Oracle 19c Instant Client (Basic + SDK) or full client, x64.

Version can be 19c even if the DB is older.

Set system PATH (server-wide)

Put the Oracle client bin folder first, e.g.
C:\oracle\instantclient_19_22

Restart the SQL Server Analysis Services service after changing PATH.

TNS or EZCONNECT

If you use TNS, place tnsnames.ora under a folder pointed by TNS_ADMIN
and make sure the SSAS service account can read it.

Example tnsnames.ora entry:

ORCLPDB =
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=yourhost)(PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=orclpdb)))

Or use EZCONNECT in the data source:

//yourhost:1521/orclpdb

Credential/impersonation in the Tabular model

In the model’s data source set Impersonation to stored username/password
or Service Account, and test with that account.

Ensure the DB user has permissions to the queried schemas.

Provider selection

For Tabular 2017+ (M engine), the Oracle Database connector requires
Oracle client libraries on the server. No OLE DB needed.

If using legacy OLE DB, install the matching x64 provider and reference it
explicitly.

Networking

Open port 1521 (or your listener port) from the SSAS server to Oracle.

Validate with:

tnsping ORCLPDB

from the SSAS server under the SSAS service account.

Common pitfalls

Installing the Oracle client only on the admin/SSMS machine.

PATH set for your user but not for the system.

tnsnames.ora under your profile instead of a folder readable by the
service account.

Forgetting to restart the SSAS service after client install.

If it still fails

Share the exact error text and your connection string.

State which account SSAS runs under, and the output of tnsping.

Confirm Oracle client path and TNS_ADMIN location.

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

[v-kpoloju-msft · Accepted solution]

Hi @S_S_A,

Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to @Ritaf1983, @Thomaslleblanc, for those inputs on this thread.

I understand you are having trouble processing your SSAS Tabular model that connects to an Oracle database, even after installing the Oracle 19c client and ODAC 64-bit. This usually happens due to provider setup or permission issues.

Install & verify drivers: Make sure the 64-bit Oracle client and Oracle Data Provider for .NET (ODP.NET) are installed and registered. The Oracle client’s bin folder should appear first in your system PATH variable. Confirm that the provider Oracle.DataAccess.Client (or managed version) is visible when editing the data source.
https://learn.microsoft.com/en-us/analysis-services/tabular-models/data-sources-supported-ssas-tabul... 

Check SSAS service account: Ensure the SSAS service account (or impersonation account) can connect to Oracle and resolve the TNS service name. You can test this using SQL*Plus or Oracle SQL Developer on the same server.
https://learn.microsoft.com/en-us/sql/reporting-services/report-data/oracle-connection-type-ssrs?vie... 

Validate connection settings: Use a correct Oracle connection string like hostname:1521/servicename. If using structured data sources, consider enabling the managed provider by setting MDataEngine\UseManagedOracleProvider = true.

After these steps, re-process your model from SSMS. If it still fails, please share the exact error message that will help identify whether it’s a driver or authentication issue.

Thank you for using the Microsoft Fabric Community Forum.

[v-kpoloju-msft]

Hi @S_S_A,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

[v-kpoloju-msft]

Hi @S_S_A,

Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

Thank you.

[Ritaf1983 · Accepted solution]

Hi @S_S_A 

Short answer: Processing happens on the SSAS server, not on your SSMS box. The Oracle client and networking files must be correctly installed and visible to the SSAS service account on the AS server.

Checklist to fix:

Install Oracle client x64 on the SSAS server

Use Oracle 19c Instant Client (Basic + SDK) or full client, x64.

Version can be 19c even if the DB is older.

Set system PATH (server-wide)

Put the Oracle client bin folder first, e.g.
C:\oracle\instantclient_19_22

Restart the SQL Server Analysis Services service after changing PATH.

TNS or EZCONNECT

If you use TNS, place tnsnames.ora under a folder pointed by TNS_ADMIN
and make sure the SSAS service account can read it.

Example tnsnames.ora entry:

ORCLPDB =
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=yourhost)(PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=orclpdb)))

Or use EZCONNECT in the data source:

//yourhost:1521/orclpdb

Credential/impersonation in the Tabular model

In the model’s data source set Impersonation to stored username/password
or Service Account, and test with that account.

Ensure the DB user has permissions to the queried schemas.

Provider selection

For Tabular 2017+ (M engine), the Oracle Database connector requires
Oracle client libraries on the server. No OLE DB needed.

If using legacy OLE DB, install the matching x64 provider and reference it
explicitly.

Networking

Open port 1521 (or your listener port) from the SSAS server to Oracle.

Validate with:

tnsping ORCLPDB

from the SSAS server under the SSAS service account.

Common pitfalls

Installing the Oracle client only on the admin/SSMS machine.

PATH set for your user but not for the system.

tnsnames.ora under your profile instead of a folder readable by the
service account.

Forgetting to restart the SSAS service after client install.

If it still fails

Share the exact error text and your connection string.

State which account SSAS runs under, and the output of tnsping.

Confirm Oracle client path and TNS_ADMIN location.

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

[Thomaslleblanc]

can you post the errors you are getting?