9 Applying the SPB Patches using SPBAT

After completing the steps described in section Prerequisites, follow the next steps to apply the SPB patches in the IDM 12.2.1.4 environment:

PreStop:

To be done on all IDM hosts, as described in section System Overview:
  1. Run the SPBAT utility with appropriate options for the PreStop phase based on the install type:

    [Unix - Please open the bash shell and execute]

    
cd IDM_SPB_12.2.1.4.<VERSION>/tools/spbat/generic/SPBAT
./spbat.sh -type <oam/oig/oud/oid> -phase prestop -mw_home <path to mw_home> -spb_download_dir <path to IDM_SPB_12.2.1.4.<VERSION> stage location> -log_dir <log_dir>

    [Windows - Please open the Command Prompt as Administrator and execute]

    
cd IDM_SPB_12.2.1.4.<VERSION>\tools\spbat\generic\SPBAT
spbat.bat -type <oam/oig/oud/oid> -phase prestop -mw_home <path to mw_home> -spb_download_dir <path to IDM_SPB_12.2.1.4.<VERSION> stage location> -log_dir <log_dir>
  2. Perform the following after running the script:
    1. Review the html reports before proceeding with the next phase. The analysis reports are generated under <log_dir>/<hostname_type>patch_log_dir/spbat-logs/reports location.
    2. Upgrade OPatch after creating a full backup of ORACLE_HOME if the minimum OPatch version requirement is not met.
    3. If there are any issues that need to be addressed, you can run the PreStop phase again but will need to create and use a new logs directory prior to doing so.
    4. If no issues are found, for Downtime and PostStart phases please use the same log directory as in the Prestop phase.
  3. For IDM cluster, repeat steps 1 and 2 on each VM. Make sure that the patching user and ORACLE_HOME install user/owner are same to avoid permission issues.
  4. If two or more install types share the same ORACLE_HOME, then repeat steps 1 and 2 against ORACLE_HOME for each install type.
Stop Services:
  1. Stop all IDM related services (including WebLogic servers) running on IDM hosts.
  2. Make sure that no services are accessing the ORACLE_HOME binaries.
Backup:
  1. Create a complete backup of ORACLE_HOME and DOMAIN_HOME locations.
  2. Create a cold backup of the entire IDM setup by using standard backup software/utilities.
  3. Create a backup of the database.

Downtime Patching:

To be done on all IDM hosts, as described in section System Overview:
  1. Run the SPBAT utility with appropriate options for the Downtime phase based on the install type:
    [Unix - Please open the bash shell and execute]
    cd IDM_SPB_12.2.1.4.<VERSION>/tools/spbat/generic/SPBAT
./spbat.sh -type <oam/oig/oud/oid> -phase downtime -mw_home <path to mw_home> -spb_download_dir <path to IDM_SPB_12.2.1.4.<VERSION> > -log_dir <log_dir>
    [Windows - Please open the Command Prompt as Administrator and execute]
    cd IDM_SPB_12.2.1.4.<VERSION>\tools\spbat\generic\SPBAT
spbat.bat -type <oam/oig/oud/oid> -phase downtime -mw_home <path to mw_home> -spb_download_dir <path to IDM_SPB_12.2.1.4.<VERSION> > -log_dir <log_dir>
  2. Perform the following after running the script:
    1. In case of any failure, review the patching logs before proceeding to next steps.
  3. Perform appropriate Post-Install and Configuration steps before the servers are started up:
    1. OAM - Please refer to item A. Before Server Startup of section Post-Install and Configuration Steps - OAM in this document.
    2. OIG - Please refer to item A. Before Server Startup of section Post-Install and Configuration Steps - OIG in this document.
    3. OUD - Please refer to item A. Before Server Startup of section Post-Install and Configuration Steps - OUD in this document.
    4. OID - Please refer to item A. Before Server Startup of section Post-Install and Configuration Steps - OID in this document.
  4. For IDM cluster, repeat steps 1 and 2 on each VM. Make sure that the patching user and ORACLE_HOME install user/owner are the same to avoid permission issues.
  5. If two or more install types share the same ORACLE_HOME, then repeat steps 1,2 and 3 against ORACLE_HOME for each install type.

Start Services:

Start all IDM related services (including WebLogic Servers) running on IDM hosts.

PostStart:

To be done on all IDM hosts, as described in section System Overview:

  1. Run the SPBAT utility with appropriate options for the PostStart phase based on the install type:
    [Unix - Please open the bash shell and execute]
    cd IDM_SPB_12.2.1.4.<VERSION>/tools/spbat/generic/SPBAT
./spbat.sh -type <oam/oig/oud/oid> -phase poststart -mw_home <path to mw_home> -spb_download_dir <path to IDM_SPB_12.2.1.4.<VERSION> > -log_dir <log_dir>
    [Windows - Please open the Command Prompt as Administrator and execute]
    cd IDM_SPB_12.2.1.4.<VERSION>\tools\spbat\generic\SPBAT
spbat.bat -type <oam/oig/oud/oid> -phase poststart -mw_home <path to mw_home> -spb_download_dir <path to IDM_SPB_12.2.1.4.<VERSION> > -log_dir <log_dir>
  2. After running the script, review the patching logs generated under /patch_log_dir/spbat-logs for any failures.
  3. Perform appropriate Post-Install and Configuration steps after the servers are started up:
    1. OAM - Please refer to item "B. After Server Startup" of section "9 Post-Install and Configuration Steps - OAM" in this document
    2. OIG - Please refer to item "B. After Server Startup" of section "10 Post-Install and Configuration Steps - OIG" in this document
    3. OUD - Please refer to item "B. After Server Startup" of section "11 Post-Install and Configuration Steps - OUD" in this document
    4. OID - Please refer to item "B. After Server Startup" of section "12 Post-Install and Configuration Steps - OID" in this document
  4. For IDM cluster, repeat steps 1 and 2 on each VM. Make sure that the patching user and ORACLE_HOME install user/owner are the same to avoid permissions issues.
  5. If two or more install types share the same ORACLE_HOME, then repeat steps 1,2 and 3 against ORACLE_HOME for each install type.

Complete Validation:

Once the SPB patching activity is completed, restart and verify the environment and URLs.