220.127.116.11 has been out for a few months now, and we’ve had several clients with whom we have worked to perform upgrade-in-place of their 18.104.22.168 environments. Thus far, the process has been far less problematic than the previous upgrades from 22.214.171.124 to 126.96.36.199. It appears Oracle has done a great deal of work making the process more seamless and less perilous.
The upgrade process for environments with HFM, FDM and Financial Reporting does have an interesting change from previous installations. The installTool will not allow you to upgrade HFM or FR if your default DCOM settings are not correct. However it does not explicitly point out that it is not upgrading those pieces. You must expand and verify every item on your product list that says ‘188.8.131.52 Installed’. If they’re not all checked, you should see an explanation why it is not checked when you select the item in question. In this case, the installer warned that the default DCOM settings were not correct. Cancel out of the installer, and change the default DCOM setting to “Connect”. Our environment seemed to work properly before the upgrade with the DCOM default set to “None”, however 184.108.40.206 seems to want a non-granular DCOM security setting scheme before allowing you to install.
Once your installation and configuration steps are complete, FDM may have some additional work that needs to be done before it will successfully allow the Load Balance Configuration to proceed. In our case, we received an error, “Unable to create Load Balance Manager object”. We found that the domain username/password needed to be added or modified for the FDM DCOM objects. Due to a peculiarity in the way DCOM picks up changes to these objects, it was necessary to remove provisioning to the objects, including removing the “dots” from the password lines, set it to ‘The Launching User”, and close the object. We were then able to re-open it, add the correct ID/password, and get the Load Balance Configuration to proceed to the next step.
Users of previous versions of FDM will not be surprised by the need to remove/change DCOM users and permissions, but it is a good reminder to be vigilant as Oracle has changed their FDM installation procedures to better fit with their overall Hyperion installation framework. Review the documentation from the previous installation, as well as the READMEs from the 220.127.116.11 documentation, in case there are other surprises or issues that may have been resolved but forgotten since the last installation.
Author Robert Spelman