Additional Steps for Recovering Oracle BI EE Depending on your environment,

18-48 Oracle Fusion Middleware Administrators Guide

18.3.4.16.1 Recovering Oracle Universal Content Management to a Different Host To recover

Oracle Universal Content Management to a different host: 1. If the database must be restored to a different host, restore it, as described in Section 18.3.6 . 2. Restore the domain, as described in Section 18.3.2 . 3. If the Vault, WebLayout, or Search directories are not located in the domain directory, restore those directories, if necessary. For example, if the Vault directory is located on a shared drive in nethomevault, restore it from backup: cd nethomevault tar -xf vault_backup_092010.tar 4. Edit the following file: DOMAIN_HOMEucm_domainucmcsconfigconfig.cfg In the file, change the HttpServerAddress setting to specify the new host. For example: HttpServerAddress=hostname:port_number Note that you should restore the database and the shared file system at the same time. If you cannot do that, you can use the IDCAnalyse utility to determine if there are any inconsistencies between the database and the shared file system. If there are, you can perform a manual recovery using IDCAnalyse.

18.3.4.16.2 Recovering Oracle Universal Records Management After Loss of Host Because

Oracle Universal Records Management depends on Oracle Universal Content Management and has no additional backup and recovery artifacts, see the recovery procedure for Oracle Universal Content Management in Section 18.3.4.16.1 .

18.3.5 Additional Actions for Recovering Entities After Loss of Host

Depending on the entity that you are recovering, you may need to take additional actions after loss of host. The sections about each entity may require you to follow one or more of the following procedures. If so, that is noted in the section describing how to recover the entity. The following topics describe the actions you may need to take: ■ Recovering Fusion Middleware Control to a Different Host ■ Changing the Host Name in the targets.xml File for Fusion Middleware Control ■ Recovering Oracle Management Agent When Components Are Recovered to a Different Host ■ Modify the mod_wl_ohs.conf File ■ Creating a New Machine for Certain Components ■ Updating Oracle Inventory ■ Recovering the Windows Registry

18.3.5.1 Recovering Fusion Middleware Control to a Different Host

To recover Fusion Middleware Control to a different host, take the following steps: 1. Update the host name in the following file: Recovering Your Environment 18-49 DOMAIN_HOMEservers AdminServertmp_WL_useremhsz5x1META-INFemoms.properties In the file, change the host name for the following properties: mas.conn.url oracle.sysman.emSDK.svlt.ConsoleServerHost 2. Edit the following file: UNIX ORACLE_INSTANCEEMAGENTemagent_namesysmanconfigemd.properties Windows ORACLE_INSTANCE\EMAGENT\emagent_name\sysman\config\emd.properties In the file, edit the following entry for each component monitored by Oracle Management Agent, replacing the host name: REPOSITORY_URL=http:newhost.domain.com:portemupload

18.3.5.2 Changing the Host Name in the targets.xml File for Fusion Middleware Control

When you recover a component to a different host, you must update the targets.xml file for Fusion Middleware Control. The file is located at: DOMAIN_HOMEsysmanstatetargets.xml In the file, change the host name to the new host name for components that are recovered to a different host.

18.3.5.3 Recovering Oracle Management Agent When Components Are Recovered to a Different Host

For many components, when you recover to a different host, as in the case of loss of host, you must take actions to recover Oracle Management Agent so that Fusion Middleware Control can manage the components. This pertains to the following installation types and components: ■ Identity Management components ■ Oracle Identity Federation ■ Oracle Portal ■ Oracle Business Intelligence Discoverer ■ Oracle Forms Services ■ Oracle Reports To recover Oracle Management Agent, take the following actions: 1. Edit the following file: UNIX ORACLE_INSTANCEEMAGENTemagent_namesysmanemdtargets.xml Windows ORACLE_INSTANCE\EMAGENT\emagent_name\sysman\emd\targets.xml In the file, edit the following element, replacing the host name: Target TYPE=host NAME=newhost.domain.com DISPLAY_NAME=newhost.domain.com 2. Edit the following file: UNIX ORACLE_INSTANCEEMAGENTemagent_namesysmanconfigemd.properties Windows ORACLE_INSTANCE\EMAGENT\emagent_name\sysman\config\emd.properties 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: