Recovering Oracle Business Intelligence Discoverer to a Different Host To recover

Recovering Your Environment 18-45 ORACLE_INSTANCEbinessbase_haessfoconfig.sh pushprp 2 12. On Node C, modify the following file to specify unique names for the cluster and its instances. The cluster name must not be the same as the existing cluster. ARBORPATHEssFOConfig.properties For example, modify the following properties: Essbase Cluster Cluster_Name Essbase Instance1 Instance1_Name Essbase Instance2 Instance2_Name Instance 1 is Node C, which is the new node created in step 6; Instance2 is Node B, which is the remaining node from the original cluster. 13. Update the SYSTEM_HOST, SYSTEM_HOST1, SYSTEM_HOST2, and SYSTEM_ USERNAME properties in the following file: ARBORPATHEssFOConfig.properties Note the following: ■ SYSTEM_HOST is the original host, Node A, because the SYSTEM_HOST must always be the first node from where Oracle Essbase was configured. ■ SYSTEM_HOST1 is Node C. ■ SYSTEM_HOST2 is Node B. 14. On Node C, run the following command to copy the EssFOConfig.properties file to the shared disk: ORACLE_INSTANCEbinessbase_haessfoconfig.sh check 15. On Node C, run the following command to create cluster configuration entries in the registry: ORACLE_INSTANCEbinessbase_haessfoconfig.sh create 16. On Node C, run the following command to dump the cluster components from the registry: ORACLE_INSTANCEbinessbase_haessfoconfig.sh dump Check the log file to ensure that the operation completed successfully. The log file is: ORACLE_INSTANCEbinessbase_hacl.md 17. On Node C, run the following command to update the essbase.cfg file: ORACLE_INSTANCEbinessbase_haessfoconfig.sh esscfg Note that if ARBORPATH is the same for the old cluster and the new cluster, the Oracle Essbase failover mode is already configured in essbase.cfg, so you do not need to run this command. 18. On Node C, run the following command to update opmn.xml: ORACLE_INSTANCEbinessbase_haessfoconfig.sh opmn 1 This command generates a modified opmn.xml file which is called opmn_ EssHA.xml. It is written to the following location: 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_