Skip Headers
Oracle® Fusion Middleware Administrator's Guide
11g Release 1 (11.1.1)

Part Number E10105-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

18 Recovering Your Environment

This chapter describes recommended recovery strategies and procedures for recovering Oracle Fusion Middleware from different types of failures and outages.

This chapter includes the following topics:

18.1 Overview of Recovering Your Environment

This section provides an overview of recovery strategies for outages that involve actual data loss or corruption, host failure, or media failure where the host or disk cannot be restarted and they are permanently lost. This type of failure requires some type of data restoration before the Oracle Fusion Middleware environment can be restarted and continue with normal processing.

Note:

The procedures in this chapter assume that no administrative changes were made since the last backup. If administrative changes were made since the last backup, they must be reapplied after recovery is complete.

When you restore the files, use your preferred tool to extract the compressed files:

Ensure that the tool you are using preserves the permissions and timestamps of the files.

Rename existing files and directories before you begin restoring the files from backup so that you do not unintentionally override necessary files.

18.2 Recovering After Data Loss, Corruption, Media Failure, or Application Malfunction

This section describes recovery strategies for outages that involve actual data loss or corruption, or media failure where the disk cannot be restored. It also describes recovery strategies for applications that are no longer functioning properly. This type of failure requires some type of data restoration before the Oracle Fusion Middleware environment can be restarted and continue with normal processing. It contains the following topics:

18.2.1 Recovering a Middleware Home

You can recover a Middleware home that was corrupted or from which files were deleted.

To recover the Middleware home:

  1. Stop all relevant processes. That is, stop all processes that are related to the domain, such as the Administration Server, Node Manager, and Managed Servers. For example, to stop the Administration Server on Linux:

    DOMAIN_HOME/bin/stopWeblogic.sh username password [admin_url]
    
  2. Recover the Middleware home directory from backup. For example:

    cd MW_HOME
    (UNIX) tar -xf mw_home_backup_092010.tar
    (Windows) jar xtf mw_home_backup_092010.jar
    
  3. Start all relevant processes. That is, start all processes that run in the Middleware home. For example, start the Administration Server:

    DOMAIN_HOME/bin/startWebLogic.sh -Dweblogic.management.username=username
     -Dweblogic.management.password=password
     -Dweblogic.system.StoreBootIdentity=true
    

18.2.2 Recovering an Oracle WebLogic Server Domain

You can recover an Oracle WebLogic Server domain that was corrupted or deleted from the file system.

Caution:

Performing a domain-level recovery can impact other aspects of a running system and all of the configuration changes performed after the backup was taken will be lost.

To recover an Oracle WebLogic Server domain that was corrupted or deleted from the file system:

  1. 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, stop the Administration Server:

    DOMAIN_HOME/bin/stopWeblogic.sh username password [admin_url]
    
  2. Recover the domain directory from backup:

    cd DOMAIN_HOME
    (UNIX) tar -xf domain_backup_092010.tar 
    (Windows) jar xtf domain_backup_092010.jar 
    
  3. Start all relevant processes. That is, start all processes that are related to the domain. For example, start the Administration Server:

    DOMAIN_HOME/bin/startWebLogic.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.2.5.

  5. If you cannot start a Managed Server, recover it, as described in Section 18.2.6.

18.2.3 Recovering an Oracle Home

To recover your Oracle home for a particular component:

  1. Recover the Oracle home to the original directory from a backup file. For example:

    cd ORACLE_HOME
    tar -xf Oracle_home_backup_092010.tar 
    
  2. Restart the Managed Server to which applications are deployed, using the WLST start command. For example:

    wls:/mydomain/serverConfig> start('myserver','Server')
    

18.2.4 Recovering an Oracle Instance Home

An Oracle instance home contains configuration information for system components, such as Oracle HTTP Server or Oracle Internet Directory. (See Section 3.5.2 for a list of system components.) The following topics describe how to recover an Oracle instance home:

18.2.4.1 Recovering After Oracle Instance Home Deleted from File System

To recover an Oracle instance home that was corrupted or deleted from the file system:

  1. Stop all relevant processes. That is, kill all processes that are related to that Oracle instance.

  2. Recover the Oracle instance home directory from a backup file. For example:

    cd ORACLE_INSTANCE
    (UNIX) tar -xf Instance_home_backup_092010.tar 
    (Windows) jar xtf Instance_home_backup_092010.jar
    
  3. Start all relevant processes. That is, start all processes that are related to that Oracle instance:

    opmnctl startall
    

18.2.4.2 Recovering After Oracle Instance Home Deregistered

To recover an Oracle instance home that was deregistered from the domain:

  1. Recover the Oracle instance home directory from a backup file. For example, on Linux:

    cd ORACLE_INSTANCE
    tar -xf Instance_home_backup_092010.tar 
    
  2. Register the Oracle instance, along with all of its components, with the Administration Server, using the opmnctl registerinstance command. For example:

    opmnctl registerinstance -adminHost admin_server_host 
         -adminPort admin_server_port -adminUsername username 
         -adminPassword password
         -oracleInstance ORACLE_INSTANCE_dir -oracleHome ORACLE_HOME_dir
         -instanceName Instance_name -wlserverHome Middleware_Home
    

18.2.5 Recovering the Administration Server Configuration

If the Administration Server configuration has been lost because of file deletion or file system corruption, the Administration Server console continues to function if it was already started when the problem occurred. The Administration Server directory is regenerated automatically, except for security information. As a result, whenever you start the Administration Server, it prompts for a user name and password. To prevent this, you can recover the configuration.

Caution:

Performing a domain-level recovery can impact other aspects of a running system and all of the configuration changes performed after the backup was taken will be lost.

To recover the Administration Server configuration:

  1. Stop all processes, including the Administration Server, Managed Servers, and Node Manager, if they are started. For example, to stop the Administration Server:

    DOMAIN_HOME/bin/stopWeblogic.sh username password [admin_url]
    
  2. Recover the Administration Server configuration by recovering the domain home backup to a temporary location. Then, restore the config directory to the following location:

    DOMAIN_HOME/config
    
  3. Start the Administration Server. For example:

    DOMAIN_HOME/bin/startWebLogic.sh -Dweblogic.management.username=username
       -Dweblogic.management.password=password
       -Dweblogic.system.StoreBootIdentity=true
    
  4. Verify that the Administration Server starts properly and is accessible.

On the next configuration change, the configuration from the Administration Server is pushed to the Managed Servers. On each Managed Server restart, the configuration is retrieved from the Administration Server.

18.2.6 Recovering a Managed Server

You can recover a Managed Server's files, including its configuration files if they are deleted or corrupted.

The following topics describe how to recover a Managed Server's files:

18.2.6.1 Recovering a Managed Server When It Cannot Be Started

In this scenario, the Managed Server does not operate properly or cannot be started because the configuration has been deleted or corrupted or the configuration was mistakenly changed and you cannot ascertain what was changed.

To recover a Managed Server when it cannot be started:

  1. If the Administration Server is not reachable, recover the Administration Server, as described in Section 18.2.5.

  2. If the Managed Server fails to start or if the file system is lost, take the following steps:

    1. Recover the Middleware home from the backup, if required. For example:

      tar -xf mw_home_backup_092010.tar 
      
    2. Create a domain template jar file for the Administration Server, using the pack utility. For example:

      pack.sh -domain=MW_HOME/user_projects/domains/domain_name
         -template=/scratch/temp.jar -template_name=test_install 
         -template_author=myname -log=/scratch/logs/my.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.

    3. Unpack the domain template jar file, using the unpack utility:

      unpack.sh -template=/scratch/aime1/ms.jar
         -domain=MW_HOME/user_projects/domains/domain_name
         -log=/scratch/logs/new.log -log_priority=info
      
    4. Ensure that the application artifacts are accessible from the Managed Server host. That is, if the application artifacts are not on the same server as the Managed Server, they must be in a location accessible by the Managed Server.

      Note:

      • For stage mode applications, the Administration server copies the application bits to the staged directories on the Managed Server hosts.

      • For nostage and external_stage mode applications, ensure that application files are available in the stage directories of the Managed Server.

      See Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server for information about stage, nostage, and external_stage mode applications.

    5. Start the Managed Server. For example:

      DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name
                admin_url 
      

      The Managed Server connects to the Administration Server and updates its configuration changes.

18.2.6.2 Recovering a Managed Server When It Does Not Function Correctly

In this scenario, the Managed Server is running, but the file system for the Managed Server has been lost or corrupted.

To recover the Managed Server:

  1. Stop the Managed Server. For example:

    DOMAIN_HOME/bin/stopManagedWeblogic.sh managed_server_name admin_url
            username password
    
  2. Recover the Middleware home from the backup, if required:

    tar -xf mw_home_backup_092010.tar 
    
  3. Create a domain template jar file for the Administration Server, using the pack utility. For example:

    pack.sh -domain=MW_HOME/user_projects/domains/WLS_SOAWC
      -template=/scratch/temp.jar -template_name=test_install 
      -template_author=myname -log=/scratch/logs/my.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.

  4. Unpack the domain template jar file, using the unpack utility:

    unpack.sh -template=/scratch/aime1/ms.jar 
       -domain=MW_HOME/user_projects/domains/WLS_SOAWC
       -log=/scratch/logs/new.log -log_priority=info
    
  5. Ensure that the application artifacts are accessible from the Managed Server host. That is, if the application artifacts are not on the same server as the Managed Server, they must be in a location accessible by the Managed Server.

    Note:

    • For stage mode applications, the Administration server copies the application bits to the staged directories on the Managed Server hosts.

    • For nostage and external_stage mode applications, ensure that application files are available in the stage directories of the Managed Server.

    See Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server for information about deploying applications.

  6. Restart the Managed Server. For example:

    DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url
    

18.2.6.3 Recovering an Oracle SOA Suite Managed Server That Has a Separate Directory

When Oracle SOA Suite is configured in a domain and no Managed Servers share the domain directory with the Administration Server, you must restore the Managed Server directory. For example, a domain contains two Managed Servers, one of which contains Oracle SOA Suite, but neither of the Managed Server's directories are in the same directory structure as the Administration Server.

In this case, you must restore the Managed Server from backup:

  1. Restore the Managed Server from backup:

    cd ManagedServer_Home
    tar -xf managed_server_backup_092010.tar 
    
  2. Restart the Managed Server:

    DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name 
              admin_url 
    

18.2.7 Recovering Components

For most components, the following topics describe how to recover a component:

For some components, you must take different steps. Table 18-1 lists those components and the section that describes the procedures to recover them.

Table 18-1 Recovery Procedures for Particular Components

Component Procedure

Oracle Access Manager

Section 18.2.7.5

Oracle Adaptive Access Manager

Section 18.2.7.6

Oracle BI Enterprise Edition

Section 18.2.7.10

Oracle Business Intelligence Publisher

Section 18.2.7.11

Oracle Business Process Management

Section 18.2.7.7

Oracle Real-Time Decisions

Section 18.2.7.12

Oracle Data Integrator

Section 18.2.7.13

Oracle Identity Manager

Section 18.2.7.3

Oracle Identity Navigator

Section 18.2.7.4

Oracle Imaging and Process Management

Section 18.2.7.15

Oracle Information Rights Management

Section 18.2.7.14

Oracle Universal Content Management

Section 18.2.7.16

Oracle Universal Records Management

Section 18.2.7.17

Oracle WebCenter Activity Graph

Section 18.2.7.8

Oracle WebCenter Analytics

Section 18.2.7.9


18.2.7.1 Recovering a Component That Is Not Functioning Properly

You can recover a component if the component's files have been deleted or corrupted or if the component cannot be started or is not functioning properly because the component's configuration was changed and committed. You may not be able to ascertain what change is causing the problem and you want to revert to an earlier version.

  • For Java components, such as Oracle SOA Suite, you recover the Managed Server, as described in Section 18.2.6.

  • For system components, such as Oracle HTTP Server or Oracle Web Cache:

    1. Stop the component. For example, to stop Oracle HTTP Server:

      opmnctl stopproc ias-component=component_name
      

      For information on stopping components, see Section 4.3.

    2. Recover the component-specific files from backup. Section 16.5 lists the directories and files needed for each component. For example, to recover Oracle HTTP Server files, you recover the following directories:

      ORACLE_INSTANCE/config/OHS/component_name
      ORACLE_INSTANCE/diagnostics/logs/OHS/component_name
      
    3. Start the component. For example, to start Oracle HTTP Server:

      opmnctl startproc ias-component=component_name
      

      For information on starting components, see Section 4.3.

18.2.7.2 Recovering a Component After Cluster Configuration Change

You can recover components in a cluster when the components cannot be started or are not functioning properly because the configuration was changed and committed at the cluster level. You may not be able to ascertain what change is causing the problem and you want to revert to an earlier version.

Caution:

Performing a domain-level recovery can impact other aspects of a running system and all of the configuration changes performed after the backup was taken will be lost.

To recover the components:

  1. Stop the cluster:

    stop('cluster_name', 'Cluster')
    
  2. Stop all processes, such as the Managed Servers and the Administration Server. For example, to stop the Administration Server on Linux:

    DOMAIN_HOME/bin/stopWeblogic.sh username password [admin_url]
    
  3. Recover the Administration Server configuration by recovering the domain home backup to a temporary location. Then, restore the config directory to the following location:

    DOMAIN_HOME/config
    
  4. Start the Administration Server. For example:

    DOMAIN_HOME/bin/startWebLogic.sh -Dweblogic.management.username=username
     -Dweblogic.management.password=password
     -Dweblogic.system.StoreBootIdentity=true
    
  5. Start the cluster. You can use the Oracle WebLogic Server Administration Console or WLST. For example, to use the WLST start command:

    start('clusterName', 'Cluster')
    

The latest configuration is retrieved from the Administration Server to every member of the cluster.

18.2.7.3 Recovering Oracle Identity Manager

To recover Oracle Identity Manager:

  1. Restore the domain, as described in Section 18.2.2.

  2. Restore the Oracle home, as described in Section 18.2.3.

  3. Restore the database containing the OIM, MDS, SOAINFRA, and the OID schemas to the same point in time. See Section 18.2.10.

    Oracle Identity Manager stores users and roles in the LDAP store. If you restore the database to a different point in time than the LDAP store, the reconciliation engine checks the change logs and reapplies all the changes that happened in the time period between the restore of the LDAP store and the database. For example, if the database is restored so that is 10 hours behind the LDAP store, the reconciliation engine checks the change logs and reapplies all the changes that happened in the last 10 hours in the LDAP store to the database.

    You do not need to explicitly trigger the reconciliation. LDAP synchronization is set up as a periodic scheduled task to submit reconciliation events periodically. You can also start the reconciliation process manually and monitor the reconciliation events from the Oracle Identity Manager console. See "Reconciliation Configuration" in Oracle Fusion Middleware User's Guide for Oracle Identity Manager.

    Note:

    Oracle recommends that you make sure that the Oracle Identity Manager application is unavailable to the end users when a bulk reconciliation is occurring (as in the above recovery scenario). When the bulk reconciliation is complete, make sure that the Oracle Identity Manager application is again available to the end users. You can monitor the reconciliation with the Oracle Identity Manager console.

18.2.7.4 Recovering Oracle Identity Navigator

To recover Oracle Identity Navigator:

  1. Restore the domain, as described in Section 18.2.2.

  2. Restore the Oracle home, as described in Section 18.2.3.

  3. Restore the file-based MDS repository, using the WLST importMetadata command. For example:

    importMetadata(application='oinav', server='server_name', fromLocation='export_directory')
    

18.2.7.5 Recovering Oracle Access Manager

To recover Oracle Access Manager:

  1. Restore the Middleware home and the domain home for the Oracle Access Manager Managed Server, as described in Section 18.2.1.

  2. Restore the domain, as described in Section 18.2.2.

  3. Restore the Oracle home for the Oracle HTTP Server that contains the WebGate, if necessary, as described in Section 18.2.3.

  4. Restore the Oracle instance for the Oracle HTTP Server that contains the WebGate, if necessary, as described in Section 18.2.4.

  5. Restore the database containing the schema used by OES for the Oracle Access Manager policy store, if necessary. See Section 18.2.10.

18.2.7.6 Recovering Oracle Adaptive Access Manager

To recover Oracle Adaptive Access Manager:

  1. Restore the domain, as described in Section 18.2.2.

  2. Restore the Oracle home, as described in Section 18.2.3.

  3. Restore the database containing the OAAM schemas, if necessary. See Section 18.2.10.

18.2.7.7 Recovering Oracle Business Process Management

To recover Oracle Business Process Management:

  1. Restore the Managed Server, as described in Section 18.2.6.

  2. Restore the Oracle homes, as described in Section 18.2.3.

18.2.7.8 Recovering Oracle WebCenter Activities Graph

To recover Oracle WebCenter Activities Graph:

  1. Restore the domain, as described in Section 18.2.2.

  2. Restore the Oracle home, as described in Section 18.2.3.

  3. Restore the database containing the ACTIVITIES schema, if necessary.

18.2.7.9 Recovering Oracle WebCenter Analytics

To recover Oracle WebCenter Analytics:

  1. Restore the domain, as described in Section 18.2.2.

  2. Restore the Oracle home, as described in Section 18.2.3.

  3. Restore the database containing the ACTIVITIES and MDS schemas, if necessary.

18.2.7.10 Recovering Oracle BI Enterprise Edition

The following topics describe how to recover Oracle BI EE:

Note:

When you recover Oracle BI EE, you must ensure that the Web Catalog and the Oracle BI EE repository (RPD) are restored to the same point in time, by using the same backup set.
18.2.7.10.1 Recovering Oracle BI Enterprise Edition in a Non-Clustered Environment

This scenario assumes that Oracle BI Enterprise Edition is running in a non-clustered environment.

  1. Restore the following, depending on the extent of the failure:

    • If the entire Middleware home is lost, restore the Middleware home, as described in Section 18.2.1.

    • If the Oracle instance home is lost, restore the Oracle instance home, as described in Section 18.2.4.

    • If the domain home is lost on the Administration Server node, restore it, as described in Section 18.2.5.

    • If the domain home is lost on the Managed Server node, restore it, as described in Section 18.2.6.

  2. Restore the database containing the Oracle BI EE schemas, if necessary. See Section 18.2.10.

  3. Reconcile the LDAP Database with the Web Catalog and the Oracle BI EE repository (RPD), as described in Section 18.2.7.10.3.

18.2.7.10.2 Recovering Oracle BI Enterprise Edition in a Clustered Environment

This scenario assumes that Oracle BI Enterprise Edition is running in a non-clustered environment. Recover the following, depending on the extent of the failure:

  1. Restore the following, depending on the extent of the failure:

    • If the entire Middleware home is lost, restore the Middleware home, as described in Section 18.2.1.

    • If the Oracle instance home is lost, restore the Oracle instance home, as described in Section 18.2.4.

    • If the domain home is lost on the Administration Server node, restore it, as described in Section 18.2.5.

    • If the domain home is lost on the Managed Server node, restore it, as described in Section 18.2.6.

  2. Recover the Administration Server, as described in Section 18.2.5.

  3. Recover the Managed Server, as described in Section 18.2.6.

  4. Restore the database containing the Oracle BI EE schemas, if necessary. See Section 18.2.10.

  5. Reconcile the LDAP Database with the Web Catalog and the Oracle BI EE repository (RPD), as described in Section 18.2.7.10.3.

18.2.7.10.3 Reconciling the LDAP Database with the Web Catalog and RPD

You must reconcile the LDAP database with the Web Catalog and the Oracle BI EE repository (RPD).

Oracle BI Enterprise Edition provides a method to perform synchronization. You can enable automatic synchronization, at all times, or temporarily to perform the synchronization.

To enable synchronization, edit the following file:

INSTANCE_HOME/config/OracleBIServerComponent/coreapplication_obis1/NQSConfig.INI 

Set the flag FMW_UPDATE_ROLE_AND_USER_REF_GUIDS to yes. Then, restart the servers. The information in the LDAP database and the Web Catalog and RPD will be synchronized.

On Windows, the Oracle BI Administration Tool provides a Consistency Check Manager that checks the validity of your repository and allows you to correct the inconsistencies. For more information, see "Checking the Consistency of Repository Objects" in the Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

18.2.7.11 Recovering Oracle Business Intelligence Publisher

To recover Oracle Business Intelligence Publisher:

  1. Recover the Managed Server containing the Oracle Business Intelligence Publisher component, as described in Section 18.2.6.

  2. Restore the database containing the Oracle Business Intelligence Publisher schemas, if necessary. See Section 18.2.10.

If backup artifacts are restored from different times, then user accounts, user reports, and user permissions will revert to the restored version. Restore all artifacts from the same point in time.

18.2.7.12 Recovering Oracle Real-Time Decisions

To recover Oracle Real-Time Decisions:

  1. Recover the Managed Server containing the Oracle Real-Time Decisions component, as described in Section 18.2.6.

Note that if backup artifacts are restored from different time, the analytic models will have missed a period of learning, but their intelligence will be unaffected.

18.2.7.13 Recovering Oracle Data Integrator

To recover Oracle Data Integrator:

  1. If the database must be restored, 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.

    cd ORACLE_HOME
    tar -xf oracle_home_backup_092010.tar 
    
  3. Recover the domain directory from backup:

    cd DOMAIN_HOME
    tar -xf domain_backup_092010.tar 
    

18.2.7.14 Recovering Oracle Information Rights Management

To recover Oracle Information Rights Management:

  1. Restore the domain, as described in Section 18.2.2.

  2. Restore the shared file system.

  3. Restore the database, if necessary. See Section 18.2.10.

    Note that the database and the keystore must be kept synchronized. If you restore one, restore the other to the same point in time.

  4. Restore the keystore.

18.2.7.15 Recovering Oracle Imaging and Process Management

Oracle Imaging and Process Management stores data in the following locations:

  • A database for Oracle I/PM configuration data

  • A database that functions as a document repository

  • JMS persistent queues

When you recover Oracle I/PM, you should ensure that all data is restored from the same point-in-time.

To recover Oracle I/PM:

  1. Restore the domain, as described in Section 18.2.2.

  2. Restore the database containing the IPM and OCS schemas, if necessary. See Section 18.2.10.

18.2.7.16 Recovering Oracle Universal Content Management

To recover Oracle Universal Content Management:

  1. If the database must be restored, restore it, as described in Section 18.3.6.

  2. Restore the domain, as described in Section 18.2.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 /net/home/vault, restore it from backup:

    cd /net/home/vault
    tar -xf vault_backup_092010.tar 
    

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.2.7.17 Recovering Oracle Universal Records Management

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.2.7.16.

18.2.8 Recovering a Cluster

The following topics describe how to recover a cluster:

18.2.8.1 Recovering a Cluster After Deletion or Cluster-Level Configuration Changes

In this scenario, the cluster has been erroneously deleted or the cluster-level configuration, such as the JMS configuration or container-level data sources, was mistakenly changed and committed. The server cannot be started or does not operate properly or the services running inside the server are not starting. You cannot ascertain what was changed.

Caution:

Performing a domain-level recovery can impact other aspects of a running system and all of the configuration changes performed after the backup was taken will be lost.

If the configuration changes are few, then the easiest way is to redo the configuration changes. If that is not feasible, use the following procedure to recover the configuration:

  1. Stop the cluster. You can use the Oracle WebLogic Server Administration Console or WLST. For example, to use WLST:

    stop('clusterName', 'Cluster')
    
  2. Stop the Administration Server. For example:

    DOMAIN_HOME/bin/stopWeblogic.sh username password [admin_url]
    
  3. Recover the Administration Server configuration by recovering the domain home backup to a temporary location. Then, restore the config directory to the following location:

    DOMAIN_HOME/config
    
  4. Start the Administration Server. For example:

    DOMAIN_HOME/bin/startWebLogic.sh -Dweblogic.management.username=username
     -Dweblogic.management.password=password
     -Dweblogic.system.StoreBootIdentity=true
    
  5. Start the cluster. You can use the Oracle WebLogic Server Administration Console or WLST. For example, to use WLST:

    start('clusterName', 'Cluster')
    

18.2.8.2 Recovering a Cluster After Membership Is Mistakenly Modified

You can recover a cluster when the cluster's membership has been mistakenly modified. For example, if you inadvertently delete a member from the cluster, you can restore the member to the cluster.

Caution:

Performing a domain-level recovery can impact other aspects of a running system and all of the configuration changes performed after the backup was taken will be lost.

To recover the cluster membership:

  1. Stop all processes, such as the Managed Servers and the Administration Server. For example, to stop the Administration Server on Linux:

    DOMAIN_HOME/bin/stopWeblogic.sh username password [admin_url]
    
  2. Recover the Administration Server configuration by recovering the domain home backup to a temporary location. Then, restore the config directory to the following location:

    DOMAIN_HOME/config
    
  3. Start the Administration Server. For example:

    DOMAIN_HOME/bin/startWebLogic.sh -Dweblogic.management.username=username
       -Dweblogic.management.password=password
       -Dweblogic.system.StoreBootIdentity=true
    

    The deleted member is now back in the cluster.

  4. Start all processes, such as the Managed Servers. For example, to start the Managed Server on Linux, use the following script:

    DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name 
              admin_url 
    
  5. Start the cluster. You can use the Oracle WebLogic Server Administration Console or WLST. For example, to use WLST:

    start('clusterName', 'Cluster')
    

    The deleted member is now part of the cluster.

  6. Start all cluster members if they are not started:

    DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url 
    

18.2.9 Recovering Applications

The following topics describe how to recover an application:

Note the following about recovering applications:

  • If the application is staged, the Administration server copies the application bits to the staged directories on the Managed Server hosts.

  • If the deployment mode is nostage or external_stage, ensure that additional application artifacts are available. For example, 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.

See Also:

Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server for information about deploying applications

18.2.9.1 Recovering Application Artifacts

If an application's artifacts, such as the .ear file, have been lost or corrupted, you can recover the application.

To recover the application:

  1. Start the Managed Server to which the application was deployed. For example:

    DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url 
    

    This synchronizes the configuration with the Administration Server.

    On each Managed Server restart, the configuration and application artifacts are retrieved from the Administration Server.

18.2.9.2 Recovering a Redeployed Application That Is No Longer Functional

If a Java EE application was redeployed to a Managed Server (whether or not the Managed Server is part of a cluster) and the application is no longer functional, you can recover it.

To recover the application:

  1. Recover the application files from backup, if needed.

  2. Redeploy the old version of the application from the backup.

    You cannot just copy the original ear file. Even if the original ear file (from the backup) is copied back to the Managed Server stage directory and you restart the Managed Server, the application is still not recovered. You must redeploy the original version.

18.2.9.3 Recovering an Undeployed Application

If a deployed application was undeployed from Oracle WebLogic Server, you can recover it.

To recover the application:

  1. Recover the application files from backup, if needed.

  2. Redeploy the old version of the application from the backup. If the application was deployed to a cluster, redeploy the application to the same cluster.

    You cannot just copy the original ear file. Even if the original ear file (from the backup) is copied back to the Managed Server stage directory and you restart the Managed Server, the application is still not recovered. You must redeploy the original version.

18.2.9.4 Recovering a Composite Application

A new version of a composite application (such as SOA application) was redeployed to a Managed Server or cluster. The application is no longer functional.

To recover the application:

  1. Recover the application files from backup, if needed.

  2. Redeploy the old version of the application. If the application was deployed to a cluster, redeploy the application to the same cluster.

18.2.10 Recovering a Database

If your database that contains your metadata repository, including the MDS Repository, is corrupted, you can recover it using RMAN. You can recover the database at the desired granularity, either a full recovery or a tablespace recovery.

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. For example:

rman> restore database;
rman> recover database;

See Appendix D for the schemas used by each component.

For detailed steps, see the Oracle Database Backup and Recovery User's Guide, which is available at:

http://www.oracle.com/technology/documentation/database.html

18.3 Recovering After Loss of Host

This section describes how to recover your Oracle Fusion Middleware environment after losing the original operating environment. For example, you could have a serious system malfunction or loss of media. The sections includes the following topics:

Note:

When you are recovering in the case of loss of host, you must restore the files using the same path as on the original host.

18.3.1 Recovering an Oracle WebLogic Server Domain

