Our Development Train is Off the Tracks. Now What? (Part One)

About the Environment

Our organization is relatively new to the Hyperion world and we are still figuring out how all the dials and levers work. Our implementation consists of two environments -- one for development/experimentation and one for production. We are running version 11.1.2.1 of Hyperion on Windows 2008 servers as the Essbase hosts, accessing Oracle RDBMS on Linux servers for the relational components of Hyperion.

It All Goes Wrong

A while back I wanted to create a new application in our development environment to do some experimentation. I made a crucial mistake when establishing the data source that has caused our development environment to be broken ever since. I did not realize that each data source must have a unique schema in the Oracle repository. "Sharing" a schema (user) with another application will hopelessly confuse Hyperion and all sorts of erratic behavior will result!

And so, having clobbered the development repository, I have been trying several different actions to recover the environment. Being a non-production environment, we do not have regularly-scheduled backups for me to roll back to. Not knowing I was clobbering anything with this data source setup step, I also did not initiate a backup. And so, here I sit, with a broken-down environment. Woe is me.

Up Next

In part two of this saga, I'll delve a little into what has been done so far to try to recover from this mess.