EPM troubleshooting Utilities

(in via Maurice)

Are you keeping up-to-date with the latest troubleshooting utilities introduced from EPM These are typically not described in product documentation, so you might miss references to them. The following five utilities may be run from the command line.

(1) Deployment Report was introduced with EPM (11 April 2012).
It details logical web addresses, web servers, application ports, database connections, user directories, database repositories configured for the EPM system, data directories used by EPM system products, instance directories, FMW homes, deployment distory, et cetera.
It also helps to keep you honest about whether you made changes to the system and at what times! Download Shared Services patch 13530721 to get the backported functionality in EPM

Run it from
/Oracle/Middleware/user_projects/epmsystem1/bin/epmsys_registry.sh report deployment
(on Unix/Linux)
\Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat report deployment (on Microsoft Windows).
The output is saved under

(2) Log Analysis has received more "press".
It was released with EPM and helps the user to slice and dice EPM logs. It has many parameters which are documented when run without parameters, when run with the -h parameter, or in the 'Readme' file. It has also been released as a standalone utility for EPM and earlier versions. (Sign in to  My Oracle Support, click the 'Patches & Updates' tab, enter the patch number 17425397, and click the Search button.
Download the appropriate platform-specific zip file, unzip, and read the 'Readme' file.
Note that you must provide a proper value to a JAVA_HOME environment variable [pointer to the mother directory of the Java /bin subdirectory] in the loganalysis.bat | .sh file and use the -d parameter when running standalone.)

Run it from
/Oracle/Middleware/user_projects/epmsystem1/bin/loganalysis.sh -h (on Unix/Linux)
\Oracle\Middleware\user_projects\epmsystem1\bin\loganalysis.bat -h (on Microsoft Windows).
The output is saved under the

(3) The Registry Cleanup command may be used (without fear!) to clean up various corruptions which can  affect the Hyperion (database-based) Repository.

Run it from
/Oracle/Middleware/user_projects/epmsystem1/bin/registry-cleanup.sh (on Unix/Linux)
\Oracle\Middleware\user_projects\epmsystem1\bin\registry-cleanup.bat (on Microsoft Windows).
The actions are described on the command line.

(4) The Remove Instance Command is only used if there are two or more instances configured on one computer and one of those should be deleted.

Run it from
/Oracle/Middleware/user_projects/epmsystem1/bin/remove-instance.sh (on Unix/Linux)
\Oracle\Middleware\user_projects\epmsystem1\bin\remove-instance.bat (on Microsoft Windows).

(5) The Reset Configuration Tool was introduced with EPM
It nullifies Shared Services Hyperion Registry settings so that a service may be reconfigured. You may locate the values to substitute for <product> or <task> by scanning registry.html (generated by running epmsys_registry.bat | .sh).
Find productNAME in INSTANCE_TASKS_CONFIGURATION and SYSTEM_TASKS_CONFIGURATION nodes and identify tasks by property pairs that have values of 'Configurated' or 'Pending'.

Run it from
/Oracle/Middleware/user_projects/epmsystem1/bin/resetConfigTask.sh -product <product> -task <task> (on Unix/Linux)
\Oracle\Middleware\user_projects\epmsystem1\bin\resetConfigTask.bat -product <product> -task <task> (on Microsoft Windows).

Thanks to Maurice for this collection of utilities.


According to an Oracle blog "ECID allows an administrator to track the end-to-end flow of a particular request across the product stack". I would love to know which EPM products support ECID tracing - can I find the log entries for a user launching a Financial Reporting report and goind all the way down to the HFM data source if I use the Log Analysis tool?

Posted by Henri Vilminko on October 21, 2013 at 08:55 AM CEST #

Individual tracking of the Execution Context ID (ECID) is only assured for Hyperion applications (and later). Hence, even if you had the backported Log Analysis utility, the implementation of ECID in earlier versions is likely to be problematic.

The log messages of Financial Reporting are lacking MESSAGE_ID and hence are somewhat difficult to locate. Similarly the HFM MESSAGE_IDs are in a few inconsistent formats (EPMHFM- HFM-).

But you may look in the logs:

If you do locate an ECID in either the Financial Reporting or HFM log files, you should be able to track between the servers. An example of what such a search would entail would be:

loganalysis.bat -ecid "0000Jz3swL5Bh4FpN0DCie1Hr26n000002"

You do not have to add other parameters as the ECID is unique and should be considered even if it is not of type ERROR.



Posted by Maurice Bauhahn on October 29, 2013 at 02:44 PM CET #

Post a Comment:
Comments are closed for this entry.

This blog talks about the latest news and upcoming events initiated by the EPM/BI Proactive Support Team.
Lia, Torben, Paul, Julie


« August 2015