Recovering Oracle BI Enterprise Edition in a Clustered Environment This scenario

18-18 Oracle Fusion Middleware Administrators Guide 2. Redeploy the old version of the application. If the application was deployed to a cluster, redeploy the application to the same cluster.

18.2.10 Recovering a Database

If your database that contains your metadata repository, including the MDS Repository, is corrupted, you can recover it using RMAN. You can recover the database at the desired granularity, either a full recovery or a tablespace recovery. For best results, recover the database to the most current state, using point-in-time recovery if the database is configured in Archive Log Mode. This ensures that the latest data is recovered. For example: rman restore database; rman recover database; See Appendix D for the schemas used by each component. For detailed steps, see the Oracle Database Backup and Recovery Users Guide, which is available at: http:www.oracle.comtechnetworkdatabaseenterprise-editiondocumenta tionindex.html

18.3 Recovering After Loss of Host

This section describes how to recover your Oracle Fusion Middleware environment after losing the original operating environment. For example, you could have a serious system malfunction or loss of media. The sections includes the following topics: ■ Recovering After Loss of Oracle WebLogic Server Domain Host ■ Recovering After Loss of Administration Server Host ■ Recovering After Loss of Managed Server Host ■ Recovering After Loss of Component Host ■ Additional Actions for Recovering Entities After Loss of Host ■ Recovering After Loss of Database Host

18.3.1 Recovering After Loss of Oracle WebLogic Server Domain Host

To recover an Oracle WebLogic Server domain: 1. Stop all relevant processes. That is, stop all processes that are related to the domain, such as the Administration Server and Managed Servers. For example, stop the Administration Server: DOMAIN_HOMEbinstopWeblogic.sh username password [admin_url] 2. Recover the domain directory from backup: cd DOMAIN_HOME UNIX tar -xf domain_backup_092010.tar Windows jar xtf domain_backup_092010.jar Note: When you are recovering in the case of loss of host, you must restore the files using the same path as on the original host. Recovering Your Environment 18-19 3. Start all relevant processes. That is, start all processes that are related to the domain. For example, start the Administration Server: DOMAIN_HOMEbinstartWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true 4. If you cannot start the Administration Server, recover it, as described in Section 18.3.2 . 5. If you cannot start a Managed Server, recover it, as described in Section 18.3.3 .

18.3.2 Recovering After Loss of Administration Server Host

If you lose a host that contains the Administration Server, you can recover it to the same host or a different host, as described in the following topics: ■ Recovering the Administration Server to the Same Host ■ Recovering the Administration Server to a Different Host

18.3.2.1 Recovering the Administration Server to the Same Host

In this scenario, you recover the Administration Server either to the same host after the operating system has been reinstalled or to a new host that has the same host name. For example, the Administration Server is running on Host A and the Managed Server is running on Host B. Host A has failed for some reason and the Administration Server must be recovered. To recover the Administration Server to the same host: 1. Recover the file system. For example, recover the domain containing the Administration Server, as described in Section 18.3.1 . 2. Attempt to start the Administration Server. For example: DOMAIN_HOMEbinstartWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true If the Administration Server starts, you do not need to take any further steps. 3. If the Administration Server fails to start, take the following steps on Host A: a. Stop all relevant processes. That is, stop all processes that are related to the domain, such as the Administration Server and Managed Servers. For example, to stop the Administration Server on Linux: DOMAIN_HOMEbinstopWeblogic.sh username password [admin_url] b. Recover the Middleware home, if needed: tar -xf mw_home_backup_092010.tar c. If the domain directory does not reside in the Middleware home, recover the domain directory from backup: cd DOMAIN_HOME tar -xf domain_backup_092010.tar d. Start the Administration Server. For example: DOMAIN_HOMEbinstartWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=password