EPM’s Validate.bat

Validate.bat | sh has been around a long time in EPM. One interesting bit of behavior with this tool is that after an upgrade-in-place, from say 11.2.5 to 11.2.8, Validate may not run against all your installed products on a server.

Briefly, after a successful upgrade-in-place, EPM resets the icons in your Configtool display to “Pending” for all products. In an 11.2.5, .6 or .7 upgrade-in-place, you may not be required to re-deploy your Java Web applications.

As you can see above, all the products’ main categories like Hyperion Foundation and Essbase are showing as “Pending” configuration. It is important to note that at this point, the 11.2.8 Validate utility works fine and displays results of tests run against ALL configured products! It is only if we run Configtool to redeploy one or more of the web apps that we begin to see issues.

After an upgrade-in-place again it is not necessary to re-deploy, but as I was tracking down another issue, I did re-deploy one application server, the Provider Services app server.

I’ve ran the Validate tool, redacted the output to protect the innocent, and only see a single product, Provider Services, was tested!

If I were to go to each of the other products and re-deploy, or hack the EPM registry to show those products as deployed, I would see those products tested in the output of Validate. I will leave this environment unchanged from above and see what happens when I conclude my upgrade process with patching to 11.2.14 later this month.