When using database leasing (for example, with whole server migration), if you recover Oracle WebLogic Server, you should discard the information in the leasing table. You can simply drop and recreate the leasing table by running the leasing table creation script. (For more information about Whole Server Migration, see Whole Server Migration in Administering Clusters for Oracle WebLogic Server.)

For Oracle Platform Security Services, restore the following files:

DOMAIN_HOME/config/fmwconfig/jps-config.xml
DOMAIN_HOME/config/fmwconfig/jps-config-jse.xml
DOMAIN_HOME/config/fmwconfig/cwallet.sso
DOMAIN_HOME/config/fmwconfig/bootstrap/cwallet.sso
DOMAIN_HOME/config/fmwconfig/keystores.xml
DOMAIN_HOME/config/config.xml
DOMAIN_HOME/config/fmwconfig/ids_config.xml
DOMAIN_HOME/config/fmwconfig/system-jazn-data.xml (if present)
DOMAIN_HOME/config/fmwconfig/jps_mbeans.xml

To recover Oracle WebCenter Portal's Analytics:

To recover Oracle WebCenter Content:

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.

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

To recover the application:

You can recover a Jakarta EE application:

• If a Jakarta 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.

• If a deployed application was undeployed from Oracle WebLogic Server.

• A new version of a composite application was redeployed to a Managed Server or cluster. The application is no longer functional.

To recover the application:

To recover the standalone domain to the same host after the operating system has been reinstalled, follow the procedures in Recovering a Standalone Domain.

In this scenario, you recover the standalone domain to a different host.

To recover the standalone domain to a different 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. Recover the file system. For example, recover the domain containing the Administration Server, as described in Recovering After Loss of Oracle WebLogic Server Domain Host.

2. Start the Administration Server. For example:

   DOMAIN_HOME/bin/startWebLogic.sh 
   

   If the Administration Server starts, you do not need to take any further steps.

3. 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 Managed Servers.

   2. Recover the Oracle home, if needed:

      tar -xf oracle_home_backup_06052017.tar 
      

   3. If the domain directory does not reside in the Oracle home, recover the domain directory from backup. First, change to the directory that you want to be the parent of the Domain home, then:

      tar -xf domain_backup_06052017.tar 
      

   4. Start the Administration Server. For example:

      DOMAIN_HOME/bin/startWebLogic.sh 
      

   5. Start the Managed Servers, specifying the Administration URL for the host:

      DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url 
      

   6. Start Node Manager:

      DOMAIN_HOME/bin/startNodeManager.sh

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:

Now you can start and stop the Managed Server on Host B using the Remote Console running on Host C.

If you are recovering the Administration Server for a Web Tier installation, see Additional Actions for Recovering Entities After Loss of Host for information about additional actions you must take.

In this scenario, you recover a Managed Server to the same host after the operating system has been reinstalled or to a new host that has the same host name. The Administration Server is running on Host A and the Managed Server is running on Host B. Host B failed for some reason and the Managed Server must be recovered to Host B.

To recover a Managed Server to the same host:

1. Start Node Manager on Host B:

   cd DOMAIN_HOME/bin
   ./startNodeManager.sh
   

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. Recover the Oracle home to Host B from the backup, if required:

      tar -xf oracle_home_backup_06052017.tar 
      

   2. Stop Node Manager as described in Starting and Stopping Node Manager.

   3. If the Managed Server contains Oracle Reports or Oracle Forms Services, and the Managed Server domain directories reside outside of the Oracle home, restore the domain, in addition to the Oracle home. For example:

      cd Domain_Home
      tar -xf domain_home_backup_06052017.tar 
      

      Go to Step 3.e.

   4. If the Managed Server does not contain Oracle Forms Services or Oracle Reports, 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=/scratch/oracle/config/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/temp.jar
          -domain=/scratch/oracle/config/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 and 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 Deploying Applications to Oracle WebLogic Server for information about deploying applications.

   6. Update the Node Manager property ListenAddress by using the following WLST commands:

      readDomain('Domain_Home')
      cd('/')
      cd('NMProperties')
      set('ListenAddress','localhost')
      set('ListenPort',9001)
      updateDomain()
      

   7. If Node Manager is not started, start it:

      cd DOMAIN_HOME/bin
      ./startNodeManager.sh
      

   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.

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. There are two machines, which are logical representations of the computer that hosts one or more WebLogic Servers, machine_1 on Host A and machine_2 on Host B.

To recover a Managed Server to a different host:

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

   tar -xf oracle_home_backup_06052014.tar 
   

2. Reconfigure the topology to point to the new host:

   1. To avoid an inconsistent backup, do not make any configuration changes until the backup is completed. To ensure that no changes are made in the WebLogic Server domain, lock the WebLogic Server configuration, as described in Locking the WebLogic Server Configuration.

   2. In Fusion Middleware Control, change the configuration of machine_2, to point it to the new host:

      From the WebLogic Domain menu, expand Environment and then select Machines. On the Machine page, select machine_2 and select the Configuration tab. Then select the Node Manager tab. Change the Listen Address to the address for Host C. Click Save.

      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 Administering Security for Oracle WebLogic Server.

   3. Change the Managed Server configuration to point to the new host:

      From the left pane of the Remote Console, expand Environment and then select Servers. The, select the name of the server. Select the Configuration tab, then the General tab.

      Change the Machine to machine_2.

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

      Click Save, then click Activate Changes.

   4. Unlock the Oracle WebLogic Server configuration by clicking Release Configuration on the Edit Session menu.

3. Take any additional steps needed for components as described in Table 18-1.

4. Stop Node Manager as described in Starting and Stopping Node Manager.

5. If the Managed Server contains Oracle Reports or Oracle Forms Services, and the Managed Server domain directories reside outside of the Oracle home, restore the domain, in addition to the Oracle home. For example:

   cd Domain_Home
   tar -xf domain_home_backup_042012.tar 
   

   Go to Step 7.

6. If the Managed Server does not contain the components listed in Step 5, 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=/scratch/oracle/config/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/temp.jar
         -domain=/scratch/oracle/config/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.

7. 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 and 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 Deploying Applications to Oracle WebLogic Server for information about deploying applications.

8. Update the ListenAddress by using the following WLST commands:

   readDomain('Domain_Home')
   cd('/')
   cd('NMProperties')
   set('ListenAddress','localhost')
   set('ListenPort',9001)
   updateDomain()
   

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

   cd DOMAIN_HOME/bin
   ./startNodeManager.sh
   

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

11. Update Oracle Inventory, as described in Updating Oracle Inventory.

12. On Windows, recover the Windows Registry, as described in Recovering the Windows Registry

13. If your environment contains Oracle HTTP Server, modify the mod_wl_ohs.conf file, as described in Modifying the mod_wl_ohs.conf File.

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

To recover a Java component to the same host:

To recover a Java component to a different host:

To recover a system component, such as Oracle HTTP Server, to the same host or a different host:

• For system components, such as Oracle HTTP Server, in a standalone domain, you recover the domain, as described in Recovering After Loss of Standalone Domain Host.

• For system components, such as Oracle HTTP Server, in an Oracle WebLogic Server domain, you recover the domain, as described in Recovering After Loss of Oracle WebLogic Server Domain Host.

However, some components require additional steps, as noted in Table 18-1.

To recover the Oracle SOA Suite Managed Server to the same host, recover the Managed Server, as described in Recovering a Managed Server to the Same Host.

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 Recovering a Managed Server to a Different Host.

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

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

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

   1. In Fusion Middleware Control, from the WebLogic Domain menu, select Environment, then Clusters.

   2. Select the cluster you want to configure.

   3. From the WebLogic Cluster menu, select Administration, then HTTP.

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

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

   6. Restart each Managed Server.

To recover Oracle Forms Services to a different host:

To recover Oracle Reports to a different host:

To recover Oracle WebCenter Content to a different host:

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.

To recover Fusion Middleware Control to a different host, update properties using the System MBean Browser:

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) DOMAIN_HOME/config/fmwconfig/components/OHS/ohs_name/mod_wl_ohs.conf
(Windows) DOMAIN_HOME\config\fmwconfig\components\OHS\ohs_name\mod_wl_ohs.conf

Note that with Oracle HTTP Server in a WebLogic Server domain, this directory is in the Domain home of the Administration Server. With Oracle HTTP Server in a standalone domain, this directory is the Domain home of Oracle HTTP Server.

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> 

If the Administration Server has a Listen address, you must create a new machine with the new host name before you start the Administration Server:

Take the following steps:

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:

(UNIX) ORACLE_HOME/oui/bin/attachHome.sh
(Windows) ORACLE_HOME\oui\bin\attachHome.cmd

When you recover any component to a different host on Windows, as in the case of loss of host, you must import any Windows Registry keys related to Oracle Fusion Middleware to the new host. (You exported the Registry keys in Backing Up Windows Registry Entries.)

Recover the following Registry key.

HKEY_LOCAL_MACHINE\Software\Oracle

In addition, recover each node that begins with Oracle within the following registry keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services

To import a key that you have previously exported, use the following command:

regedit  /I  FileName

For example:

regedit /I C:\oracleregistry.reg 

You can also use the Registry Editor to import the key, as described in the Registry Editor Help.