OMSPatcher Session Resume

OMSPatcher supports resume upon failure capability for both single-OMS and multi-OMS configurations.

This section covers the following topics:

Resume capability in Single-OMS Configuration

On a single OMS System, OMSPatcher executes end-to-end automation of patching steps. Once a failure has occurred, OMSPatcher can resume from the failed step. The OMS administrator must refer to the master log file created by OMSPatcher to ascertain and resolve the root cause of the failure, and then run the omspatcher resume command to complete the patching. OMSPatcher resume runs the steps from the point of failure.

Example

  1. OMSPatcher, while applying an auto system patch, it fails while stopping the OMS.

    Example:

    $omspatcher apply /scratch/patches_april/24_1_latest/1111112
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation.  All rights reserved.

OMSPatcher version : 13.9.24.2.0
OUI version        : 13.9.4.0.0
Running from       : /scratch/sm/work/omshome3308/oms_home
Log file location  : /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/opatch2025-04-11_15-28-54PM_1.log

OMSPatcher log file: /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/1111112/omspatcher_2025-04-11_15-29-13PM_apply.log

Please enter OMS weblogic admin server URL(t3s://shortterm-16095.subnet1rg2phxsu.emdevinfraphx1.oraclevcn.com:7102):> 
Please enter OMS weblogic admin server username(weblogic):> 
Please enter OMS weblogic admin server password:> 

Enter SYS or Non-SYS (Admin User) username: sys
Enter 'sys' password : 
Checking if current repository database is a supported version
Current repository database version is supported

Prereq "checkComponents" for patch 1111140 passed.

Prereq "checkComponents" for patch 1111143 passed.

Prereq "checkComponents" for patch 1111142 passed.

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) "1111140,1111143" and Oracle Home "/scratch/sm/work/omshome3308/oms_home"...
Sub-patch(es) "1111140,1111143" are successfully analyzed for Oracle Home "/scratch/sm/work/omshome3308/oms_home"

Running apply prerequisite checks for sub-patch(es) "1111142" and Oracle Home "/scratch/sm/work/omshome3308/ext_oms_home"...
Sub-patch(es) "1111142" are successfully analyzed for Oracle Home "/scratch/sm/work/omshome3308/ext_oms_home"

To continue, OMSPatcher will do the following:
[Patch and deploy artifacts]   : Apply sub-patch(es) [ 1111140 1111143 1111142 ]
                                 Apply sub-patch(es) [ 1111140 1111143 1111142 ]
                                 Apply RCU artifact with patch "/scratch/sm/work/omshome3308/ext_oms_home/.omspatcher_storage/1111142_Sep_12_2024_10_04_19/original_patch";
                                 Apply RCU artifact with patch "/scratch/sm/work/omshome3308/oms_home/.omspatcher_storage/1111143_Oct_9_2024_09_22_52/original_patch";
                                 Register MRS artifact "swlib";
                                 Register MRS artifact "eventsaux";
                                 Register MRS artifact "eventSpecificCustmzn";
                                 Register MRS artifact "compression";
                                 Register MRS artifact "oobrules";
                                 Register MRS artifact "targetType";
                                 Register MRS artifact "storeTargetType";
                                 Register MRS artifact "jobTypes";
                                 Register MRS artifact "default_collection";
                                 Register MRS artifact "omsPropertyDef";
                                 Register MRS artifact "runbooks";
                                 Register MRS artifact "TargetPrivilege"

Do you want to proceed? [y|n]
y
User Responded with: Y
Stopping all the services on primary OMS.....
Please monitor log file: /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/2025-04-11_15-36-55PM_SystemPatch_1111112_9/stop_oms_all_2025-04-11_15-36-55PM.log

Complete Summary
================

All log file names referenced below can be accessed from the directory "/scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/2025-04-11_15-36-55PM_SystemPatch_1111112_9"

Patching summary:
-----------------

The following sub-patch(es) are applicable:

             Featureset       Sub-patches                                            Log file
             ----------       -----------                                            --------
  oracle.sysman.top.oms   1111140,1111143   1111140,1111143_opatch2025-04-11_15-30-27PM_2.log
  oracle.sysman.top.zdt           1111142           1111142_opatch2025-04-11_15-31-40PM_2.log

OMSPatcher failed to execute some of the patching steps. Please check the Patching summary,individual logs and try to resolve the issue. Once the issue is resolved,Please execute below command to complete patching session:
	omspatcher resume

