How to Resolve EPM Validation Tool Failures After Patching to Oracle EPM 11.2.18: A Step-by-Step Guide
One tool I find useful that Oracle provides in the EPM product is the EPM Validation tool. I use it after I do any install/config and after I patch to verify all the components are talking to each other as they should. It’s a good report I can show the client that shows the system is up and working as expected, before I migrate any content in.
After a recent patching update from 11.2.15 to 11.2.18 the EPM validation tool Oracle provides in the %EPM_INSTANCE%\bin directory – validate.bat appeared to fail. After some investigation I was able to figure out the tool was working but it was not sending any output to the report file the tool generates and so it never opened in a browser afterwards. I did a little more digging and I tried to run another type of report, deployment. When I ran the command to generate a deployment report the tool threw an error :
com.hyperion.hit.registry.exceptions.RegistryException: Unable to initialize Deployment Report Processor org/slf4j/LoggerFactory
at com.hyperion.hit.registry.reports.DeploymentReportProcessor.initialize(DeploymentReportProcessor.java:129)
at com.hyperion.hit.registry.regedit.DeploymentReportGenerator.generateDeploymentReport(DeploymentReportGenerator.java:88)
at com.hyperion.hit.registry.regedit.RegEditUtility.main(RegEditUtility.java:362)
Cause: The patching of 11.2.18 deleted the slf4j-log4j.jar file located in D:\Oracle\Middleware\EPMSystem11R1\common\thrift\11.1.2.0\lib
Resolution: Copy the entire D:\Oracle\Middleware\EPMSystem11R1\common\thrift\ directory from a working host to host where validation and deployment reports are failing.
If you are still using an older version of EPM on-premise and want to refresh your ageing servers and infrastructure, now is the time for an upgrade.
Contact us today for help bringing your EPM platform up to date!