Service Fix to Correct EPM System Configurator Anomaly: Cannot Change Shared Services Repository Password

Service Fix to Correct EPM System Configurator Anomaly: Cannot Change Shared Services Repository Password [ID 845780.1]
		Modified 06-APR-2010     Type PROBLEM     Status PUBLISHED

In this Document
  Symptoms
  Cause
  Solution
  References

---

Applies to:

Hyperion BI+ - Version: 11.1.1.1.00 - Release: 11.1
Hyperion Essbase - Version: 11.1.1.1.00 - Release: 11.1
Hyperion Financial Management - Version: 11.1.1.1.00 - Release: 11.1
Hyperion Planning - Version: 11.1.1.1.00 - Release: 11.1
Hyperion Profitability - Version: 11.1.1.1.00 - Release: 11.1
Information in this document applies to any platform.

Symptoms

After the initial configuration of Shared Services Registry database, the EPM System Configurator does not re-display the panel from which the administrator can reset the database password.

Cause

There is an anomaly in the EPM System Configurator that does not allow the admin to change the password for the EPM System Shared Services Registry database. The configuration panel is not displayed subsequent to its initial running. Editing the config.xml to replace Configured with Pending for Shared Services registration will bring the panel back again, however, the admin is still be unable to change the database password.

Solution

Apply Patch:8415312  to correct this anomaly.
NOTE: The Readme for Patch:8415312 states that this patch corrects defect 8415312

After an initial installation and configuration of EPM System, Oracle Essbase Studio server does not start. In addition to that defect, Patch 8415312 corrects this anomaly as well.

This patch expects Essbase Studio to be installed to Hyperion Home.  If Essbase Studio is not installed in Hyperion Home on the computer to which this patch is being applied, perform the following:
1. Unzip the service fix into any folder

2. Edit HIT_11_1_1_1_05/etc/config/inventory.xml and remove the line:
<component internal_name="oracle.epmsystem.essbase.studio.server" version="11.1.1.1.0" opt_req="R"/>

3. Edit HIT_11_1_1_1_05/etc/config/actions.xml; remove the lines:
 <oracle.epmsystem.essbase.studio.server version="11.1.1.1.0" opt_req="R">
 <copy name="essconfiguration.jar" path="%ORACLE_HOME%\products\Essbase\EssbaseStudio\Server" file_name="products\Essbase\EssbaseStudio\Server\essconfiguration.jar"/>
 </oracle.epmsystem.essbase.studio.server>

4. You may now follow the normal documented procedure to apply the service fix.