------------------------------------------------------------------------------------------------
OMSPatcher wont allow any other patching operations unless the script is executed successfully
------------------------------------------------------------------------------------------------

Log file location: /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/1111112/omspatcher_2025-04-11_15-29-13PM_apply.log

OMSPatcher failed with error code 240

  2. OMS Administrator cannot start a new patching session when there are remnants of an incomplete patching session. OMSPatcher clearly errors out with the detailed information regarding the failure and what action need to be taken to fix this issue.

    Example:

    omspatcher apply /scratch/patches_april/24_1_latest/1111112
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation.  All rights reserved.

OMSPatcher version : 13.9.24.2.0
OUI version        : 13.9.4.0.0
Running from       : /scratch/sm/work/omshome3308/oms_home
Log file location  : /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/opatch2025-04-11_17-05-39PM_1.log

OMSPatcher finds that previous patching session is not yet completed. Please refer log file for the previous session and execute the below command to complete the previous session. OMSPatcher can proceed to execute new operations only if previous session is completed successfully.
	omspatcher resume

Log file location: /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/opatch2025-04-11_17-05-39PM_1.log

OMSPatcher failed with error code 255

  3. Now OMS Administrator can run the omspatcher resume command on the single OMS to finish the failed patching session.

    Example:

    OMSPatcher/omspatcher resume
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation.  All rights reserved.

OMSPatcher version : 13.9.24.2.0
OUI version        : 13.9.4.0.0
Running from       : /scratch/sm/work/omshome3308/oms_home
Log file location  : /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/opatch2025-04-11_17-07-40PM_1.log

OMSPatcher log file: /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/SystemPatch/omspatcher_2025-04-11_17-07-13PM_resume.log

[Info:Previous action was performed by user:'sys']
Enter 'sys' password : 
Enter SYSMAN Password : 
command /scratch/sm/work/omshome3308/oms_home/bin/emctl  stop oms  -all -force
/scratch/sm/work/omshome3308/oms_home/bin/emctl  stop oms  -all -force is Successfully run 
......

command /scratch/sm/work/omshome3308/oms_home/OMSPatcher/omspatcher executeCommand -cmdType POST_APPLY_SQL -oh /scratch/sm/work/omshome3308/oms_home -dbUser sys
/scratch/sm/work/omshome3308/oms_home/OMSPatcher/omspatcher executeCommand -cmdType POST_APPLY_SQL -oh /scratch/sm/work/omshome3308/oms_home -dbUser sys is Successfully run

command /scratch/sm/work/omshome3308/oms_home/bin/emctl start oms
/scratch/sm/work/omshome3308/oms_home/bin/emctl start oms is Successfully run

OMSPatcher succeeded.

Resume Capability in Multi-OMS Configuration

On a multi-OMS System, OMSPatcher executes end-to-end automation of patching steps. Once a failure has occurred, OMSPatcher can resume from the failed step. The OMS administrator must refer to the master log file created by OMSPatcher to ascertain and resolve the root cause of the failure, and then run the omspatcher resume command to complete the patching. OMSPatcher resume runs the steps from the point of failure.

For Multi-OMS configuration, OMSPatcher resume runs on the primary OMS and automatically completes the patching on add OMSes by submitting the job.

Example

  1. OMSPatcher, while applying an auto system patch, it fails while stopping the OMS.

    Example:

    $omspatcher apply /scratch/patches_april/24_1_latest/1111112
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation.  All rights reserved.

OMSPatcher version : 13.9.24.2.0
OUI version        : 13.9.4.0.0
Running from       : /scratch/sm/work/omshome3308/oms_home
Log file location  : /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/opatch2025-04-11_15-28-54PM_1.log

OMSPatcher log file: /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/1111112/omspatcher_2025-04-11_15-29-13PM_apply.log

Please enter OMS weblogic admin server URL(t3s://shortterm-16095.subnet1rg2phxsu.emdevinfraphx1.oraclevcn.com:7102):> 
Please enter OMS weblogic admin server username(weblogic):> 
Please enter OMS weblogic admin server password:> 

Enter SYS or Non-SYS (Admin User) username: sys
Enter 'sys' password : 
Checking if current repository database is a supported version
Current repository database version is supported

Prereq "checkComponents" for patch 1111140 passed.

Prereq "checkComponents" for patch 1111143 passed.

Prereq "checkComponents" for patch 1111142 passed.

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) "1111140,1111143" and Oracle Home "/scratch/sm/work/omshome3308/oms_home"...
Sub-patch(es) "1111140,1111143" are successfully analyzed for Oracle Home "/scratch/sm/work/omshome3308/oms_home"

