Recovering Oracle BI Enterprise Edition to a Different Host in a Non-Clustered

18-46 Oracle Fusion Middleware Administrators Guide ORACLE_INSTANCEconfigOPMNopmn 19. On Node B, run the following command to update opmn.xml: ORACLE_INSTANCEbinessbase_haessfoconfig.sh opmn 2 This command generates a modified opmn.xml file which is called opmn_ EssHA.xml. It is written to the following location: ORACLE_INSTANCEconfigOPMNopmn 20. On Nodes B and C, modify the following file, adding a topology element if it does not exist, and modify the nodes list element to reflect the nodes Node B and Node C in the new cluster: ORACLE_INSTANCEconfigOPMNopmnopmnEssHA.xml For example: notification-server interface=any port local=9500 remote=9501 ssl enabled=false wallet-file=ORACLE_ INSTANCEconfigOPMNopmnwallet topology nodes list=Node_B,Node_C topology notification-server 21. On Nodes B and C, copy the opmnEssHA.xml file for each node to the following location, renaming it opmn.xml: ORACLE_INSTANCEconfigOPMNopmn Now, Nodes B and C are OPMN cluster node members. 22. Stop all OPMN components on Nodes B and C, and then restart them: opmnctl stopall opmnctl startall

18.3.4.13 Recovering Oracle Hyperion Calculation Manager After Loss of Host

To recover Oracle Hyperion Calculation Manager after loss of host, follow the procedure in Section 18.2.7.14 . If the database must be restored, restore the database and import Calculation Manager rules and rule sets from the file you exported. In Calculation Manager, select File, and then Import.

18.3.4.14 Recovering Oracle Hyperion Financial Reporting After Loss of Host

If you lose a host that contains Oracle Hyperion Financial Reporting, you can recover it to the same host or a different host. To recover Oracle Hyperion Financial Reporting, recover the Oracle home, as described in Section 18.2.3 and the Oracle instance, as described in Section 18.2.4 . If the database host has changed, update the host name using the following commands: Epmsys_registry updateproperty financial_reporting_producthost new_host Epmsys_registry updateproperty financial_reporting_productlogical_web_apphost new_host Epmsys_registry updateproperty financial_reporting_productlogical_web_ Recovering Your Environment 18-47 appfinancial_reporting_web_apphost new_host

18.3.4.15 Recovering Oracle Data Integrator to a Different Host

To recover Oracle Data Integrator to a different host: 1. If the database must be restored to a different host, restore it, as described in Section 18.3.6 . 2. Recover the Oracle Data Integrator Oracle home from backup, as described in Section 18.2.3 3. Restore the domain, as described in Section 18.3.2 . 4. Stop each standalone agent, and stop the Oracle Data Integrator applications deployed in Oracle WebLogic Server. 5. Modify the repository connection information in the topology, if the database is on a different host: a. Connect to the restored Oracle Data Integrator repository using ODI Studio. Create a new connection for the master repository to the new database host, as described in Connecting to the Master Repository in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. b. Edit each of the Work Repositories. Click Connection and edit the connection information so that the JDBC URL points to the new database host containing the work repository. c. Edit each physical agents configuration and provide the updated Host Name value and, if changed, the Port value. d. If there are standalone agent scripts generated and they contain the -PORT property, change the -PORT value to the new port value. The scripts are named agentName_agent.sh or agentName_agent.bat. 6. For each standalone agent, edit the following files and change the ODI_MASTER_ URL parameter to match the new database host location, if the database is on a different host: oraclediagentbinodiparams. 7. Edit the following file to change the database connection information and the port number: oraclediagentbinodi_opmn_standaloneagent_template.xml 8. In the Oracle WebLogic Server configuration, edit the Data Sources to match the new database host location. 9. Restart the standalone agents and the Oracle Data Integrator applications deployed in Oracle WebLogic Server.

18.3.4.16 Recovering Oracle Enterprise Content Management Suite to a Different Host

The following sections describe how to recover Oracle Universal Content Management and Oracle Universal Records Management to a different host: ■ Recovering Oracle Universal Content Management to a Different Host ■ Recovering Oracle Universal Records Management After Loss of Host