Applying feature packs or fix packs on the Infrastructure Management server in high-availability and disaster recovery mode

Where you are in the Applying-feature-packs-or-fix-packs process

To apply the feature pack or fix pack on Infrastructure Management in application high-availability and disaster recovery mode

If you have configured Infrastructure Management for application high availability and disaster recovery, perform the following steps to apply the feature pack or fix pack:

If you are using Oracle Data Guard

Note

You do not need to apply the feature pack or fix pack on the recovery site Infrastructure Management servers, since the pw folder that you copy from the primary site contains the updated files.


  1. At the primary site, apply the feature pack or fix pack on the Infrastructure Management servers. See Applying-feature-packs-or-fix-packs-on-the-Infrastructure-Management-server-in-the-application-high-availability-mode.
  2. If you are using a third-party data replication solution or any OS backup option, you do not need to stop either server. Else, stop both servers by following the sequence in sub-steps a and b.
    1. Stop the secondary server by using the pw sys stop command.
      After stopping the secondary server, ensure that all internal processes are stopped by using the pw process list command.
    2. Stop the primary server by using the pw sys stop command.
      After stopping the primary server, ensure that all internal processes are stopped by using the pw process list command.
  3. Create a backup of the installedDirectory/pw folder on both servers.
  4. Copy the backup of the installedDirectory/pw folder from the primary site to the corresponding recovery site servers.

  5. At the recovery site, on both primary and secondary Infrastructure Management servers, update the $BPPM_SERVER_HOME/pw/server/etc/mcell.dir entry with the recovery site, primary Presentation Server host name. For example:

    gateway.pn_server   ts_event_gateway    mc  <Primary Presentation Server host name>:<port number>

If you are not using Oracle Data Guard

Perform these steps at the primary site:

  1. Apply the feature pack or fix pack on the Infrastructure Management servers. See Applying-feature-packs-or-fix-packs-on-the-Infrastructure-Management-server-in-the-application-high-availability-mode.
  2. If you are using a third-party data replication solution or any OS backup option, you do not need to stop either server. Else, stop both servers by following the sequence in sub-steps a and b.
    1. Stop the secondary server by using the pw sys stop command.
      After stopping the secondary server, ensure that all internal processes are stopped by using the pw process list command.
    2. Stop the primary server by using the pw sys stop command.
      After stopping the primary server, ensure that all internal processes are stopped by using the pw process list command.
  3. Create a backup of the installedDirectory/pw folder on both servers.
  4. Start the primary server by using the pw sys start command.
    Ensure that the primary server has successfully started by running the pw license list command. The output should display a valid license expiration date, as in the following example:
    Feature : Server, Expiration : Thu Dec 31 00:00:00 IST 2099, NodeLocked : false
  5. Verify that the primary server is the active node by running the pw ha status command.
  6. Start the secondary server by using the pw sys start command.
    Ensure that the secondary server has successfully started by running the pw license list command. The output should display a valid license expiration date, as in the following example:
    Feature : Server, Expiration : Thu Dec 31 00:00:00 IST 2099, NodeLocked : false

Perform these steps at the recovery site:

  1. Apply the feature pack or fix pack on the Infrastructure Management servers. See Applying-feature-packs-or-fix-packs-on-the-Infrastructure-Management-server-in-the-application-high-availability-mode.
  2. If you are using a third-party data replication solution or any OS backup option, you do not need to stop either server. Else, stop both servers by following the sequence in sub-steps a and b.
    1. Stop the secondary server by using the pw sys stop command.
      After stopping the secondary server, ensure that all internal processes are stopped by using the pw process list command.
    2. Stop the primary server by using the pw sys stop command.
      After stopping the primary server, ensure that all internal processes are stopped by using the pw process list command.
  3. Copy the backup of the installedDirectory/pw folder from the primary site to the corresponding recovery site servers.
  4. Start the primary server by using the pw sys start command.
    Ensure that the primary server has successfully started by running the pw license list command. The output should display a valid license expiration date, as in the following example:
    Feature : Server, Expiration : Thu Dec 31 00:00:00 IST 2099, NodeLocked : false
  5. Verify that the primary server is the active node by running the pw ha status command.
  6. Start the secondary server by using the pw sys start command.
    Ensure that the secondary server has successfully started by running the pw license list command. The output should display a valid license expiration date, as in the following example:
    Feature : Server, Expiration : Thu Dec 31 00:00:00 IST 2099, NodeLocked : false


Where to go from here

Step 3 Phase C — Now that you have successfully installed the feature pack or fix pack on the Infrastructure Management server, you must apply it on the administrator console.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*