Running apply prerequisite checks for sub-patch(es) "1111142" and Oracle Home "/scratch/sm/work/omshome3308/ext_oms_home"...
Sub-patch(es) "1111142" are successfully analyzed for Oracle Home "/scratch/sm/work/omshome3308/ext_oms_home"

To continue, OMSPatcher will do the following:
[Patch and deploy artifacts]   : Apply sub-patch(es) [ 1111140 1111143 1111142 ]
                                 Apply sub-patch(es) [ 1111140 1111143 1111142 ]
                                 Apply RCU artifact with patch "/scratch/sm/work/omshome3308/ext_oms_home/.omspatcher_storage/1111142_Sep_12_2024_10_04_19/original_patch";
                                 Apply RCU artifact with patch "/scratch/sm/work/omshome3308/oms_home/.omspatcher_storage/1111143_Oct_9_2024_09_22_52/original_patch";
                                 Register MRS artifact "swlib";
                                 Register MRS artifact "eventsaux";
                                 Register MRS artifact "eventSpecificCustmzn";
                                 Register MRS artifact "compression";
                                 Register MRS artifact "oobrules";
                                 Register MRS artifact "targetType";
                                 Register MRS artifact "storeTargetType";
                                 Register MRS artifact "jobTypes";
                                 Register MRS artifact "default_collection";
                                 Register MRS artifact "omsPropertyDef";
                                 Register MRS artifact "runbooks";
                                 Register MRS artifact "TargetPrivilege"

Do you want to proceed? [y|n]
y
User Responded with: Y
Stopping all the services on primary OMS.....
Please monitor log file: /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/2025-04-11_15-36-55PM_SystemPatch_1111112_9/stop_oms_all_2025-04-11_15-36-55PM.log

Complete Summary
================

All log file names referenced below can be accessed from the directory "/scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/2025-04-11_15-36-55PM_SystemPatch_1111112_9"

Patching summary:
-----------------

The following sub-patch(es) are applicable:

             Featureset       Sub-patches                                            Log file
             ----------       -----------                                            --------
  oracle.sysman.top.oms   1111140,1111143   1111140,1111143_opatch2025-04-11_15-30-27PM_2.log
  oracle.sysman.top.zdt           1111142           1111142_opatch2025-04-11_15-31-40PM_2.log

OMSPatcher failed to execute some of the patching steps. Please check the Patching summary,individual logs and try to resolve the issue. Once the issue is resolved,Please execute below command to complete patching session:
	omspatcher resume

------------------------------------------------------------------------------------------------
OMSPatcher wont allow any other patching operations unless the script is executed successfully
------------------------------------------------------------------------------------------------

Log file location: /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/1111112/omspatcher_2025-04-11_15-29-13PM_apply.log

OMSPatcher failed with error code 240

  2. OMS Administrator cannot start a new patching session when there are remnants of an incomplete patching session. OMSPatcher clearly errors out with the detailed information regarding the failure and what action need to be taken to fix this issue.

    Example:

    omspatcher apply /scratch/patches_april/24_1_latest/1111112
OMSPatcher Automation Tool
Copyright (c) 2024, Oracle Corporation.  All rights reserved.

OMSPatcher version : 13.9.24.2.0
OUI version        : 13.9.4.0.0
Running from       : /scratch/sm/work/omshome3308/oms_home
Log file location  : /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/opatch2025-04-11_17-05-39PM_1.log

OMSPatcher finds that previous patching session is not yet completed. Please refer log file for the previous session and execute the below command to complete the previous session. OMSPatcher can proceed to execute new operations only if previous session is completed successfully.
	omspatcher resume

Log file location: /scratch/sm/work/omshome3308/oms_home/cfgtoollogs/omspatcher/opatch2025-04-11_17-05-39PM_1.log

OMSPatcher failed with error code 255

  3. Now OMS Administrator can run the omspatcher resume command on the primary OMS to finish the failed patching session.

    Example:

    OMSPatcher/omspatcher resume