The Boucher Group Knowledge Base
My Backup Brain

How to Connect Microsoft Report Builder to Oracle (Fix ORACLE Data Extension Error)

Craig Boucher .Net, Microsoft Report Builder, Oracle, PeopleSoft April 30, 2026

If you’re trying to connect Microsoft Report Builder to an Oracle database and you hit this error:

The selected data extension ORACLE is not installed or cannot be loaded

you’re not dealing with a query problem or a bad connection string.

This is a missing or misconfigured Oracle provider problem. Report Builder literally cannot load the Oracle driver it needs.

Here’s how to fix it properly.

Why This Error Happens

Microsoft Report Builder does not include native Oracle connectivity out of the box.

It depends on Oracle’s ODP.NET (Oracle Data Provider for .NET). If that provider is:

  • not installed
  • installed with the wrong bitness (32-bit vs 64-bit)
  • not registered correctly

you’ll get this exact error.

Important: Check Your Report Builder Version

This matters more than anything else.

  • Report Builder 15.1.20318.47 and newer → requires 64-bit Oracle client
  • Older versions → require 32-bit

If you install the wrong one, it will never work.

Step 1 – Install the Correct Oracle Client

For modern Report Builder (15.x):

👉 Install the following (64-bit):

For the scripts below to work, install into c:\oracle64.

If you have a c:\tnsnames folder from doing .Net development, point the config to this folder during installation.

Step 2 – Register ODP.NET (Critical Step)

This is the step most people miss.

Installing ODAC is not enough. You must register the managed provider so Report Builder can see it.

Open an elevated Command Prompt (Run as Administrator) and run:

C:\oracle64\odp.net\bin\4\OraProvCfg.exe /action:gac /providerpath:C:\oracle64\odp.net\managed\common\Oracle.ManagedDataAccess.dll

C:\oracle64\odp.net\bin\4\OraProvCfg.exe /action:config /force /product:odpm /frameworkversion:v4.0.30319 /providerpath:C:\oracle64\odp.net\managed\common\Oracle.ManagedDataAccess.dll

Notes:

  • Adjust the path if you installed to a different directory
  • If you used OCMT, it may already be configured—but verify

Step 3 – Restart Report Builder

Close and reopen Report Builder after installation and registration.

Step 4 – Test Your Data Source

Now create your data source:

  • Type: Oracle
  • Connection string example: Data Source=YourTNSName;

If everything is set up correctly, the error will be gone.

Common Pitfalls

❌ Installing 32-bit Oracle client on a 64-bit Report Builder

This is the #1 mistake. It will fail every time.

❌ Skipping the OraProvCfg step

Without this, the provider is not registered and cannot be loaded.

❌ Confusing this with a TNS or connection issue

If the provider loads but the connection fails, that’s a different problem.

This error happens before any connection attempt is made.

❌ Forgetting the Report Server

If you publish the report to SSRS:

  • You must install and configure Oracle on the server as well
  • Same rules apply (bitness + registration)

Summary

To fix the error:

  1. Install 64-bit ODAC / ODP.NET (18c or newer)
  2. Run OraProvCfg.exe to register the provider
  3. Restart Report Builder

That’s it. Once the provider is properly installed and registered, Report Builder will recognize Oracle without issue.

Final Thoughts

Microsoft didn’t bundle Oracle support, and Oracle didn’t make the setup simple. You have to bridge the gap yourself.

Once you understand that this is a provider problem—not a SQL problem, the fix is straightforward and repeatable.

About: Craig Boucher