Essbase Error (1053025) – SOLVED!

Just hours before production was to open on my ASO cube, I got the dreaded error from January – 1053025.  I was going into a mild (to put it mildly) panic attack because of all the work that has been done since December.  Minutes before I was to click “Send” to submit an Oracle SR, I realized the issue.

To reiterate, the error I got in EPMA was:

Error.
Failed to deploy Essbase cube.
Caused by: Failed to build Essbase cube dimension: (Scenario) .
Caused by: Cannot put olap file object. Essbase Error(1053025): Object [Scenario] already exists and is not locked by user [Sarah.Zumbrum@Domain]
Failed to deploy Essbase cube.
Caused by: Failed to build Essbase cube dimension: (Scenario) .

Caused by: Cannot put olap file object. Essbase Error(1053025): Object [Scenario] already exists and is not locked by user [Sarah.Zumbrum@Domain]

As I was going through all I had tried (and what failed) for Oracle, it hit me.  Since it stated that an object was locked, it had to be something with EAS.  And since EAS is driven from Essbase Studio in EPMA, it had to be something used by Studio to EAS.  Scenario is a dimension.  It had to be the Scenario load rule in EAS used by Studio.  So, I went to EAS and unlocked the stuck load rule…and it all works now.  
Seems as if Essbase Studio is not too good at closing its connections to Essbase after updating…

One comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s