Recovering Oracle Web Cache to a Different Host To recover Oracle Web Cache

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