Showing posts with label ADOP. Show all posts
Showing posts with label ADOP. Show all posts

12 June 2022

adop phase=actualize_all

 

How to Drop Old Database Editions in EBS R12.2 


In EBS R12.2, as each online patching cycle is completed, the database will accumulate an additional old database edition. An additional column ZD_EDITION_NAME is populated in the seed tables. If the number of these grows too large, system performance will start to be affected. When the number of old database editions reaches 25 or more, we should consider dropping all old database editions by running the adop actualize_all phase and then performing a full cleanup. 

Important: This procedure will take a large amount of time (significantly longer than a normal patching cycle), and should only be performed when there is no immediate need to start a new patching cycle.

Before starting, you should ensure that the system has the recommended database patches and latest AD-TXK code level installed.


When no patches need to be applied in Online Patching

To proceed, run the following commands in the order shown:
$ adop phase=prepare
$ adop phase=actualize_all
$ adop phase=finalize finalize_mode=full
$ adop phase=cutover
$ adop phase=cleanup cleanup_mode=full

Old database editions would be cleared now


OR

Every-time online patching is performed:

$ adop phase=prepare
$ adop phase=apply patches=1,2,3
$ adop phase=actualize_all   -------------> Do this here
$ adop phase=finalize finalize_mode=full
$ adop phase=cutover
$ adop phase=cleanup cleanup_mode=full

It has to be performed just before phase=finalize/cutover

How to execute an Empty Patching cycle in Oracle Apps R12.2

 

How to execute an Empty Patching cycle in Oracle Apps R12.2



Purpose: How to run empty patching cycle in EBS R12.2 

Occasion to run

> Testing purpose
> Switching the filesystem from fs1 to fs2, or vice versa.


Simple Command

login to application tier and invoke env file
cd /u01/install/APPS
. EBSapps.env RUN 

adop phase=prepare,finalize,cutover,cleanup