Introduction
When running an ADOP patch cycle, if the prepare, apply, or finalize phases fail, you have the option of aborting the cycle and starting again.
For example, when applying a patch last week, we got the following error:
*******FATAL ERROR*******
PROGRAM : (/opt/app/oracle/apps/fs2/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl)
TIME : Thu Jan 25 16:15:44 2024
FUNCTION: ADOP::GlobalVars::_validateApplyRestartArgs [ Level 1 ]
ERRORMSG: When running adop after a previous patching cycle failed, you must specify either the 'abandon' or 'restart' parameter.
[STATEMENT] Please run adopscanlog utility, using the command
"adopscanlog -latest=yes"
to get the list of the log files along with snippet of the error message corresponding to each log file.
adop exiting with status = 255 (Fail)
We decided to abort the patch cycle so all changes were rolled back and we could start over.
Aborting a Patch Cycle
Step 1: Source the Applications environment and abort the current patch cycle
As the applmgr user
unix> . /opt/app/oracle/apps/EBSapps.env run
unix>adop phase=abort
If successful, you will see the following
The abort phase completed successfully.
adop exiting with status = 0 (Success)
Step 2: Confirm the cycle was aborted (optional)
As the applmgr user
unix>adop -status
You should see output similar to the following:
==============================================================
ADOP (C.Delta.14)
Session Id: 94
Command: status
Output: /opt/app/oracle/apps/fs_ne/EBSapps/log/adop/91/20240126_094640/adzdshowstatus.out
===============================================================
| Node Name | Node Type | Phase | Status | Started | Finished | Elapsed |
|---|---|---|---|---|---|---|
| beejartha | master | PREPARE | SESSION ABORTED | 2024/01/25 14:40:30 | 2024/01/25 15:04:40 | 0:24:10 |
| APPLY | SESSION ABORTED | 2024/01/25 16:01:04 | 2024/01/26 09:28:28 | 17:27:24 | ||
| FINALIZE | SESSION ABORTED | |||||
| CUTOVER | SESSION ABORTED | |||||
| CLEANUP | NOT STARTED |
File System Synchronization Type: Light
INFORMATION: Patching cycle aborted, so fs_clone will run automatically on beejartha node in prepare phase of next patching cycle.
adop exiting with status = 0 (Success)
Step 3: Run the Cleanup phase
As the applmgr user
unix>adop phase=cleanup cleanup_mode=full
Step 4: Start the patching cycle again with the prepare phase
Credits
- This tutorial is independently created and is not official Oracle Corporation documentation.
- The content of this tutorial has been enriched by leveraging the insights and documentation available from Oracle Corporation. We extend our thanks to Oracle for their dedication to knowledge sharing. For official Oracle resources and additional information, please refer to www.oracle.com.
