How to Migrate Oracle EPM and Essbase 21c to SQL Server (Common Issues & Fixes)

One of our partners had a requirement to move their EPM databases, including Essbase 21c, to another MS SQL Server host. We were able to follow the normal procedures to update the server names in the EPM Registry and in WebLogic, but there were a couple of added wrinkles.


First, we were forced to use a HOSTS file on the EPM server to point to the old and the new MS SQL server hostnames. There was some configuration in WebLogic, either in the tables created by RCU or elsewhere in the WL deployment, which would not lose the address of the ‘old’ MS SQL server. We had changed the database server names in all the normal locations in WL and in the deployment files, but could not find the offending entry. The behavior we observed was that WebLogic would try to read from the ‘old’ server, fail because we had taken those databases offline, then move on to the ‘new’ server and successfully read the RCU database information from there.

Our second issue was user-related. We had copied the databases and users over from the old server, but had to take additional steps before those users were able to be logged in. The RCU Schema Users came over disabled, so we re-enabled them and re-entered their passwords for safety’s sake. We encountered another error that indicated the MS SQL SID – a unique identifier tied to the source server – had been transferred for each user we had copied. The result was each user looked correct but we’d get errors indicating the user could not be logged in to. The fix was to force an ALTER USER statement for each user to overwrite the original server’s SID in the user configuration with the new server’s SID.

USE [your database name];

ALTER USER [RCUSchemaUser here] WITH LOGIN = [your RCUSchemaUser again];

GO

 Remember your RCU Schema Users aren’t just the ones created for EPM’s WebLogic instance, they’re also the ones for ESSBASE’S WebLogic instance. Make sure you get them all!

Migrating Oracle EPM and Essbase environments, especially when involving infrastructure changes like SQL Server migrations, often comes with unexpected challenges that go beyond standard documentation. From WebLogic configuration quirks to user authentication issues, having the right expertise can make the difference between a smooth transition and prolonged downtime.

At iArch Solutions, we specialize in helping organizations navigate complex EPM migrations, optimize system performance, and resolve the kinds of issues that aren’t always obvious. If you are planning a migration or running into roadblocks, our team is here to help.

Schedule a discovery call today to discuss your environment and how we can support your success.

Next
Next

How to Fix Slow Planning Refreshes in Oracle EPM 11.2 with Essbase 21c