Why... Why... Why?
This blog is dedicated to documenting error resolution and other tidbits that I discover while working as a Consultant in the Oracle EPM (Hyperion) field. As much of my job revolves around issue resolution, I see an opportunity to supplement the typical troubleshooting avenues such as the Oracle Knowledgebase and Oracle Forums with more pinpointed information about specific errors as they are encountered. Beware, the information found in this blog is for informational purposes only and comes without any warranty or guarantee of accuracy.

EPMVirt: Create your own Oracle Hyperion Virtual Environment:

Tuesday, January 15, 2013

epmsys_registry Command Line Options

The epmsys_registry command is the key to manipulating the insides of the EPM System. However, it is not well documented. Here are a few ways to further explore the tool...

A command that is useful is the host report. This report can show you what hosts are stored inside the epm registry and what those hosts are being resolved to on each node in the environment. This is useful if you have DNS names or virtual names inside the registry and how those names are being resolved on the host itself. Over time, host resolution may change based on host file entries, DNS changes, failover scenarios, load balancing...etc. The report can identify host related issues buried inside the registry.

epmsys_registry viewhosts

Hosts in EPM Registry
*************************                            *************************************
1       host1.full                                      host1.full
2       VirtualIP                                       host2.full

Generate a deployment report
  - Creates a report enumerating your web deployments and a history of deployment activities.
epmsys_registry report deployment

Components of the report:
  • Logical Web Addresses
  • Application Tier Components
  • EPM Deployment Topology Report 
  • EPM Deployment History Report
  • User Directories - SSO Not Enabled
  • Database Connections
  • Data Directories
Sample Command Line Usage:

epmsys_registry deletecomponent #8dafd4d781a01633a4a713b43baa1b1S6c71
    The component has been removed. However the linked components remain.


Change the database password in the EPM Registry:
epmsys_registry updateencryptedproperty #64f85ee85aef2a62eccaf7d13c02cb3445S76a3/@dbPassword testpw
    The new value of the property has been encrypted and updated on the component.

Hierarchical changes:
epmsys_registry createlink #18349408fd0bc34c2226d26dafds88d019S7a87 #834940894494fdcS6fe8c90313b3e28c59dS6d7f

-- first argument is parent component , second is the child link that will be removed. epmsys_registry removelink #18349408fd0bc34dfda33b3e28c59dS6d7f #8349408fd0bc34addd26213aad88d019S7a87

Full List of Command Line Options
 viewencryptedproperty (and yes this does display the unencrypted password)


  1. I am trying to recover the admin password (version and I tried viewencryptedproperty but it does not work. have you tested it.

  2. I have tested the viewnencryptedproperty but I do not think it is going to be useful for changing the admin password. This is more for stuff stored in the epm registry like database connection passwords. You probably can google how to recover the admin password - but I dont think the approach is to try and make it readable - it will be to replace the encrypted hash with something you know. One likely approach is to do it at the relational database level by finding the admin password and replacing it with a value from a known native user and or the password from another env.