Recovering Oracle Forms Services to a Different Host To recover Oracle Forms

18-42 Oracle Fusion Middleware Administrators Guide ■ If the failed host contained the master BI Server, primary cluster controller, and primary Oracle BI Scheduler and you want the new instance to be the master BI Server, take the following steps as appropriate. Note that if you want to leave instance2 as the master BI server, you do not need to take these additional steps. – If the master BI Server is lost: a. Stop Oracle WebLogic Server and OPMN processes on all nodes. b. Update the following configuration file to designate a new master BI Server: INSTANCE_ HOMEconfigOracleBIApplicationcoreapplicationClusterConfig.xml For example, change the instance number in the NodeId element and change the host name or IP address in the HostNameOrIP element: Node NodeTypeServerNodeType --This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager-- MasterServertrueMasterServer --This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager-- NodeIdinstance2:coreapplication_obis1NodeId --This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager-- HostNameOrIPhost1.example.comHostNameOrIP --This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager-- ServicePort9703ServicePort --This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--MonitorPort9701MonitorPort Node c. Copy the file to the other host. – If the primary cluster controller or scheduler is lost, it fails over to the standby cluster controller or scheduler. You must determine whether you want to reconfigure it to be the primary cluster controller or scheduler or leave it as secondary that has been activated because the primary components have failed. For more information, see Configuring Secondary Instances of Singleton System Components in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence. ■ If the failed host contained the BI Server, the secondary cluster controller, and the secondary Oracle BI Scheduler, designate the new host as the secondary cluster controller or scheduler. ■ If the failed host contained the BI Server and system components such as BI Presentation Services and BI Java hosts, no additional steps are needed. ■ If the failed host contained the following related components, recover them: – Oracle Business Intelligence Publisher: See Section 18.3.4.10 . – Oracle Real-Time Decisions: See Section 18.3.4.11 . – Oracle Essbase: See Section 18.3.4.12 . – Oracle Hyperion Calculation Manager: See Section 18.3.4.13 . 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: