Recovering Oracle Reports to a Different Host To recover Oracle Reports to a

Recovering Your Environment 18-43 – Oracle Hyperion Financial Reporting: See Section 18.3.4.14 . – Oracle Hyperion Smart View: See Section 18.2.7.16 .

18.3.4.9.4 Importing Oracle BI Enterprise Edition Registry Entries On Windows, you must

import the Oracle BI Enterprise Edition Registry entries to the new host. Section 17.3.3 describes how to export them from the original host. 1. Copy all the files that you exported from the original host to the new host. 2. Double-click each file you copied from the original host. Click Yes when prompted, to import the file into the Registry.

18.3.4.10 Recovering Oracle Business Intelligence Publisher to a Different Host

To recover Oracle Business Intelligence Publisher to a different host: 1. Recover the Managed Server containing the Oracle Business Intelligence Publisher component, as described in Section 18.3.3 . 2. Restore the database containing the Oracle Business Intelligence Publisher schemas, if necessary. See Section 18.2.10 . If backup artifacts are restored from different time, then user accounts, user reports, and user permissions revert to the restored version. Restore all artifacts from the same point in time.

18.3.4.11 Recovering Oracle Real-Time Decisions to a Different Host

To recover Oracle Real-Time Decisions to a different host: 1. Recover the Managed Server containing the Oracle Real-Time Decisions component, as described in Section 18.3.3 . Note that if backup artifacts are restored from different time, the analytic models miss a period of learning, but their intelligence is unaffected.

18.3.4.12 Recovering Oracle Essbase After Loss of Host

If Oracle Essbase is in a clustered environment, and the failed host contained Essbase system component clustering using OPMN, take the following additional steps to recover Oracle Essbase. In this scenario, Oracle Essbase clustering is set up on Node A and B, and you lose Node A. You create a new Essbase component on Node C and a new cluster with Essbase components on Node C and Node B. The old cluster is gone and should not be recovered at any time. 1. Scale out the Oracle BI EE system and the system components on the new host, Node C, as described in Steps 6 and 7 in Section 18.3.4.9 . 2. Mount the shared ARBORPATH directory to the same path on both Node B and Node C. For example, on Windows, map the directory to Drive Y on both Node B and Node C. 3. Edit the following file on Node B and Node C, to update the adminHost property: ORACLE_INSTANCEconfigOPMNopmninstance.properties For example: adminHost=ADMINVHN 4. On Node C, copy the wallet and push it to the Administration Server: a. Copy the wallet from Node B to Node C. The wallet is located in: 18-44 Oracle Fusion Middleware Administrators Guide ORACLE_INSTANCEconfigOPMNopmnwallet b. Ensure that the opmn.xml file has ssl enabled=true. c. Push the wallet to the Administration Server, using the following command: .opmnctl updateinstanceregistration This command prompts for an Oracle WebLogic Server Administrator password. The updateinstanceregistration command updates information registered on the Administration Server for the Oracle instances. Specifically, the updateinstanceregistration command updates the registered OPMN remote port, remote host, and wallet from the current OPMN settings. d. Restart OPMN on all nodes: opmnctl startall 5. Shut down the Oracle Essbase instance on Node B because it will be made part of the new cluster: opmnctl stopproc ias-component=essbaseserver1 process-type=Essbase 6. Create the Essbase system component on a new host, Node C: opmnctl createcomponent -componentName component_name -componentType Essbase -appServerDomainHomeLocation Admin_Server_Domain_Home -jpsConfigSetup false -epmEssbaseAgentPort port_num -epmEssbaseServerStartPort port_num -epmEssbaseServerEndPort port_num Note: Do not specify the -epmClusterName parameter in the opmnctl createcomponent command. Refer to the ORACLE_HOMEbifoundationadminprovisioningreadme.txt file for changes to the opmnctl createcomponent parameters for Oracle Essbase. 7. On Node C, update the SHARED_FOLDER parameter in the following files: ORACLE_INSTANCEbinessbase_haessfoenv.properties UNIX ORACLE_INSTANCEbinessbase_haessfoenv.sh Windows ORACLE_INSTANCE\bin\essbase_ha\essfoenv.bat For example, change the value of the SHARED_FOLDER parameter to: ARBORPATHEssconfig 8. Remove the following file from the ARBORPATH directory, because you are creating a new cluster with the same ARBORPATH: EssFOConfig.properties 9. On Node C, run the following command to copy the EssFOConfig.properties file from the local disk to the shared ARBORPATH directory: ORACLE_INSTANCEbinessbase_haessfoconfig.sh check 10. On Node C, run the following command: ORACLE_INSTANCEbinessbase_haessfoconfig.sh pushprp 1 11. On Node B, run the following command: 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: