Recovering Oracle Universal Records Management

Recovering Your Environment 18-21 8. Update Oracle Inventory, as described in Section 18.3.5.7 . 9. If your environment contains Oracle HTTP Server, modify the mod_wl_ohs.conf file, as described in Section 18.3.5.4 . 10. Edit the targets.xml file for Fusion Middleware Control, as described in Section 18.3.5.2 . 11. Oracle Management Service, which is part of Fusion Middleware Control, is on the original host and is recovered to the new host when you restore the Administration Server. Oracle Management Agent connects to Oracle Management Service to monitor certain components. If your environment contains components, such as Oracle Internet Directory and Oracle Virtual Directory, that use Oracle Management Agent, but they are located on a different host, you must take the following steps on each host containing the components. For example, the Administration Server was on Host A, but is restored, along with Oracle Management Service, to Host B. Oracle Internet Directory is on Host C and Oracle Virtual Directory is on Host D. You must take these steps on both Host C and Host D. a. Edit the following file: UNIX ORACLE_INSTANCEEMAGENTemagent_namesysmanconfigemd.properties WindowsORACLE_INSTANCE\EMAGENT\emagent_name\sysman\config\emd.properties Update the following entries, replacing the host name with the new host for the Administration Server: emdWalletSrcUrl=http:newhost.domain.com:portemwalletsemd REPOSITORY_URL=http:newhost.domain.com:portemupload b. Shut down and restart the EM Agent process: cd ORACLE_INSTANCEEMAGENTemagent_dir .emctl stop agent .emctl start agent .emctl status agent The status command shows the REPOSITORY_URL pointing to the new host. Now you can start and stop the Managed Server on Host B using the Administration Console running on Host C. If you are recovering the Administration Server for a Web Tier installation, see Section 18.3.5 for information about additional actions you must take.

18.3.3 Recovering After Loss of Managed Server Host

If you lose a host that contains a Managed Server, you can recover it to the same host or a different host, as described in the following topics: ■ Recovering a Managed Server to the Same Host ■ Recovering a Managed Server to a Different Host ■ Recovering an Oracle SOA Suite Managed Server That Has a Separate Directory This section pertains when Oracle SOA Suite is configured in a domain and no Managed Servers share the domain directory with the Administration Server. 18-22 Oracle Fusion Middleware Administrators Guide

18.3.3.1 Recovering a Managed Server to the Same Host

In this scenario, you recover a Managed Server to the same host after the operating system has been reinstalled or to a new host that has the same host name. The Administration Server is running on Host A and the Managed Server is running on Host B. Host B failed for some reason and the Managed Server must be recovered to Host B. To recover a Managed Server to the same host: 1. Start Node Manager on Host B: java weblogic.WLST wls:offline startNodeManager 2. Start the Managed Server. For example: DOMAIN_HOMEbinstartManagedWebLogic.sh managed_server_name admin_url If the Managed Server starts, it connects to the Administration Server and updates its configuration changes. You do not need to take any further steps. 3. If the Managed Server fails to start or if the file system is lost, take the following steps: a. Stop Node Manager: java weblogic.WLST wls:offline stopNodeManager b. Recover the Middleware home to Host B from the backup, if required: tar -xf mw_home_backup_092010.tar c. If the Managed Server contains Oracle Portal, Oracle Reports, Oracle Forms Services, or Oracle Business Intelligence Discoverer, and the Managed Server domain directories reside outside of the Middleware home, restore the domain, in addition to the Middleware home. For example: cd Domain_Home tar -xf domain_home_backup_092010.tar Go to Step e. d. If the Managed Server does not contain the components listed in Step c, take the following steps: – Create a domain template jar file for the Administration Server running in Host A, using the pack utility. For example: pack.sh -domain=MW_HOMEuser_projectsdomainsdomain_name -template=scratchtemp.jar -template_name=test_install -template_author=myname -log=scratchlogsmy.log -managed=true Specifying the -managed=true option packs up only the Managed Servers. If you want to pack the entire domain, omit this option. – Unpack the domain template jar file in Host B, using the unpack utility: unpack.sh -template=scratchaime1ms.jar -domain=MW_HOMEuser_projectsdomainsdomain_name -log=scratchlogsnew.log -log_priority=info