Recovering Oracle BI Enterprise Edition to a Different Host in a Clustered

Recovering Your Environment 18-47 appfinancial_reporting_web_apphost new_host

18.3.4.15 Recovering Oracle Data Integrator to a Different Host

To recover Oracle Data Integrator 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. Recover the Oracle Data Integrator Oracle home from backup, as described in Section 18.2.3 3. Restore the domain, as described in Section 18.3.2 . 4. Stop each standalone agent, and stop the Oracle Data Integrator applications deployed in Oracle WebLogic Server. 5. Modify the repository connection information in the topology, if the database is on a different host: a. Connect to the restored Oracle Data Integrator repository using ODI Studio. Create a new connection for the master repository to the new database host, as described in Connecting to the Master Repository in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. b. Edit each of the Work Repositories. Click Connection and edit the connection information so that the JDBC URL points to the new database host containing the work repository. c. Edit each physical agents configuration and provide the updated Host Name value and, if changed, the Port value. d. If there are standalone agent scripts generated and they contain the -PORT property, change the -PORT value to the new port value. The scripts are named agentName_agent.sh or agentName_agent.bat. 6. For each standalone agent, edit the following files and change the ODI_MASTER_ URL parameter to match the new database host location, if the database is on a different host: oraclediagentbinodiparams. 7. Edit the following file to change the database connection information and the port number: oraclediagentbinodi_opmn_standaloneagent_template.xml 8. In the Oracle WebLogic Server configuration, edit the Data Sources to match the new database host location. 9. Restart the standalone agents and the Oracle Data Integrator applications deployed in Oracle WebLogic Server.

18.3.4.16 Recovering Oracle Enterprise Content Management Suite to a Different Host

The following sections describe how to recover Oracle Universal Content Management and Oracle Universal Records Management to a different host: ■ Recovering Oracle Universal Content Management to a Different Host ■ Recovering Oracle Universal Records Management After Loss of Host 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: