With the release of Oracle EPM 11.2.25, Oracle Essbase is upgraded to version 21.8.1 which introduces an important change: the DataDirect SQL Server driver is updated from version 7.x to 8.x.
However, if you are using Microsoft SQL Server for Oracle Essbase repositories, this driver update is not fully automated and requires manual configuration.
This post walks through the required steps, including a key fix not covered in the official documentation.
📘 Reference Documentation
Be sure to review the official EPM 11.2.25 Readme:
EPM 11.2.15 – Readme
Relevant sections:
- End of page 14
- Pages 15–16
These outline the driver upgrade process from 7.x → 8.0.2.
- Backup Existing Registry Settings
Before making any changes, export your current ODBC configuration.
Export ODBC.INI
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
- Right-click ODBC.INI
- Select Export
- Save as:
- odbc.orig.reg
Export ODBCINST.INI
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI
- Right-click ODBCINST.INI
- Select Export
- Save as:
- odbcini.orig.reg
![]()
- Update Registry Driver References
Update Data Source Driver
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\essbase_datasource
Modify the following entries:
- Driver .dll
- Description
Change:
Oracle 7.1 SQL Server Wire Protocol
![]()
To:
Oracle 8.0 SQL Server Wire Protocol
![]()
Update the driver DLL:
arsqls27.dll → arsqls28.dll
Update ODBC Data Sources Entry
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources
Update:
essbase_datasource
Change:
Oracle 7.1 SQL Server Wire Protocol
![]()
To:
Oracle 8.0 SQL Server Wire Protocol
![]()
- Apply DataDirect 8.0.2 Driver Registry Entries
On the Essbase server, navigate to:
..\Oracle\Middleware\essbase\modules\oracle.essbase.datadirect.odbc\8.0.2
Backup the File
ODBC802.reg → ODBC802_orig.reg
![]()
Edit the Registry File
Replace all occurrences of:
$ODBC_PATH
With your absolute path, for example:
E:\Oracle\Middleware\essbase\modules\oracle.essbase.datadirect.odbc E:\Oracle\Middleware\essbase\modules\oracle.essbase.datadirect.odbc\8.0.2\Drivers
![]()
Apply the File
- Double-click the edited ODBC802.reg
- This registers all DataDirect 8.0.2 drivers
![]()
Verify Installation
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Oracle 8.0 SQL Server Wire Protocol
![]()
Looks good, here’s an example of it updating the Oracle driver:
![]()
- Known Issue: Essbase Fails to Start
![]()
![]()
Attempt to connect to database failed with error [[Oracle DataDirect][ODBC SQL Server Wire Protocol driver]The value specified (E:\Oracle\Middleware\oracle_common\..\essbase\modules\oracle.essbase.datadirect.odbc\8.0.2\Drivers\arsqls28.dll) for connect option 'DRIVER' is disallowed. Please check the user]
The value specified (…) for connect option ‘DRIVER’ is disallowed.
Fatal Error: Server aborting
Problematic Path Example
E:\Oracle\Middleware\oracle_common\..\essbase\modules\oracle.essbase.datadirect.odbc\8.0.2
Although using \\..\\ should resolve to:
E:\Oracle\Middleware\essbase\modules\oracle.essbase.datadirect.odbc\8.0.2
⚠️ In practice, this path does NOT resolve correctly, leading to driver load failures.
See the link below in Oracle Communities, there are a few replies to show that this has affected some of the 11.1.2.25 upgraders:
unable to start Essbase applications after EPM 11.2.25 release update — oracle-mosc
- Critical Fix (Missing from Readme)
The official steps do not update all required registry paths.
You must manually correct remaining entries.
Fix Driver Path in Registry
Check:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\essbase_datasource HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC
Update the Driver path to use a fully resolved absolute path:
![]()
![]()
✅ Correct:
E:\Oracle\Middleware\essbase\modules\oracle.essbase.datadirect.odbc\8.0.2\Drivers\arsqls28.dll
✅ Final Step: Restart Essbase
After correcting all paths:
- Restart services
Start Essbase applications
You should now see a successful startup with the updated 8.0 driver.
🎯 Summary
- EPM 11.2.25 upgrades Essbase → 21.8.1
- DataDirect driver moves from 7.x → 8.0.2
- Registry updates are partially manual
- Key issue: relative paths (..) break driver resolution
- Fix: enforce absolute paths in all registry entries
Done and dusted ✅
Until Next time
Ben


