Recovering Oracle Business Intelligence Publisher

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 18-20 Oracle Fusion Middleware Administrators Guide -Dweblogic.system.StoreBootIdentity=true e. Start the Managed Servers, specifying the Administration URL for the host: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url f. Start Node Manager: java weblogic.WLST wls:offline startNodeManager

18.3.2.2 Recovering the Administration Server to a Different Host

In this scenario, 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 moved to Host C. To recover the Administration Server to a different host: 1. Recover the Middleware home to Host C the new Host: cd MW_HOME tar -xf mw_home_backup_092010.tar 2. 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 3. If the Administration Server has a Listen address, create a new machine with the new host name, as described in Section 18.3.5.5 . 4. Start Node Manager on Host C if it was configured on the original host: java weblogic.WLST wls:offline startNodeManager 5. Start the Administration Server. For example: DOMAIN_HOMEbinstartWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true 6. Start the Managed Servers. The section Restarting a Failed Administration Server in the Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server describes different ways to restart them, depending on how they were configured. One option is to use the following script, specifying the Administration URL of the new host: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url 7. Ensure that additional application artifacts are available. For example, if the deployment mode is nostage or external_stage, applications may reside in directories outside of the domain directory. Make your application files available to the new Administration Server by copying them from backups or by using a shared disk. Your application files should be available in the same relative location on the new file system as on the file system of the original Administration Server. If the application is staged, the Administration Server copies the application bits to the staged directories on the Managed Server hosts.