On this page
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.
Learn more about Pythian by reading the following blogs and articles.
With Pythian, you can accomplish your data transformation goals and more.
© 2025 All rights reserved.