You have to source always Run file edition when initiating adop patching cycle
Internally adop takes care for other tasks
Hope this answers
You have to source run file system env file to run adop , internally it will apply the patch on patch file system
You can go through the maintainance document for R12.2
Oracle E-Business Suite Maintenance Guide
Part Number E22954-21
We can see a point in maintanance guide where clearly mentioned as
The adop utility sets its own environment. There is therefore no need to source the environment before running it.
Thanks Jibu and Shaik
So it is not true that when you run patch=apply phase , you should be in the patch edition or
must run first > . /u01/appascp/ASCP/EBSapps.env patch
Therefore, you can run as well a one time command for all the phases?
adop phase=prepare,apply,finalize,cutover,cleanup,fs_clone patches=20000145 patchtop=/u01/PATCH
You will be able to run below:
adop phase=prepare,apply,finalize,cutover,cleanup patches=20000145 patchtop=/u01/PATCH
You will not be able to club them into a single statement.
A high level overview of an online patching cycle would, programmatically, look like this:
Source your run file system env file:
. <ebs_root>/EBSapps.env run
# Prepare for patching:
$ adop phase=prepare
# Apply patches:
$ adop phase=apply patches=<xyz>
# Finalize patch application:
$ adop phase=finalize
# Perform cutover:
$ adop phase=cutover
$ . <ebs_root>/EBSapps.env run
# Perform user acceptance testing via application UI
# Perform cleanup:
$ adop phase=cleanup
#Syncronize the filesystem:
Optionally, you can combine the abort and cleanup commands as follows:
$ adop phase=abort,cleanup cleanup_mode=full
You should perform adop cycle in this order as specified not in the same command line to avoid any issues.
For complete details refer the maintenance guide:
Hope it helps.
An additional information on fs_clone:
The fs_clone phase is a command that is used to synchronize the patch file system with the run file system.
Normally, the fs_clone phase should only be run when mentioned as part of a specific documented procedure.
You may perform a procedure that as a final step instructs you to run fs_clone.
You do not have to do this immediately:
the key requirement is to run fs_clone before you start the next patching cycle. And if you are performing multiple procedures, each of which requires fs_clone to be run at the end, you only need to run it once before the start of the next patching cycle.
fs_clone - Recreates the patch edition file system as an exact copy of the run edition file system. This phase cannot be specified with any other phase.
Use of fs_clone is normally not required. Situations that do require fs_clone are will explicitly document that requirement. If running this phase, ensure that your current working directory is not within the patch edition file system.
Thanks ALL dearest friends
Why is that when I apply patch, when it switch to another file system, the developers are complaining that their source codes are gone
Does it mean their codes were left behind with the previous fs and need to be fs_clone or copy manually to the new run fs?
Review following MOS Notes:
12.2 E-Business Suite Steps To Migrate The Custom Configuration Settings And Files From RUN To PATCH FILESYSTEM Using Tool ADOP_SYNC.DRV (Doc ID 2167878.1)
This will help you in handling the customizations.
Hope this helps.
Thanks Narsi and ALL
Hi Samya and ALL,
- The key requirement is to run fs_clone before you start the next patching cycle. And if you are performing multiple procedures, each of which requires fs_clone to be run at the end, you only need to run it once before the start of the next patching cycle.
- fs_clone - Recreates the patch edition file system as an exact copy of the run edition file system. This phase cannot be specified with any other phase.
I am confused now what if I forgot to run fs_clone? or I run twice? for example I forgot long ago may last patch that I did run it, and when I apply a new patch , I run in again? Does this mean my instance is now messed up?
I was thinking that when you run adop phase=prepare << it will do fs_clone and cleanup first?
Why is Oracle fond of complicating things? The patching process now is too long and complicated than when it was simple in 12.1 , It is now becoming too long to apply, offsetting the benefits of online patching. Before in 12.1, It was better and faster to shutdown and apply a patch.
if you forgot to run fs_clone, when you run prepare phase it will run internally fs_clone
fs_clone recreates the exact copy of patch file system from run filesystem
So phase=prepare has the most number of jobs being done including cleanup and fs_clone.