Introduction
If you would like to test the ADOP process with applying a patch, you can execute an empty patch cycle. You could also execute an empty patch cycle to switch between the fs1 and fs2 filesystems, again, without applying a patch.
Below is an example of executing a complete version of an empty patch cycle. Note the “actualize_all” phase will delete the old database editions.
Run an empty patch cycle
Step 1: Log in to your application server as the “applmgr” user
Step 2: Run an ADOP empty patch cycle
unix> source /opt/app/oracle/apps/EBSapps.env run
unix>adop phase=prepare
unix>adop phase=actualize_all
unix>adop phase=finalize finalize_mode=full
unix>adop phase=cutover
unix> source /opt/app/oracle/apps/EBSapps.env run
adop phase=cleanup cleanup_mode=full
When complete, if you check the status you will see output similar to the following:
==============================================================
ADOP (C.Delta.11)
Session Id: 91
Command: status
Output: /opt/app/oracle/apps/fs_ne/EBSapps/log/adop/91/20230101_190926/adzdshowstatus.out
===============================================================
| Node Name | Node Type | Phase | Status | Started | Finished | Elapsed |
|---|---|---|---|---|---|---|
| beejartha | master | PREPARE | COMPLETED | 2023/01/0116:37:06 | 2023/01/01 16:42:29 | 0:05:23 |
| APPLY | COMPLETED | |||||
| FINALIZE | COMPLETED | 2023/01/0117:16:17 | 2023/01/01 17:20:19 | 0:04:02 | ||
| CUTOVER | COMPLETED | 2023/01/0117:24:09 | 2023/01/01 17:34:55 | 0:10:46 | ||
| CLEANUP | COMPLETED | 2023/01/0117:36:54 | 2023/01/01 19:07:57 | 1:31:03 |
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.