To recover an Oracle WebLogic Server domain:

  1. 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, stop the Administration Server:

    DOMAIN_HOME/bin/stopWeblogic.sh username password [admin_url]
    
  2. Recover the domain directory from backup:

    cd DOMAIN_HOME
    (UNIX) tar -xf domain_backup_092010.tar 
    (Windows) jar xtf domain_backup_092010.jar 
    
  3. Start all relevant processes. That is, start all processes that are related to the domain. For example, start the Administration Server:

    DOMAIN_HOME/bin/startWebLogic.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:

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. Attempt to start the Administration Server. For example:

    DOMAIN_HOME/bin/startWebLogic.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.

  2. If the Administration Server fails to start, take the following steps on Host A:

    1. 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_HOME/bin/stopWeblogic.sh username password [admin_url]
      
    2. Recover the Middleware home, if needed:

      tar -xf mw_home_backup_092010.tar 
      
    3. 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 
      
    4. Start the Administration Server. For example:

      DOMAIN_HOME/bin/startWebLogic.sh -Dweblogic.management.username=username
          -Dweblogic.management.password=password
          -Dweblogic.system.StoreBootIdentity=true
      
    5. Start the Managed Servers, specifying the Administration URL for the host:

      DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url 
      
    6. Start the 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 the 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_HOME/bin/startWebLogic.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_HOME/bin/startManagedWebLogic.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.

  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.

    1. Edit the following file:

      (UNIX) ORACLE_INSTANCE/EMAGENT/emagent_name/sysman/config/emd.properties
      (Windows)ORACLE_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:port/em/wallets/emd 
      REPOSITORY_URL=http://newhost.domain.com:port/em/upload/
      
    2. Shut down and restart the EM Agent process:

      cd ORACLE_INSTANCE/EMAGENT/emagent_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:

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 the Node Manager on Host B:

    java weblogic.WLST
    wls:/offline> startNodeManager()
    
  2. Start the Managed Server. For example:

    DOMAIN_HOME/bin/startManagedWebLogic.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:

    1. Stop the Node Manager:

      java weblogic.WLST
      wls:/offline> stopNodeManager()
      
    2. Recover the Middleware home to Host B from the backup, if required:

      tar -xf mw_home_backup_092010.tar 
      
    3. 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.

    4. 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_HOME/user_projects/domains/domain_name
          -template=/scratch/temp.jar -template_name=test_install 
          -template_author=myname -log=/scratch/logs/my.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=/scratch/aime1/ms.jar
          -domain=MW_HOME/user_projects/domains/domain_name 
          -log=/scratch/logs/new.log -log_priority=info
        
    5. Ensure that the application artifacts are accessible from the Managed Server host. That is, if the application artifacts are not on the same server as the Managed Server, they must be in a location accessible by the Managed Server.

      Note:

      • For applications that are deployed in nostage or external_stage mode, copy the application artifacts from the Administration Server host directory.

      • For applications that are deployed in stage mode, the Administration server copies the application bits to the staged directories on the Managed Server hosts.

      See Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server for information about deploying applications.

    6. If the Node Manager is not started, start it:

      java weblogic.WLST
      wls:/offline> startNodeManager()
      
    7. Start the Managed Server. For example:

      DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url 
      

      The Managed Server connects to the Administration Server and updates its configuration changes.

18.3.3.2 Recovering a Managed 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 B failed for some reason and the Managed Server must be recovered to Host C.

Important:

Recover the Middleware home to the same location as the original.

To recover a Managed Server to a different host:

  1. Recover the Middleware home for the Managed Server to Host C.

    tar -xf mw_home_backup_092010.tar 
    
  2. 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 4.

  3. If the Managed Server does not contain the components listed in Step 2, take the following steps:

    1. Create a domain template jar file from the Administration Server running in Host A, using the pack utility. For example:

      pack.sh -domain=MW_HOME/user_projects/domains/domain_name
        -template=/scratch/temp.jar -template_name=test_install 
        -template_author=myname -log=/scratch/logs/my.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.

    2. Unpack the domain template jar file on Host C, using the unpack utility:

      unpack.sh -template=/scratch/aime1/ms.jar
         -domain=MW_HOME/user_projects/domains/domain_name
         -log=/scratch/logs/new.log -log_priority=info
      

      If you are recovering to a different domain home, use the -app_dir switch in the unpack command.

  4. Ensure that the application artifacts are accessible from the Managed Server host. That is, if the application artifacts are not on the same server as the Managed Server, they must be in a location accessible by the Managed Server.

    Note:

    • For applications that are deployed in nostage or external_stage mode, copy the application artifacts from the Administration Server host directory.

    • For applications that are deployed in stage mode, the Administration server copies the application bits to the staged directories on the Managed Server hosts.

    See Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server for information about deploying applications.

  5. Start the Node Manager on Host C, if it is not started:

    java weblogic.WLST
    wls:/offline> startNodeManager()
    
  6. Using WLST, connect to the Administration Server and then enroll the Node Manager running in the new host with the Administration Server:

    connect('username','password','http://host:port')
    nmEnroll('MW_HOME/user_projects/domains/domain_name',
      'MW_HOME/wlserver_n/common/nodemanager')
    
  7. Change the Managed Server configuration to point to the new host:

    1. In the WebLogic Server Administration Console, create a machine, which is a logical representation of the computer that hosts one or more WebLogic Servers, and point it to the new host. (From the Home page, select Machines. Then, click New.) Follow the directions in the Administration Console help.

      If you identify the Listen Address by IP address, you must disable Host Name Verification on the Administration Servers that access Node Manager. For more information and instructions, see "Using Hostname Verification" in Oracle Fusion Middleware Securing Oracle WebLogic Server.

    2. Change the Managed Server configuration to point to the new machine. (From the left pane of the Console, expand Environment and then Servers. Then, select the name of the server. Select the Configuration tab, then the General tab. In the Machine field, select the machine to which you want to assign the server.)

      Change Listen Address to the new host. (If the listening address was set to blank, you do not need to change it.)

  8. Start the Managed Server. For example:

    DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url 
    

    The Managed Server connects to the Administration Server and updates its configuration changes.

  9. Update Oracle Inventory, as described in Section 18.3.5.7.

  10. If your environment contains Oracle HTTP Server, modify the mod_wl_ohs.conf file, as described in Section 18.3.5.4.

  11. Edit the targets.xml file for Fusion Middleware Control, as described in Section 18.3.5.2.

Now you can start and stop the Managed Server on Host C using the Administration Server running on Host A.

18.3.3.3 Recovering an Oracle SOA Suite Managed Server That Has a Separate Directory

When Oracle SOA Suite is configured in a domain and no Managed Servers share the domain directory with the Administration Server, you must restore the Managed Server directory. For example, a domain contains two Managed Servers, one of which contains Oracle SOA Suite, but neither of the Managed Server's directories are in the same directory structure as the Administration Server.

To recover to the same host or a different host, use the procedures in Section 18.2.6.3.

18.3.4 Recovering After Loss of Component Host

If you lose a host that contains a component (and its Managed Server, if applicable), you can recover most components to the same host or a different host using the procedures described in the following topics:

Some components require additional actions, which are described in the sections listed in Table 18-2.

Table 18-2 Recovery Procedures for Loss of Host for Particular Components

Component Procedure

Oracle Access Manager

Section 18.3.4.5.7

Oracle Adaptive Access Manager

Section 18.3.4.5.8

Oracle BI Discoverer

Section 18.3.4.8.4

Oracle BI Enterprise Edition

Section 18.3.4.9

Oracle BI Publisher

Section 18.3.4.10

Oracle Business Process Management

No additional steps needed for loss of host. See Section 18.2.7.7 for information about recovering Oracle Business Process Management.

Oracle Data Integrator

Section 18.3.4.12

Oracle Directory Integration Platform

Section 18.3.4.5.3

Oracle Forms Services

Section 18.3.4.8.2

Oracle HTTP Server

Section 18.3.4.7.1

Oracle Identity Federation

Section 18.3.4.5.4

Oracle Identity Manager

Section 18.3.4.5.5

Oracle Identity Navigator

Section 18.3.4.5.6

Oracle Imaging and Process Management

No additional steps needed for loss of host. See Section 18.2.7.15 for information about recovering Oracle Imaging and Process Management.

Oracle Information Rights Management

No additional steps needed for loss of host. See Section 18.2.7.14 for information about recovering Oracle Information Rights Management.

Oracle Internet Directory

Section 18.3.4.5.1

Oracle Portal

Section 18.3.4.8.1

Oracle Real-Time Decisions

Section 18.3.4.11

Oracle Reports

Section 18.3.4.8.3

Oracle SOA Suite

No additional steps needed if recovering to the same host. See Section 18.3.4.6 for information about recovering to a different host.

Oracle Universal Content Management

Section 18.3.4.13.1

Oracle Universal Records Management

Section 18.3.4.13.2

Oracle Virtual Directory

Section 18.3.4.5.2

Oracle Web Cache

Section 18.3.4.7.2

Oracle WebCenter Activity Graph

No additional steps needed for loss of host. See Section 18.2.7.8 for information about recovering Oracle WebCenter Activity Graph.

Oracle WebCenter Analytics

No additional steps needed for loss of host. See Section 18.2.7.9 for information about recovering Oracle WebCenter Analytics.


18.3.4.1 Recovering a Java Component to the Same Host

To recover a Java component to the same host, such as Oracle SOA Suite:

  1. Recover the Managed Server, as described in Section 18.2.6.1.

  2. If the component requires additional steps, as noted in Table 18-2, take those steps.

