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. I normally consider to do it, once the count reaches 15 editions in my Production environment.

 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
$ 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