Recovering Oracle Essbase After Loss of Host

18-50 Oracle Fusion Middleware Administrators Guide Update the following entry, replacing the host name: EMD_URL=http:newhost.domain.com:portemdmain 3. Start Oracle Management Agent, using the following command: opmnctl startproc ias-component=EMAGENT 4. Start the Administration Server: DOMAIN_HOMEbinstartWebLogic.sh -Dweblogic.management.username=username -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true Starting the Administration Server also starts Fusion Middleware Control.

18.3.5.4 Modify the mod_wl_ohs.conf File

When you recover an Administration Server or a Managed Server to a different host and your environment includes Oracle HTTP Server, you must modify the following file on the new host: UNIX ORACLE_INSTANCEconfigOHSohs_namemod_wl_ohs.conf Windows ORACLE_INSTANCE\config\OHS\ohs_name\mod_wl_ohs.conf Modify all of the instances of the host name, port, and clusters elements such as WebLogicHost, WebLogicPort, and WebLogicCluster entries in that file. For example: Location console SetHandler weblogic-handler WebLogicHost Admin_Host WeblogicPort Admin_Port WLProxySSL ON WLProxySSLPassThrough ON Location . . . Location soa-infra SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN2:8001,SOAHOST2VHN1:8001 WLProxySSL ON WLProxySSLPassThrough ON Location

18.3.5.5 Creating a New Machine for Certain Components

For the following Identity Management components and for the Administration Server if it has an Listen address, you must create a new machine with the new host name before you start the Administration Server: ■ Oracle Access Manager ■ Oracle Adaptive Access Manager ■ Oracle Identity Manager ■ Oracle Identity Navigator Take the following steps: 1. Create a new machine with the new host name. Use the following WLST commands, in offline mode: Recovering Your Environment 18-51 wls:offline readDomainDomainHome wls:offlinesampledomain machine = createnewhostname, Machine wls:offlinesampledomain cdMachinenewhostname wls:offlinesampledomain nm = createnewhostname, NodeManager wls:offlinesampledomain cdMachinenewhostnameNodeManagernewhostname wls:offlinesampledomain setListenAddress, newhostname wls:offlinesampledomain updateDomain wls:offlinesampledomain exit 2. For the Administration Server, set the machine with the new host name, using the following WLST command, in offline mode: wls:offline readDomainDomainHome wls:offlinesampledomain cd Machinenewhostname wls:offlinesampledomain machine = cmo wls:offlinesampledomain cd ServerAdminServer wls:offlinesampledomain setMachine, machine wls:offlinesampledomain updateDomain wls:offlinesampledomain exit 3. Set the listen address for the Administration Server: readDomainDomainHome cdserversAdminServer cmo.setListenPort8001 updateDomain

18.3.5.6 Reassociate Users to Groups for Certain Identity Management Components

When you restore a backup of the following Identity Management components, the weblogic user is no longer associated with groups to which it had previously been associated: ■ Oracle Access Manager ■ Oracle Adaptive Access Manager ■ Oracle Identity Manager ■ Oracle Identity Navigator You must reassociate the weblogic user with the groups. For information about associating a user with a group, see the section Add Users to Groups in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.

18.3.5.7 Updating Oracle Inventory

For many components, when you recover to a different host, as in the case of loss of host, you must update the Oracle inventory. To do so, execute the following script: ORACLE_HOMEouibinattachHome.sh In addition, you must update beahomelist to edit the location of a Middleware home. Edit the following file to update the Middleware home information: UNIX user_homebeabeahomelist Windows C:\bea\beahomelist 18-52 Oracle Fusion Middleware Administrators Guide

18.3.5.8 Recovering the Windows Registry

When you recover any component to a different host on Windows, as in the case of loss of host, you must import any Windows Registry keys related to Oracle Fusion Middleware to the new host. You exported the Registry keys in Section 17.3.3 . Recover the following Registry key. HKEY_LOCAL_MACHINE\Software\Oracle In addition, recover each node that begins with Oracle within the following registry keys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services To import a key that you have previously exported, use the following command: regedit I FileName For example: regedit I C:\oracleregistry.reg You can also use the Registry Editor to import the key. See the Registry Editor Help for more information.

18.3.6 Recovering After Loss of Database Host

If the host that contained your database is lost, you can recover the database using RMAN. For example: rman restore database; rman recover database; 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. Also, use the same name for the database. Note the following: ■ See Appendix D for the schemas used by each component. ■ For Oracle BPEL Process Manager, point-in-time recovery ensures that the latest process definitions and in-flight instances are restored. However, this may result in reexecution of the process steps. Oracle recommends that you strive for idempotent Oracle BPEL Process Manager processes. If the system contains processes that are not idempotent, you must clean them up from the dehydration store before starting Oracle Fusion Middleware. See Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle Business Process Management Suite for more information. For detailed steps about recovering a database and using RMAN, see the Oracle Database Backup and Recovery Users Guide, which is available at: http:www.oracle.comtechnetworkdatabaseenterprise-editiondocumenta tionindex.html Part VIII Part VIII Advanced Administration: Expanding Your Environment This part describes how to expand your Oracle Fusion Middleware environment. It contains the following chapters: ■ Chapter 19, Scaling Your Environment ■ Chapter 20, Using the Movement Scripts ■ Chapter 21, Moving from a Test to a Production Environment