18.3.4.2 Recovering a Java Component to a Different Host

To recover a Java component to a different host, such as Oracle SOA Suite:

  1. Recover the Managed Server, as described in Section 18.3.3.2.

  2. Edit the targets.xml file for Fusion Middleware Control, as described in Section 18.3.5.2.

However, note that some components require additional steps, as noted in Table 18-2.

18.3.4.3 Recovering a System Component to the Same Host

To recover a system component, such as Oracle HTTP Server, to the same host, you take the following general steps. However, note that some components require additional steps, as noted in Table 18-2.

  1. Stop all relevant processes. That is, stop all processes that are related to the component. For example, to stop Oracle HTTP Server:

    opmnctl stopproc ias-component=component_name
    

    For information on stopping components, see Section 4.3.

  2. Recover the component-specific files from backup. Section 16.5 lists the directories and files needed for each component. For example, to recover Oracle HTTP Server files, you recover the following directories:

    ORACLE_INSTANCE/config/OHS/component_name
    ORACLE_INSTANCE/diagnostics/logs/OHS/component_name
    
  3. If the Oracle instance home has been deregistered from the Administration Server, register the Oracle instance:

    opmnctl registerinstance -adminHost admin_server_host 
         -adminPort admin_server_port -adminUsername username 
         -adminPassword password
         -wlserverHome wlserver_home_location 
    

    If only the file system is being recovered, you do not need to register the Oracle instance.

  4. Start all relevant processes, as described in Section 4.3.

18.3.4.4 Recovering a System Component to a Different Host

To recover a system component, such as Oracle HTTP Server, to a different host, you take the following general steps. However, note that most components require additional steps, as noted in Table 18-2.

  1. Recover the Middleware home, as described in Section 18.2.1.

  2. Start all relevant processes. Section 4.3 explains how to start components.

  3. Update the registration of the Oracle instance with the Administration Server, using the opmnctl updateinstanceregistration command on the new host. For example:

    opmnctl updateinstanceregistration -adminHost admin_server_host 
    

    This command updates OPMN's instance.properties file.

  4. Update the registration of the component with the Administration Server, using the opmnctl updatecomponentregistration command on the new host. For example, to update the registration for Oracle Virtual Directory, use the following command:

    opmnctl updatecomponentregistration -Host new_host -Port nonSSLPort
        -componentName ovd1 -componentType OVD
    
  5. Edit the targets.xml file for Fusion Middleware Control, as described in Section 18.3.5.2.

18.3.4.5 Recovering Identity Management Components to a Different Host

For most Identity Management components, you recover the Managed Server, as described in Section 18.3.3.2.

Some components require additional steps to recover the components to a different host, as described in the following topics:

18.3.4.5.1 Recovering Oracle Internet Directory to a Different Host

To recover Oracle Internet Directory to a different host:

  1. Recover the component as described in Section 18.3.4.4.

  2. On UNIX and Linux systems, before you attempt to start Oracle Internet Directory, set the following file to have root permission:

    ORACLE_HOME/bin/oidldapd
    

    For example:

    chown root oidldapd
    chmod 4710 oidldapd
    
  3. Recover Oracle Management Agent, as described in Section 18.3.5.3.

  4. If the Managed Server on which Oracle Directory Services Manager is deployed is moved to different host and if SSL is enabled, you must delete the following file on the new host:

    DOMAIN_HOME/servers/wls_ods1/tmp/_WL_user/odsm_11.1.1.1.0/randomid/war/conf/odsm.cer
    

    Oracle Directory Services Manager uses this file as its keystore and trust store and the password is stored in JKS. However, when Oracle Directory Services Manager is copied to another host and is started, it generates a different password. If you delete the file, Oracle Directory Services Manager creates a new file when it starts, with the new password.

18.3.4.5.2 Recovering Oracle Virtual Directory to a Different Host

To recover Oracle Virtual Directory to a different host:

  1. Recover the component as described in Section 18.3.4.4.

  2. Recover Oracle Management Agent, as described in Section 18.3.5.3.

18.3.4.5.3 Recovering Oracle Directory Integration Platform to a Different Host

To recover Oracle Directory Integration Platform to a different host:

  1. Recover the Managed Server, as described in Section 18.3.3.2.

  2. Before starting the Managed Server, restore the files in the following directory:

    DOMAIN_HOME/servers/wls_ods1/stage/DIP/11.1.1.1.0/
    
  3. Start the Managed Servers and Oracle instances.

  4. If Oracle Internet Directory is also moved to a different host, execute the following commands immediately after the Managed Server and the Oracle instance are started:

    set ORACLE_HOME Oracle_home_path
    set WLS_HOME WLS_Home_path
    cd ORACLE_HOME/bin
    ./manageDIPServerConfig set -h dip_server_host -p dip_server_port 
        -D weblogic_user -attribute oidhostport -value oid_host:oid_ssl_port
    

    The manageDIPServerConfig command prompts you for a password.

    For example:

    ./manageDIPServerConfig set -h hostname -p 19523 -D weblogic
                -attribute oidhostport -value hostname.domain.com:24163 
    
  5. Register the Oracle instance, along with all of its components, with the Administration Server, using the opmnctl registerinstance command on the new host. For example:

    opmnctl registerinstance -adminHost admin_server_host 
         -adminPort admin_server_port -adminUsername username 
         -adminPassword password
         -wlserverHome wlserver_home_location 
    
18.3.4.5.4 Recovering Oracle Identity Federation to a Different Host

Because Oracle Identity Federation provides SSO functionality, if the host name on which Oracle Identity Federation runs is changed as part of loss of host recovery, it impacts remote partners. In that case, remote partners must make changes regarding the host name to continue to operate. It may take many days for remote partners to update their data and this may cause production delays that are unacceptable. Oracle strongly recommends that you do not change the host name of a standalone Oracle Identity Federation server.

If a load balancer is part of the environment and the host where Oracle Identity Federation is being recovered is in the list of VIPs, then no host name changes are required.

In the case of a standalone installation of Oracle Identity Federation, Oracle recommends using a new host with the same name to minimize the impact. However, if, for whatever reason, you must use a different host name for recovering Oracle Identity Federation, then the host name must be updated manually for Oracle Identity Federation and remote partners.

To recover Oracle Identity Federation to a different host:

  1. Recover the Managed Server, as described in Section 18.3.3.2.

  2. Recover Oracle Management Agent, as described in Section 18.3.5.3.

  3. Register the Oracle instance, along with all of its components, with the Administration Server, using the opmnctl registerinstance command on the new host. For example:

    opmnctl registerinstance -adminHost admin_server_host 
         -adminPort admin_server_port -adminUsername username 
         -adminPassword password
         -wlserverHome wlserver_home_location 
    
  4. Provide the updated data to remote partners.

  5. Modify the host name using Fusion Middleware Control:

    1. In the navigation pane, expand the farm and then Identity and Access.

    2. Select the Oracle Identity Federation instance.

    3. From the Oracle Identity Federation menu, choose Administration, then Server Properties.

      The Server Properties page is displayed.

    4. For Host, replace the old host name with the new host name.

    5. For Port, replace the port number if it has changed.

    6. For SOAP Port, replace the port number if it has changed.

    7. Click Apply.

    8. Restart the Managed Server to which Oracle Identity Federation is deployed:

      DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name 
                admin_url 
      
  6. If Oracle Identity Federation is acting as an SSL server, you must replace the SSL certificate presented by Oracle Identity Federation to clients with a new one that has the new host name. Otherwise, host name verification by clients may fail.

18.3.4.5.5 Recovering Oracle Identity Manager to a Different Host

To recover Oracle Identity Manager to a different host:

  1. Restore the domain, as described in Section 18.3.2.

  2. Restore the Oracle home, as described in Section 18.2.3.

  3. Restore the database containing the OIM, OID, MDS, and SOAINFRA schemas, if necessary. See Section 18.2.10.

  4. Synchronize the Oracle Identity Manager database and the LDAP provider. See the Oracle Fusion Middleware Command Reference for Oracle WebLogic Server for more information.

  5. Export the oim-config.xml file, using the weblogicExportMetadata.sh script. Then, edit the file, changing the host name or IP address for the SOA URL. Import the file into MDS, using the weblogicImportMetadata.sh script.

  6. Create a new machine with the new host name, as described in Section 18.3.5.5.

  7. Reassociate the weblogic user with any groups, as described in Section 18.3.5.6.

18.3.4.5.6 Recovering Oracle Identity Navigator to a Different Host

To recover Oracle Identity Navigator to a different host:

  1. Create a new machine with the new host name, as described in Section 18.3.5.5.

  2. Reassociate the weblogic user with any groups, as described in Section 18.3.5.6.

18.3.4.5.7 Recovering Oracle Access Manager to a Different Host

To recover Oracle Access Manager to a different host:

  1. Follow the instructions in Section 18.2.7.5.

  2. To restore the WLS Agent, restore the Managed Server, as described in Section 18.3.3.2.

  3. Log into the Oracle Access Manager console.

  4. Select the Oracle Access Manager proxy server.

  5. Modify Host, specifying the new host name.

  6. If you have protected pages, you must reregister Oracle Single Sign-On or WebGate as partners with Oracle Access Manager, using the oamreg tool, described in "About the Remote Registration Tool" in the Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager. Also see "OSSO Remote Registration Request" in the same manual.

  7. Create a new machine with the new host name, as described in Section 18.3.5.5.

  8. Edit the WebGate configuration file, obAccessClient.xml, to update the host name for the Oracle Access Manager server. The file is located in the following directory:

    DOMAIN_HOME/output/agentName/
    
  9. Reassociate the weblogic user with any groups, as described in Section 18.3.5.6.

