Oracle E-Business Suite R12.2.x : ADOP Online Patching Phases Explanation

 Oracle E-Business Suite R12.2.X : Adop Online Patching Phases Explanation

All patches starting from Release R12.2.X are online patches and is applied using AD online Patching utility (ADOP)

Imporatnat Points:

1. If patch does not contains new updates to files or database to the objects in system then is does not take any action .

2. If is detects a previously failed session.it will attempts to recover previously failed session.

3. Adop patching is applied in same way  there is no change in RAC enabled Oracle E-Business Suite.

==> Online Patching is classified into five main phases and three additional phases. <==

A) Prepare

B) Apply

C) Finalize

D) Cutover

E) Cleanup

Additional phases:-

F) abort

G) fs_clone

H) Actualize_all

1.. Online Patching Cycle – Prepare :-

syntax:- adop phase=prepare

3

1.1 :- Prepares the environment for patching by synchronizing the patch edition and the run edition on the file system.

2.1.. Creates a new patch edition in the database.

3.1.. Checks that environment is set to the run APPL_TOP.

4.1.. Checks to see if the database is prepared for online patching and enough space is available in the database.

5.1.. Check if the database user is edition-enabled i.e. at least one user ,PL/SQL API will return true if user is not edition-enabled then adop displays an error Users are not edition-enabled.

6.1.. Checks for adequate file system space and database using the TXK (Technology stack) script

$AD_TOP/patch/115/bin/txkADOPPreparePhaseSanityCheck.pl

7.1.. Generates a report about the important tablespace and report is created under

$APPL_TOP/admin/$TWO_TASK/out

8.1.. Checks for the existence of the “Online Patching In Progress” i.e. ADZDPATCH is a  concurrent program which ensure that any other concurrent program cannot run during an online patching cycle if they are compatible with new patching cycle.

9.1.. Invokes a TXK script to synchronize the patches which has been applied to the run APPL_TOP but not the patch $APPL_TOP using  $AD_TOP/patch/115/bin/txkADOPPreparePhaseSynchronize.pl script

2.. Online Patching Cycle – Apply:-

syntax:- adop phase=apply

3.1

2.1.. Executes patch drivers to update patch edition.

2.2.. There could be either one or more than one patches depending upon requirement and customization.

In adop apply phase online patching can be applied if 2 different ways:-

A.. Interactive patching (default):- User gives all the information needed by adop phase responding to series of prompts.

syntax :- adop phase=apply

 B.. No-Interactive patching :- User does not give any information whereas all the information   required are given through normal text file.

syntax:- adop phase=apply input_file=<patch_input.txt>

3.. Online Patching Cycle – Finalize:-

syntax:- adop phase=finalize

4

3.1.. Pre-compute DDL :- In this phase it pre-computes DDL to be run at Cutover i.e it revises any out of date indexes and Materialized View .

3.2.. Generates derived objects which cannot be editioned during run time, intermediate objects are created which will replace the original objects during cutover.

3.3.. Compile Invalid objects.

In finalize phase there are two different kind of modes:-

A.. Quick  :- This is default mode and adop skips gathering the database dictionary statistics.

syntax:- adop phase=finalize

B.. Full :- Adop gathers database dictionary statistics (not transaction tables statistics). This mode is userfull in case when RUP patches are applied where database is running with optimal performance.

syntax:- adop phase=finalize finalize_mode=full

4.. Online Patching Cycle – Cutover

syntax:- adop phase=cutover

5

4.1.. Finalize :- Invokes the finalize API in the database if required.

4.2.. Application Tier Services Switch 1:- Completes any in-progress concurrent requests and then shutdown services on current run APPL_TOP and restarts services on current patch APPL_TOP

4.3.. Database cutover :- Patch database edition becomes the new run database edition , using adzdpmgr.pl script

4.4.. File System Cutover:- Patch file system becomes the new run file system i.e the current patch APPL_TOP becomes the new run APPL_TOP and the current run APPL_TOP becomes the new patch APPL_TOP

