Please contact me :- ajith.narayanan@infrastack-labs.in

Tuesday, October 7, 2014

All patches to an editioned system are
applied in below explained sequence of an Online Patching Cycle.

1)Prepare
- creates the patch edition.

“ADOP” is the new ad utility given by
Oracle for patching the Oracle Apps R12.2 environments.

ADOP is similar to our old adpatch.

What actually happens during “PREPARE”
phase?

Before applying a patch, you must start
an Online Patching Cycle. This is done using the adop "prepare"
command. Connect to the primary application-tier node of your target system and
source the run edition environment file. Then execute the prepare command.

Note:- In case, the previous
patch cycle did not complete its cleanup phas, The new adop prepare phase will execute
the clean-up phase of previous cycle, if needed, and then proceed with
preparing the new patch edition for new Online patching cycle.

Create
a new database patch edition

Synchronize
the file system patch edition with the run edition

Configure
the patch edition for use by the patching tools

File system synchronization may be done
by applying the delta (changes) from the previous patching cycle, or by
re-creating the entire patch edition file system as a fresh copy of the run
edition (called "fs_clone"). When complete, check the exiting status
code (success is '0'):

adop exiting with status = 0 (Success)

Once prepare phase is complete, the
database and file system patch edition will contain a copy of the run edition
code and seed data.

Now the instance is ready for ARU or
Manual Patching to the Patch Edition

2)Apply
- apply ARU or manual patches to the patch edition.

Below steps can be followed for ARU
Patches

Download
the patch bundle from ARU from metalink.

SCP
the ZIP files in the "fs_ne/EBSapps/patch" directory on the Middle-tier

After applying an ARU patch or a manual
patch you can look at the patch edition file system or database status to
verify that the patching actions were successful and that the resulting patch
edition code and seed data are as expected.

üThe
finalize phase is used by the Online Patching system to perform any final
actions needed to make the system ready for the fastest possible cutover.

The
finalize command is run as follows:

[ajithpathiyil1:ajithebs:applmgr]>
adop phase=finalize

The
finalize command should not have any error, In case of error, the system is not
ready for cutover

üAfter
successful completion of the finalize phase, the system is ready for cutover

Note:- We
do not need to execute the cutover immediately; Cutover can
be delayed until a convenient time in the future. In the meantime, We may also
apply additional patches if needed, but you will need to run the finalize phase
again after doing so.

4)Cutover
- Promote Patch Edition to be the new Run Edition.

üThe
cutover phase will configure the patch edition to become the new run edition,
and restart the application on this new run edition.

Note:- Since
the run/patch designation of the dual file systems are swapped during cutover,
you must re-source the run edition environment directly after cutover.