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

18-40 Oracle Fusion Middleware Administrators Guide Oracle_BI\bifoundation\install\vc80\vcredist_x86.exe 4. Import the Registry entries that you exported into the new host, as described in Section 18.3.4.9.4 .

18.3.4.9.2 Recovering Oracle BI Enterprise Edition to a Different Host in a Clustered

Environment In this scenario, you have an Oracle BI EE cluster on two hosts, Host A and Host B. Host A must be replaced for some reason, such as a host crash, and you must recover to Host C. Take the following steps: 1. Restore the Middleware home from backup to Host C, as described in Section 18.2.1 . 2. Restore the database containing the Oracle BI EE schemas, if necessary. See Section 18.3.6 . 3. On Windows, install the C++ libraries from Microsoft, by executing the following file: Oracle_BI\bifoundation\install\vc80\vcredist_x86.exe 4. On Windows, import the Registry entries that you exported into the new host, as described in Section 18.3.4.9.4 . 5. If the failed node contained the Administration Server, recover it, as described in steps 1 through 5 in Section 18.3.2.2 . 6. Scale out the Oracle BI EE system, as described in Scaling Out the BI System on APPHOST2 in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence. Note the following: ■ When you enter the directory specifications for the Domain Home and Applications Home, enter specifications for directories that do not yet exist or that are empty. ■ If the Domain Home field is empty, update the following file with the domain directory: MW_HOMEwlserver_10.3commonnodemanagernodemanager.domains Before you start Node Manager, take the following steps: a. Stop Node Manager process if it is running. b. Run the setNMProps.sh script, which is located in the ORACLE_ COMMON_HOMEcommonbin directory, to set the StartScriptEnabled property to true before starting Node Manager: cd ORACLE_COMMON_HOMEcommonbin .setNMProps.sh c. Restart Node Manager and enable dynamic registration using the following commands: cd WL_HOMEserverbin export JAVA_OPTIONS=-DDomainRegistrationEnabled=true .startNodeManager.sh Recovering Your Environment 18-41 7. Scale out the system components, as described in Scaling Out the System Components in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence. Fusion Middleware Control prompts you to restart the instances after you have changed their configuration. Restart the instances. Because instance1 on Host A is no longer available, you must modify its count of BI Servers, Presentation Servers, and JavaHosts to be 0. Fusion Middleware Control prompts you to restart the instances after you have changed their configuration. Restart the instances. 8. Make instance2 the primary instance and instance3 the secondary instance using Fusion Middleware Control: a. Make instance 2 the primary instance and specify the secondary instance as none. Activate and restart the instance as prompted by Fusion Middleware Control. b. Make instance3 the secondary instance. Activate and restart the instance as prompted by Fusion Middleware Control. See Configuring Secondary Instances of Singleton System Components in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence for more information. 9. Set the listen address of the bi_servern Managed Server, as described in Setting the Listen Address for the bi_server2 Managed Server in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence. 10. Disable host name verification for the bi_servern Managed Server, as described in Disabling Host Name Verification for the bi_server2 Managed Server in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence. 11. Depending on your configuration, perform additional configuration, as described in Performing Additional Configuration for Oracle Business Intelligence Availability in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence. 12. If Oracle HTTP Server is installed, set the frontend HTTP host and port for the Oracle WebLogic Server cluster to ensure that Oracle BI Search URLs are set correctly, as described in Setting the Frontend HTTP Host and Port in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence. 13. Configure Node Manager for the Managed Servers as described in Configuring Node Manager for the Managed Servers in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence. 14. Start the Oracle BI EE Managed Server and all of the OPMN-managed components.

18.3.4.9.3 Additional Steps for Recovering Oracle BI EE Depending on your environment,

you may need to take additional steps after you perform the steps in Section 18.3.4.9.2 : Note: It is important that you set -DDomainRegistrationEnabled=true whenever you start a Node Manager which must manage the Administration Server. If there is no Administration Server on this computer, and if this computer is not an Administration Server failover node, then Node Manager can be started as follows: .startNodeManager.sh 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 .