By Eldred Smikle
August 3rd, 2011
A few months and many migrations later, I have thoughts, discoveries, and a two-part question about the Hyperion 220.127.116.11 migration.
Thoughts and Discoveries
I am happy to report that the release documentation continues to impress. And believe me, good documentation goes a long way to making migrations run smoothly.
Another nice surprise in 18.104.22.168 is High Availability. Oracle has made some nice changes from 22.214.171.124 in 126.96.36.199.
In previous versions, High Availability used to be restricted by number of database connections, specifically, Reporting and Analysis had this limitation. This is no longer the case in 188.8.131.52. In the new release you can have multiple database connections for Reporting and Analysis.
The 184.108.40.206 upgrade also allows for true failover. That said, I did encounter one minor problem to note in multiple database connections: The Reporting and Analysis Framework GSM service seemed to improperly register in the Shared Services registry. I am currently working with Oracle support to clarify what is happening. Regardless, while the High Availability function is not quite seamless, the good news is Oracle has definitely brought it a long way, which should make the folks working with the new release very happy.
The Problem Outlined
Before I ask the two-part 220.127.116.11 question, I want to outline the problem:
When doing the prescribed 18.104.22.168 migration it appears that hssmigrate utility omits two key pieces of Shared Services functionality.
Provisioning: Essbase provisioning is something that I fully expected to come over from previous versions. It doesn’t.
Reporting and Analysis: Reporting and Analysis provisioning does not work properly either and currently, the only available workaround is to re-provision all reports manually. This could be quite a bit of work, particularly for companies that work with a large number of reports.
The Essbase and Reports and Analysis provisioning is major and there is no straightforward resolution. We did try testing with LCM (Lifecycle Management) but this is also very time consuming approach.
We are working with Oracle support, but have not been offered a viable solution other than LCM, which we have already discovered is no better than manual.
The big question is: Have any of you run into this migration problem and if so, have you found a reasonable workaround? If you can answer yes to either part of this question, please drop me a note.
At this juncture, I don’t have any workaround and/or resolutions to offer for these not so minor Provisioning and Reporting and Analysis problems. When I have more information, I’ll post it here.