18.3.4.5.8 Recovering Oracle Adaptive Access Manager to a Different Host

To recover Oracle Adaptive Access Manager to a different host:

  1. Follow the instructions in Section 18.2.7.6.

  2. Create a new machine with the new host name, as described in Section 18.3.5.5.

  3. Reassociate the weblogic user with any groups, as described in Section 18.3.5.6.

18.3.4.6 Recovering Oracle SOA Suite After Loss of Host

Note that when Oracle SOA Suite is configured in a domain and no Managed Servers share the domain directory with the Administration Server, take the steps described in Section 18.3.3.3. Otherwise, follow the steps in this section.

To recover the Oracle SOA Suite Managed Server to the same host, recover the Managed Server, as described in Section 18.3.3.1.

To recover the Oracle SOA Suite Managed Server to a different host after loss of host:

  1. Before you recover, update the WSDL file to point to the new host name and port.

  2. Recover the Managed Server, as described in Section 18.3.3.2.

  3. After you recover the Oracle SOA Suite Managed Server, take the following actions:

    • If the ant command is used to deploy composites, edit the deploy-sar.xml file, which is located in:

      (UNIX) ORACLE_HOME/bin
      (Windows) ORACLE_HOME\bin
      

      In the following line, replace the previous host name with the new host name:

      <property name="wlsHost" value="newhostname"/> 
      

      If a Load Balancer is used, do not modify this property. Instead, register the new host with the Load Balancer.

    • Change the host name in the soa-infra MBean:

      1. In Fusion Middleware Control, navigate to the Managed Server.

      2. From the WebLogic Server menu, choose System MBean Browser.

      3. Expand Application Defined MBeans, then oracle.as.soainfra.config, then Server: server_name and then SoaInfraConfig. Select soa-infra.

      4. In the Attributes tab, click ServerURL. If the ServerURL attribute contains a value, change the host name to the new host name.

      5. Click Apply.

    • Redeploy all applications which have the WSDL files updated to the new host name.

Note:

If there is no Load Balancer configured with the environment and Oracle SOA Suite must be recovered to a different host, then in-flight instances that are pending a response from task flow and asynchronous responses are not recovered. Oracle recommends that you use a Load Balancer to ensure that you can recover to a different host.

If a Load Balancer is configured with the environment, take the following additional steps:

  1. Log in to the Oracle WebLogic Server Administration Server.

  2. In Domain Structure, navigate to Servers. For each Managed Server, select the Protocol tab, then the HTTP tab.

  3. For Frontend Host, enter the new host name.

  4. For Frontend HTTP Port and Frontend HTTPs Port, if applicable, enter the new port number.

  5. Restart each Managed Server.

18.3.4.7 Recovering Web Tier Components to a Different Host

The Web tier consists of Oracle HTTP Server and Oracle Web Cache. The following topics describe how to recover these components to a different host:

18.3.4.7.1 Recovering Oracle HTTP Server to a Different Host

To recover Oracle HTTP Server to a different host:

  1. Recover the component as described in Section 18.3.4.4.

  2. Recover Oracle Management Agent, as described in Section 18.3.5.3.

  3. Modify the ServerName entry in the following file to have the new host name:

    (UNIX) ORACLE_INSTANCE/config/OHS/ohs_name/httpd.conf
    (Windows) ORACLE_INSTANCE\config\OHS\ohs_name\httpd.conf
    
18.3.4.7.2 Recovering Oracle Web Cache to a Different Host

To recover Oracle Web Cache to a different host:

  1. Recover the component as described in Section 18.3.4.4.

  2. Recover Oracle Management Agent, as described in Section 18.3.5.3.

  3. Edit the webcache.xml file, replacing the previous host name with the new host name. The file is located in:

    (UNIX) ORACLE_INSTANCE/config/WebCache/webcache_name
    (Windows) ORACLE_INSTANCE\config\WebCache\webcache_name
    

18.3.4.8 Recovering Oracle Portal, Oracle Reports, Oracle Forms Services, and Oracle Business Intelligence Discoverer to a Different Host

The following topics describe how to recover these components to a different host:

18.3.4.8.1 Recovering Oracle Portal to a Different Host

To recover Oracle Portal to a different host:

  1. Restore the Middleware home, the domain directory, and the Oracle instance directory to the new host. See Section 18.3.3.2 for more information.

  2. Recover Oracle Management Agent, as described in Section 18.3.5.3.

  3. If the instance has been deregistered, register the Oracle instance, along with all of its components, with the Administration Server, using the opmnctl registerinstance command on the new host. For example:

    opmnctl registerinstance -adminHost admin_server_host 
         -adminPort admin_server_port -adminUsername username 
         -adminPassword password
         -wlserverHome wlserver_home_location 
    
  4. Update the registration of the Oracle instance with the Administration Server, using the opmnctl updateinstanceregistration command on the new host. For example:

    opmnctl updateinstanceregistration -adminHost admin_server_host 
    

    This command updates OPMN's instance.properties file.

  5. Modify the following files, replacing the old host name with the new host name:

    ORACLE_INSTANCE/config/OHS/ohs_name/httpd.conf
    ORACLE_INSTANCE/config/OHS/ohs_name/moduleconf/portal.conf
    
  6. Run the ssoreg script, which is located in:

    Identity_Management_ORACLE_HOME/sso/bin
    

    Use the following command:

    ssoreg.sh -site_name newhost:http_listen_port 
        -mod_osso_url http://newhost:http_listen_port -config_mod_osso TRUE
        -oracle_home_path $ORACLE_HOME -config_file any_new_file_path
        -admin_info cn=orcladmin -virtualhost -remote_midtier
    

    For example:

    ssoreg.sh -site_name example.com:8090 
       -mod_osso_url http://example.com:8090 -config_mod_osso TRUE 
       -oracle_home_path $ORACLE_HOME -config_file /tmp/loh_osso.conf  
       -admin_info cn=orcladmin -virtualhost -remote_midtier
    
  7. Copy the file from the previous step to the new host.

  8. In the new host, modify the OssoConfigFile section in the following file to include the path of the file in step 6:

    ORACLE_INSTANCE/config/OHS/ohs1/moduleconf/mod_osso.conf
    

    For example:

    <IfModule mod_osso.c>
        OssoIpCheck off
        OssoSecureCookies off
        OssoIdleTimeout off
        OssoConfigFile /tmp/path_of_file_created
    
  9. Edit the following files, replacing the previous host name with the new host name:

    • webcache.xml. This file is located in:

      (UNIX) ORACLE_INSTANCE/config/WebCache/webcache_name
      (Windows) ORACLE_INSTANCE\config\WebCache\webcache_name
      

      Replace all occurrences of the previous host name with the new host name.

    • instance.properties. The file is located in:

      (UNIX) ORACLE_INSTANCE/config/OPMN/opmn
      (Windows) ORACLE_INSTANCE\config\OPMN\opmn
      

      In the following line, replace the previous host name with the new host name if the Administration Server host name has changed.

      adminHost=host_name
      
  10. If the published host used to access Oracle Portal is changing, take the following steps. This could happen if you have a single node install which contains both Oracle Web Cache and WLS_PORTAL, and those processes need to move to a different host. Another scenario is when you have Oracle Web Cache running on a node remotely from WLS_PORTAL, and Oracle Web Cache must move to a different host. In both these cases, take the following steps to update the Published Host information within Oracle Portal. (Note: If you have a load balancer or reverse proxy configuration, the steps are not needed.)

    1. Recursively delete all content from the following directory, but do not delete the directory itself:

      ORACLE_INSTANCE/portal/cache
      
    2. Log in to Fusion Middleware Control. Expand the farm and right-click Portal. Then, choose Settings, then Wire Configuration.

    3. In the Portal Midtier section, update Published Host with the new host name.

    4. In the Oracle Web Cache section, update Host with the new host name.

  11. Restart the WLS_PORTAL instance.

18.3.4.8.2 Recovering Oracle Forms Services to a Different Host

