12.2: Running Maintenance Procedures During An Open Online Patching Cycle (Doc ID 1580108.1)

Last updated on JUNE 12, 2016

Applies to:

Oracle Applications DBA - Version 12.2 and later
Information in this document applies to any platform.

Goal

Let us use an example to explain the question we have.

You initiate a patching cycle on Monday. You are planning to perform cutover on the weekend. During the week there is a production issue and to resolve that you need to run adadmin to regenerate forms or jar files.
e.g. fndutil.jar.


After running adadmin the current RUN file system has the updated fndutil.jar file and the PATCH file system has the old file. When you perform cutover (upon completion of patching operations) the PATCH file system becomes the RUN file system and the old file will be carried over to run. As a result the new RUN file system will not have latest file.

How do we overcome this kind of situation? Do we need to run adadmin on both file systems?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms