If you are in process of upgrading to Oracle E-Business Suite 12.2.4, you would have went though this critical phase in the upgrade which is to apply the Online Patching Enablement patch:
13543062:R12.AD.C.
It’s very common to run into errors with this patch in the first try and have to apply it couple of times, in order to get all issues fixed and get online patching enabled. The recommended command to apply this patch is:
adpatch options=hotpatch,forceapply
When the time comes to re-apply the patch to fix problems, if you use the same command to reapply the patch, you will notice that the patch completed normal with in no time and nothing happens in the back end. This is because of a specific feature from Adpatch. ADPATCH by default skips jobs that are marked as “run successfully” in previous runs or as part of another patch. So we have to force it re-run those jobs. This can be done by using command below:
adpatch options=hotpatch,forceapply,nocheckfile
Sometimes we run into cases where Online Patching Enablement patch completes as “normal” and the actual online patching feature gets enabled where we see that a schema or two have failed to enable the EBR feature. As soon as APPS schema gets EBR enabled by this patch, even though other custom schemas failed to get enabled, Adpatch gets disabled and we are forced to adop utility from then on. In this scenario, we can still re-apply the Online Patch Enablement using Adpatch after setting the environment variable below:
export ENABLE_ADPATCH=YES
I see that online patching enablement exercise for every customer is a unique experience. Do post your experiences with this online patching enablement patch in the comments section. I’d love to hear your story!
Discover more about Pythian’s expertise in the world of Oracle.
4 Comments. Leave new
I’ve never seen (I hope it’s only my experience) Online Patching Enablement execution without errors. But it does not mean we should re-run patch installation once again any time we see errors in AD_ZD_LOGS table. Our experience shows us that the next adop session completes all the works haven’t been done during Online Patching Enablement. Of course there shouldn’t be any serious errors in AD_ZD_LOGS like APPS schema wasn’t been EBR enabled (in that case I believe something went terribly wrong and re-run could be wasting the time, one should clarify the main reason of error).
Also because of works for enable EBR for error-ed objects the next adop session usually takes much more time, it should be considered when we schedule our update.
Dear Friend,
My compay is implementing Oracle EBS R12.2 and Oracle Database 12c. I have some requirements:
1/ I want to setup Change Management process consist of: master data, DFF, KFF, new forms, new reports, new tables, new views, v.v….
2/ I want the system support copy and transfer master data, DFF, KFF, new forms, new reports, new tables, new views, v.v…. from instance DEV to instance PROD.
3/ I want to the system automatic detec and download patch.
4/ I want the system support Incident Management, Problem Management process.
Regards,
CUONGNT
Dear Friend,
My company is implementing Oracle EBS R12.2 and Oracle Database 12c. I have some requirements:
1/ I want to setup Change Management process consist of: master data, DFF, KFF, new forms, new reports, new tables, new views, v.v….
2/ I want the system support copy and transfer master data, DFF, KFF, new forms, new reports, new tables, new views, v.v…. from instance DEV to instance PROD.
3/ I want to the system automatic detect and download patch.
4/ I want the system support Incident Management, Problem Management process.
Regards,
CUONGNT
THanks a lot for your blog, i found it very helpful we are also in the same situation in online patching enablementt were able to resume it.