Now with this new release there are more options to move to it, you can upgrade/migrate from previous versions, fresh install or apply the maintenance patch to upgrade 11.1.2 to 220.127.116.11, some of this options I will be covering in future blogs.
This release is also about bug fixes as masses have been addressed, there are a number enhancements and new features in a selection of the products but nothing ground breaking (you may disagree), it looks like planning has a larg share of them.
As in past blogs I have gone through the installation and maintenance patches for previous releases so I thought I might as well share my experience of apply the maintenance release today. The release has only been around for a few days so I apologise if I provide any incorrect information.
The OS the maintenance release is being applied to is windows 2008 x64 SP2.
If you are intending of applying the maintenance release I recommend having a read of the “Installation and Configuration Guide” as it covers important detailed information
Next step is download all the required files, I usually obtain them from Oracle edelivery, the files that are required are covered in the install and config guide, note this release there are seven foundation files and not four, also don’t forget the additional content file.
Once you have all the files then extract them all to the same location (if you have the install files in a folder from the previous release 11.1.2 make sure you extract to a different folder), if you are installing on a distributed environment make sure you extract the necessary files on each machine and take note of information provided in the config guide, for instance
- On the machine on which you plan to administer the WebLogic Server, you must install all Web applications for all applications you plan to deploy on any machine in the environment. (The WebLogic Administration Server is installed and deployed on the Foundation Services machine.)
There are a number of extra folders at root level in this release.
Now there is a list of prerequisites to be met before installing the Maintenance Release to move from 11.1.2 to 18.104.22.168, here is a summary of the main points.
• You must apply the maintenance release on top of your existing EPM System installation.
• You must apply the maintenance release to all EPM System products in the deployment. You cannot apply the maintenance release to only some products.
• If you are applying the maintenance release to move from EPM System release 22.214.171.124 to EPM System Release 126.96.36.199, or if you are reinstalling EPM System products, you must first stop all the services for EPM System products.
• If you are applying the maintenance release to move from Essbase Release 11.1.2 to Release 188.8.131.52, you must first export linked reporting object information from the 11.1.2 database, and then delete the linked reporting objects. After applying the maintenance release, import the exported linked reporting objects. More information available here
One more point before starting the installation is to be sure you have more than 5GB spare on the drive where EPM is currently installed, if there is not you will not be able to complete the installation steps.
Once all the prerequisites have been met then start up the installation by executing InstallTool.cmd/sh
A new addition to the start up of the installer is the check whether UAC is enabled, I know this could cause problem with 11.1.2 if it was enabled, if it is enabled in this release a warning will be displayed and the installer will not start up.
There are also a few more prerequisite checks, good news all have been passed.
Nothing new on this screen, displays the current Middleware Home.
Three main options to choose from and this time it is “Apply maintenance release”.
Check that there is a tick in each of the products with “184.108.40.206.0” against them, if there is not then you have not downloaded and extracted all the required files.
Once you click next a list of products to patched will be shown, click next again and the maintenance patching will start up, this is a good point to go and spend time doing something that is actually meaningful in life and then on your return hope the status is all green.
All green, see it wasn’t worth hanging around staring at the screen.
Click the Configure button, when I first installed 11.1.2 the configure button never worked but in this release it actually opened up the configurator.
You have the choice whether to stick with the original instance or create a new one, I have no reason to change this so I kept with the default.
The configurator should have checked all the pending tasks for each product that need configuring, I unchecked everything except foundation as I want to be sure there are no issues with the maintenance release, if there is a problem with foundation there wouldn’t be any point configuring the other products.
Another reason for doing this is I have used a separate Oracle schema for each product database configuration, if you leave everything selected then it wouldn’t give the option to apply to separate schemas.
This is just a personal preference Oracle no doubt recommends to leave all products checked and the choice is yours.
If you choose to only configure foundation then you would have “Configure Web Server” again when you configure the other products, this step should always be done last.
I do notice there is a new option “Setup connection to Oracle BI and Publisher”, it is not checked by default and I am not intending on changing that today.
Keep “connect to a previously configured Shared Services database” selected.
Once again there should be no need to change anything when applying the maintenance patch.
Guess what, kept the defaults, can’t beat just clicking next.
Next one more time for me and then it will configure as I am only configuring foundation
All green again, nice smooth ride up to now.
Right that’s me satisfied, back to the configurator to run through the rest of the pending tasks product by product, remembering to check “Configure Web Server” in foundation as the last step, this may not be necessary as I have already configured the web server but I am not taking any chances.
Instead of selecting uncheck all, I unchecked the products I was not configuring for, this way I knew the product I was configuring had the required tasks checked.
I am not going to paste all the screens because as this is a maintenance release there were no new surprises and the process I followed was to stick with the defaults for each product, it was basically reconfiguring the database and redeploying the web application servers.
What I did notice after installing is the number of services being used by EPMA has now been cut down, originally this is how it looked in 11.1.2
The five non web app related services have been combined into one service called “Hyperion EPMA Server”.
I also noticed after the deployment of the web applications the issue I posted about here has been resolved; the installer’s temporary directory is no longer used.
I went through each product and quickly tested I could access them without problems, understandably this is not a rigourous test but it didn't show up any major issues, I will update this post if I do come across any.
For each planning application I had to log in and upgrade from 11.1.2 to 220.127.116.11
If you are using EPMA then this is taken from the installation readme -
"After the installation and configuration of Enterprise Performance Management Architect 18.104.22.168.000, you must install Enterprise Performance Management Architect patch 11804477"