4.5.. Retires Old Edition :- This phase disables access to the old database edition.

4.6.. Terminate Old Database sessions :- Terminates any database connection to old run edition of the database.

4.7.. Application Tier Services Switch 2 :- Shutdown services on old run APPL_TOP and starts up services on new run $APPL_TOP.

Note :- In case if there is some manual steps to  be performed ,then in cutover phase automatic start of application tier should be stopped .

syntax :- adop phase=cutover mtrestart=no  where default value for mtrestart is YES and giving value NO will not start application in cutover phase.

5.. Online Patching Cycle – Cleanup

6

syntax:- adop phase=cleanup

5.1.. Old code objects which are no longer visible in the run edition are dropped.

5.2.. Old data (rows and column) that is no longer visible in the run edition is deleted or dropped.

5.3.. Old database editions that no longer contain actual objects are dropped.

Note :- In adop, cleanup phase can be executed in three modes.

A.. Standard:- This is default mode and does minimum cleanup (deletes seed data which are no longer needed and drops covered_objects) . Reason behind using of standard mode default is to prevent SYSTEM tablespace growing too large.

B.. Quick :- Performs minimum clean up (deletes unneeded copies of seed data) and this mode requires least time for the processing.

C.. Full :- Performs maximum cleanup and Deletes unneeded code, storage columns and database edition.

6:- Online Patching Cycle – Abort

syntax :- adop phase=abort

7

 

6.1..Check for environment is set to the run APPL_TOP

6.2.. Checks for any previous session has an incomplete session, i.e whether the abort call is valid

6.3.. Checks for existence of a patch edition and drops one if its exists.

6.4.. Checks for concurrent program status if necessary cancels a concurrent program submitted in earlier run.

6.5.. Deletes the rows inserted for the pending session ID from the ad_adop_sessions and ad_adop_session_patches tables.

6.6.. After executing abort, full mode clean up shoule be run

adop phase=cleanup cleanup_mode=full

Note :- The abort phase is used to abandon a patching cycle before it completes and rollback any changes that have been made and this abort phase can be aborted any time before the cutover phase. Similarly in multinode environment abort phase should be executed in all node and in multinode environment which uses a non-shared file system then abort phase should be appended with autoskip=yes

adop phase= abort autoskip=yes

7.. Online Patching Cycle – fs_clone

7.1.. fs_clone phase is used to synchronize the patch file system with run file system and it should be run if it is explicitly guided to execute in read me of patch.

7.2.. This phase of patching should be execute before cutover phase and and cannot be executed with any other phase.

8.. Online Patching Cycle – actualize_all

As completion of each patching cycle, the database will accumulate an additional old database edition so if the number of old edition becomes huge system performance is affected and when the number of old editions reaches 25 or more then adop phase=actualize_all should be executed to drop all old database edition.

The actualize_all phase should be invoked as a command in following sequence order.

8.1.. adop phase=prepare

8.2.. adop phase=actualize_all

8.3.. adop phase=finalize finalize_mode=full

8.4.. adop phase= cutover

8.5.. adop phase=cleanup clean_mode=full

Miscellaneous Patch Online patching phases:-

Hotpatch Mode: – The hotpatch mode can only be used to apply patches that provide explicit support for it. Hotpatch mode applies changes directly to the run edition file system.

adop phase= apply apply_mode=hotpatch

Downtime Mode:-  Downtime mode is only supported for production user where it is explicitly documented in read me. This mode of patching does not use an online patching cycle and in this mode, adop will first confirm that the application tier services are down and then will proceed to apply the patch to the run edition of the Oracle E-Business Suite database and file system. Similarly this mode can be specified with apply phase only.

adop phase=apply patch=patch_number apply_mode=downtime.

Preinstall Mode:-  This patch mode is applicable only if the patch readme instructs in read me and generally used during the upgrade process to update AD utilities or pre-upgrade patches.

Syntax:- adop phase=apply patch=patch number preinstall=y