To recover Oracle Forms Services to a different host:

  1. Recover the Managed Server as described in Section 18.3.3.2.

  2. Recover Oracle Management Agent, as described in Section 18.3.5.3.

  3. Register the Oracle instance, along with all of its components, with the Administration Server, using the opmnctl registerinstance command on the new host. For example:

    opmnctl registerinstance -adminHost admin_server_host 
         -adminPort admin_server_port -adminUsername username 
         -adminPassword password
         -wlserverHome wlserver_home_location 
    
  4. Edit the following files, replacing the previous host name with the new host name:

    • webcache.xml. This file is located in:

      (UNIX) ORACLE_INSTANCE/config/WebCache/webcache_name
      (Windows) ORACLE_INSTANCE\config\WebCache\webcache_name
      

      Replace all occurrences of the previous host name with the new host name.

    • instance.properties. The file is located in:

      (UNIX) ORACLE_INSTANCE/config/OPMN/opmn
      (Windows) ORACLE_INSTANCE\config\OPMN\opmn
      

      In the following line, replace the previous host name with the new host name if the Administration Server host name has changed.

      adminHost=host_name
      
    • forms.conf. The file is located in:

      (UNIX) ORACLE_INSTANCE/config/OHS/ohs_name/moduleconf
      (Windows) ORACLE_INSTANCE\config\OHS\ohs_name\moduleconf
      

      Replace the host name in the parameter WebLogicHost with the name of the new host.

  5. On the Administration Server host, edit the following file:

    DOMAIN_HOME/opmn/topology.xml
    

    Add properties for the <ias-component id> element for Oracle Forms Services. The following example shows the element after you modify it:

    </ias-component>
      <ias-component id="forms" type="FormsComponent" >
      <em-properties>
          <property name="OracleHome" value="/path_to_oracle_home" />
          <property name="instName" value="instance_name" />
          <property name="EMTargetType" value="oracle_forms" />
          <property name="version" value="11.1.1" />
      </em-properties>
     </ias-component>
    
  6. On the host where the Oracle instance has been recovered, update the registration of the component with the Administration Server, using the opmnctl updatecomponentregistration command on the new host.

    For example:

    opmnctl updatecomponentregistration -Host new_host -Port nonSSLPort
        -componentName forms -componentType FormsComponent
    
  7. Run the ssoreg script, which is located in:

    Identity_Management_ORACLE_HOME/sso/bin
    

    Use the following command:

    ssoreg.sh -site_name newhost:http_listen_port 
        -mod_osso_url http://newhost:http_listen_port -config_mod_osso TRUE
        -oracle_home_path $ORACLE_HOME -config_file any_new_file_path
        -admin_info cn=orcladmin -virtualhost -remote_midtier
    

    For example:

    ssoreg.sh -site_name example.com:8090 
       -mod_osso_url http://example.com:8090 -config_mod_osso TRUE 
       -oracle_home_path $ORACLE_HOME -config_file /tmp/loh_osso.conf  
       -admin_info cn=orcladmin -virtualhost -remote_midtier
    
  8. Copy the file from the previous step to the new host.

  9. In the new host, modify the OssoConfigFile section in the following file to include the path of the file in step 7:

    ORACLE_INSTANCE/config/OHS/ohs1/moduleconf/mod_osso.conf
    

    For example:

    <IfModule mod_osso.c>
        OssoIpCheck off
        OssoSecureCookies off
        OssoIdleTimeout off
        OssoConfigFile /tmp/path_of_file_created
    
18.3.4.8.3 Recovering Oracle Reports to a Different Host

To recover Oracle Reports to a different host:

  1. Recover the Managed Server as described in Section 18.3.3.2.

  2. Recover Oracle Management Agent, as described in Section 18.3.5.3.

  3. Register the Oracle instance, along with all of its components, with the Administration Server, using the opmnctl registerinstance command on the new host. For example:

    opmnctl registerinstance -adminHost admin_server_host 
         -adminPort admin_server_port -adminUsername username 
         -adminPassword password
         -wlserverHome wlserver_home_location 
    
  4. Edit the following files, replacing the previous host name with the new host name:

    • reports_install.properties. The file is located in:

      (UNIX) ORACLE_INSTANCE/reports
      (Windows) ORACLE_INSTANCE\reports
      

      Edit the parameters SERVER_NAME, OHS_HOST and REPORTS_MANAGED_WLS_HOST.

    • webcache.xml. This file is located in:

      (UNIX) ORACLE_INSTANCE/config/WebCache/webcache_name
      (Windows) ORACLE_INSTANCE\config\WebCache\webcache_name
      

      Replace all occurrences of the previous host name with the new host name.

    • instance.properties. The file is located in:

      (UNIX) ORACLE_INSTANCE/config/OPMN/opmn
      (Windows) ORACLE_INSTANCE\config\OPMN\opmn
      

      In the following line, replace the previous host name with the new host name if the Administration Server host name has changed.

      adminHost=host_name
      
    • reports_ohs.conf. The file is located in:

      (UNIX) ORACLE_INSTANCE/config/OHS/ohs_name/moduleconf
      (Windows) ORACLE_INSTANCE\config\OHS\ohs_name\moduleconf
      
    • rwservlet.properties. The file is located in:

      (UNIX) DOMAIN_HOME/config/fmwconfig/servers/server_name/applications/reports_version/configuration
      (Windows) DOMAIN_HOME\config\fmwconfig\servers\server_name\applications\reports_version\configuration
      

      In the file, modify the <server> element to use the new host name.

  5. In the following directory, rename the subdirectory to have the new host name:

    (UNIX) ORACLE_INSTANCE/diagnostics/logs/ReportsServer
    (Windows) ORACLE_INSTANCE\diagnostics\logs\ReportsServer
    
  6. In the following directory, rename the old_host_name.dat file to the new host name:

    (UNIX) ORACLE_INSTANCE/reports/server
    (Windows) ORACLE_INSTANCE\reports\server
    
  7. In the following directory, rename the subdirectory to have the new host name:

    (UNIX) ORACLE_INSTANCE/config/ReportsServer
    (Windows) ORACLE_INSTANCE\config\ReportsServer
    
  8. Run the ssoreg script, which is located in:

    Identity_Management_ORACLE_HOME/sso/bin
    

    Use the following command:

    ssoreg.sh -site_name newhost:http_listen_port 
        -mod_osso_url http://newhost:http_listen_port -config_mod_osso TRUE
        -oracle_home_path $ORACLE_HOME -config_file any_new_file_path
        -admin_info cn=orcladmin -virtualhost -remote_midtier
    

    For example:

    ssoreg.sh -site_name example.com:8090 
       -mod_osso_url http://example.com:8090 -config_mod_osso TRUE 
       -oracle_home_path $ORACLE_HOME -config_file /tmp/loh_osso.conf  
       -admin_info cn=orcladmin -virtualhost -remote_midtier
    
  9. Copy the file from the previous step to the new host.

  10. In the new host, modify the OssoConfigFile section in the following file to include the path of the file in step 8:

    ORACLE_INSTANCE/config/OHS/ohs1/moduleconf/mod_osso.conf
    

    For example:

    <IfModule mod_osso.c>
        OssoIpCheck off
        OssoSecureCookies off
        OssoIdleTimeout off
        OssoConfigFile /tmp/path_of_file_created
    
  11. In the following file, replace occurrences of the host name with the new host name:

    (UNIX) DOMAIN_HOME/servers/server_name/tmp/_WL_user/reports_version/random_string/META-INF/mbeans.xml
    (Windows) DOMAIN_HOME\servers\server_name\tmp\_WL_user\reports_version\random_string\META-INF\mbeans.xml
    
  12. In the following file, replace occurrences of the host name with the new host name:

    ORACLE_INSTANCE/EMAGENT/emagent_<instanceName>/sysman/emd/targets.xml
    

    You change the host name in the elements beginning with the following:

    <Target TYPE="oracle_repapp" ..>
    <Target TYPE="oracle_repserv" ..>
    
18.3.4.8.4 Recovering Oracle Business Intelligence Discoverer to a Different Host

To recover Oracle Business Intelligence Discoverer to a different host:

  1. Recover the Managed Server as described in Section 18.3.3.2.

  2. Recover Oracle Management Agent, as described in Section 18.3.5.3.

  3. Register the Oracle instance, along with all of its components, with the Administration Server, using the opmnctl registerinstance command on the new host. For example:

    opmnctl registerinstance -adminHost admin_server_host 
         -adminPort admin_server_port -adminUsername username 
         -adminPassword password
         -wlserverHome wlserver_home_location 
    
  4. Edit the following files, replacing the previous host name with the new host name:

    • module_disco.conf. This file is located in:

      (UNIX) ORACLE_INSTANCE/config/OHS/ohs_name//moduleconf
      (Windows) ORACLE_INSTANCE\config\OHS\ohs_name\moduleconf
      
    • webcache.xml. This file is located in:

      (UNIX) ORACLE_INSTANCE/config/WebCache/webcache_name
      (Windows) ORACLE_INSTANCE\config\WebCache\webcache_name
      

      Replace all occurrences of the previous host name with the new host name.

  5. Run the ssoreg script, which is located in:

    Identity_Management_ORACLE_HOME/sso/bin
    

    Use the following command:

    ssoreg.sh -site_name newhost:http_listen_port 
        -mod_osso_url http://newhost:http_listen_port -config_mod_osso TRUE
        -oracle_home_path $ORACLE_HOME -config_file any_new_file_path
        -admin_info cn=orcladmin -virtualhost -remote_midtier
    

    For example:

    ssoreg.sh -site_name example.com:8090 
       -mod_osso_url http://example.com:8090 -config_mod_osso TRUE 
       -oracle_home_path $ORACLE_HOME -config_file /tmp/loh_osso.conf  
       -admin_info cn=orcladmin -virtualhost -remote_midtier
    
  6. Copy the file from the previous step to the new host.

  7. In the new host, modify the OssoConfigFile section in the following file to include the path of the file in step 5:

    ORACLE_INSTANCE/config/OHS/ohs1/moduleconf/mod_osso.conf
    

    For example:

    <IfModule mod_osso.c>
        OssoIpCheck off
        OssoSecureCookies off
        OssoIdleTimeout off
        OssoConfigFile /tmp/path_of_file_created
    

18.3.4.9 Recovering Oracle BI Enterprise Edition to a Different Host

You can recover Oracle BI Enterprise Edition to a different host, but the new host must have the same name as the original host.

Note:

You cannot recover Oracle BI EE or any other component which is co-located with Oracle BI EE to a new host that has a new host name. You can only recover Oracle BI EE and other components to a new host with the same host name as the original host. For example, if Oracle BI EE is co-located with Oracle Real-Time Decisions and Oracle Business Intelligence Publisher, none of these components can be recovered to a new host with different host name.

The following topics describe how to move Oracle BI EE to a different host with the same name:

18.3.4.9.1 Recovering Oracle BI Enterprise Edition to a Different Host in a Non-Clustered Environment

The steps you take to recover Oracle BI EE to a different host depends on the operating system:

  • On UNIX, take the following steps:

    1. Restore the Middleware home, as described in Section 18.2.1.

    2. Restore the database containing the Oracle BI EE schemas, if necessary. See Section 18.3.6.

  • On Windows, take the following steps:

    1. Restore the Middleware home from backup, as described in Section 18.2.1, overwriting the Middleware home that you created with the new installation.

    2. Restore the database containing the Oracle BI EE schemas, if necessary. See Section 18.3.6.

    3. Install the C++ libraries from Microsoft, by executing the following file:

      Oracle_BI\bifoundation\install\vc80\vcredist_x86.exe
      
    4. Import the Registry entries that you exported into the new host, as described in Section 18.3.4.9.4.

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

In this scenario, you have an Oracle BI EE cluster on two hosts, Host A and Host B. Host A must be replaced for some reason, such as losing the original operating system, and you must recover to Host C.

Take the following steps:

  1. Restore the Middleware home from backup to Host C, as described in Section 18.2.1.

  2. Restore the database containing the Oracle BI EE schemas, if necessary. See Section 18.3.6.

  3. On Windows, install the C++ libraries from Microsoft, by executing the following file:

    Oracle_BI\bifoundation\install\vc80\vcredist_x86.exe
    
  4. On Windows, import the Registry entries that you exported into the new host, as described in Section 18.3.4.9.4.

  5. If the failed node contained the Administration Server, recover it, as described in steps 1 through 5 in Section 18.3.2.2.

  6. Scale out the Oracle BI EE system, as described in "Scaling Out the BI System on APPHOST2" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

    When you enter the directory specifications for the Domain Home and Applications Home, enter specifications for directories that do not yet exist or that are empty.

  7. Scale out the system components, as described in "Scaling Out the System Components" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

    Because instance1 on Host A is no longer available, you must modify its count of BI Servers, Presentation Servers, and JavaHosts to be 0.

    Then, instance2 on Host B automatically becomes the primary instance. The new instance on Host C, instance3, becomes the secondary instance.

  8. The Oracle BI Cluster Controllers and Oracle BI Scheduler are singleton components that operate in active/passive mode. Configure a secondary instance of these components so that they are distributed for high availability, as described in "Configuring Secondary Instances of Singleton System Components" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

  9. Set the listen address of the bi_servern Managed Server, as described in "Setting the Listen Address for the bi_server2 Managed Server" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

  10. Disable host name verification for the bi_servern Managed Server, as described in "Disabling Host Name Verification for the bi_server2 Managed Server" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

  11. Depending on your configuration, perform additional configuration, as described in "Performing Additional Configuration for Oracle Business Intelligence Availability" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

  12. If Oracle HTTP Server is installed, set the frontend HTTP host and port for the Oracle WebLogic Server cluster to ensure that Oracle BI Search URLs are set correctly, as described in "Setting the Frontend HTTP Host and Port" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

  13. Configure Node Manager for the Managed Servers as described in "Configuring Node Manager for the Managed Servers" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

  14. Start the Oracle BI EE Managed Server and all of the OPMN-managed components.

18.3.4.9.3 Additional Steps for Recovering Oracle BI EE

Depending on your environment, you may need to take additional steps after you perform the steps in Section 18.3.4.9.2:

  • If the failed host contained the master BI Server, primary cluster controller, and primary Oracle BI Scheduler and you want the new instance to be the master BI Server, take the following steps as appropriate. Note that if you want to leave instance2 as the master BI server, you do not need to take these additional steps.

    • If the master BI Server is lost:

      1. Stop Oracle WebLogic Server and OPMN processes on all nodes.

      2. Update the following configuration file to designate a new master BI Server:

        INSTANCE_HOME/config/OracleBIApplication/coreapplication/ClusterConfig.xml
        

        For example, change the instance number in the NodeId element and change the host name or IP address in the HostNameOrIP element;

        <Node> 
           <NodeType>Server</NodeType> 
            <!--This Configuration setting is managed by Oracle Business 
         Intelligence Enterprise Manager-->
              <MasterServer>true</MasterServer> 
             <!--This Configuration setting is managed by Oracle Business 
         Intelligence Enterprise Manager-->
             <NodeId>instance2:coreapplication_obis1</NodeId> 
              <!--This Configuration setting is managed by Oracle Business 
        Intelligence Enterprise Manager-->
        <HostNameOrIP>host1.example.com</HostNameOrIP> 
            <!--This Configuration setting is managed by Oracle Business 
         Intelligence Enterprise Manager-->
           <ServicePort>9703</ServicePort> 
                     <!--This Configuration setting is managed by Oracle Business 
         Intelligence Enterprise Manager--><MonitorPort>9701</MonitorPort> 
                 </Node> 
        
    • If the primary cluster controller or scheduler is lost, it fails over to the standby cluster controller or scheduler. You must determine whether you want to reconfigure it to be the primary cluster controller or scheduler or leave it as secondary that has been activated because the primary components have failed. For more information, see "Configuring Secondary Instances of Singleton System Components" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

  • If the failed host contained the BI Server, the secondary cluster controller, and the secondary Oracle BI Scheduler, designate the new host as the secondary cluster controller or scheduler.

  • If the failed host contained the BI Server and system components such as BI Presentation Services and BI Java hosts, no additional steps are needed.

  • If the failed host contained the following related components, recover them:

18.3.4.9.4 Importing Oracle BI Enterprise Edition Registry Entries

On Windows, you must import the Oracle BI Enterprise Edition Registry entries to the new host. Section 17.3.3 describes how to export them from the original host.

  1. Copy all the files that you exported from the original host to the new host.

  2. Double-click each file you copied from the original host. Click Yes when prompted, to import the file into the Registry.

18.3.4.10 Recovering Oracle Business Intelligence Publisher to a Different Host

To recover Oracle Business Intelligence Publisher to a different host:

  1. Recover the Managed Server containing the Oracle Business Intelligence Publisher component, as described in Section 18.3.3.

  2. Restore the database containing the Oracle Business Intelligence Publisher schemas, if necessary. See Section 18.2.10.

If backup artifacts are restored from different time, then user accounts, user reports, and user permissions will revert to the restored version. Restore all artifacts from the same point in time.

18.3.4.11 Recovering Oracle Real-Time Decisions to a Different Host

To recover Oracle Real-Time Decisions to a different host:

  1. Recover the Managed Server containing the Oracle Real-Time Decisions component, as described in Section 18.3.3.

Note that if backup artifacts are restored from different time, the analytic models will have missed a period of learning, but their intelligence will be unaffected.

18.3.4.12 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:

    1. 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 Developer's Guide for Oracle Data Integrator.

    2. 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.

    3. Edit each physical agent's configuration and provide the updated Host Name value and, if changed, the Port value.

    4. 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:

    oracledi/agent/bin/odiparams.*
    
  7. Edit the following file to change the database connection information and the port number:

    oracledi/agent/bin/odi_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.13 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:

18.3.4.13.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 /net/home/vault, restore it from backup:

    cd /net/home/vault
    tar -xf vault_backup_092010.tar 
    
  4. Edit the following file:

    DOMAIN_HOME/ucm_domain/ucm/cs/config/config.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.13.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.13.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:

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:

    DOMAIN_HOME/servers/AdminServer/tmp/_WL_user/em/hsz5x1/META-INF/emoms.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_INSTANCE/EMAGENT/emagent_name/sysman/config/emd.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:port/em/upload/ 
    

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_HOME/sysman/state/targets.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_INSTANCE/EMAGENT/emagent_name/sysman/emd/targets.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_INSTANCE/EMAGENT/emagent_name/sysman/config/emd.properties
    (Windows) ORACLE_INSTANCE\EMAGENT\emagent_name\sysman\config\emd.properties
    

    Update the following entry, replacing the host name:

    EMD_URL=http://newhost.domain.com:port/emd/main
    
  3. Start Oracle Management Agent, using the following command:

    opmnctl startproc ias-component=EMAGENT
    
  4. Start the Administration Server:

    DOMAIN_HOME/bin/startWebLogic.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_INSTANCE/config/OHS/ohs_name/mod_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:

    wls:/offline> readDomain('DomainHome')
    wls:/offline/sampledomain> machine = create('newhostname', 'Machine')
    wls:/offline/sampledomain> cd('/Machine/newhostname')
    wls:/offline/sampledomain> nm = create('newhostname', 'NodeManager')
        wls:/offline/sampledomain> cd('/Machine/newhostname/NodeManager/newhostname')
        wls:/offline/sampledomain> set('ListenAddress', 'newhostname')
        wls:/offline/sampledomain> updateDomain()
        wls:/offline/sampledomain> exit()
    
  2. For the Administration Server, set the machine with the new host name, using the following WLST command, in offline mode:

    wls:/offline> readDomain('DomainHome')
    wls:/offline/sampledomain> cd ('/Machine/newhostname')
    wls:/offline/sampledomain> machine = cmo
    wls:/offline/sampledomain> cd ('/Server/AdminServer')
    wls:/offline/sampledomain> set('Machine', machine)
    wls:/offline/sampledomain> updateDomain()
    wls:/offline/sampledomain> exit()   
    

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_HOME/oui/bin/attachHome.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_home/bea/beahomelist
(Windows) C:\bea\beahomelist

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 recover the following Windows Registry key.

HKEY_LOCAL_MACHINE\Software\Oracle

In addition, when you recover system components, such as Oracle Web Cache, you must recover the following Windows Registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\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 Administrator's 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 User's Guide, which is available at:

http://www.oracle.com/technology/documentation/database.html