ORACLE APPS R12 ONLINE PATCHING Utility AD Online Patching (ADOP)

adop (AD Online Patching) utility to apply patches to the Oracle E-Business Suite file system or database

 

1. ADOP Phases :
    

adop phase = prepare

adop phase=apply patches=<patch1>,<patch2>

adop phase=finalize

adop phase=cutover

adop phase=cleanup

adop phase=abort

adop phase =fs_clone

 

 Standard phases:

  prepare       - Prepare the instance for patch application.

  apply         - Apply patches (to the patch edition).

  finalize      - Ready the instance for cutover.

  cutover       - Make the patch edition the new run edition.

  cleanup       - Drop obsolete objects and data from old editions.

 

  Special phases:

  abort         - Abort the current patching operation.

  fs_clone      - Copy the run file system to the patch file system.

 

(NOTE : ALL patches shuld be unzipped and copied to “<S_NE_BASE>/EBSapps/patch” )

 

1. ADOP NOTES:
    

      1. Allow the patching while up and running the system.

 

r12.2 having 2 file system

1.patch file system

2.Run file system

 

all patches will apply to the patch file system during that time

all applications are run from run file system ,so it will not impact the run file system file so no need to down the application.

      2. In the adop phase "cutover" patch file system become RUN file system             during      that time need downtime.

 

      3.  12.2 and higher will use this method.

      4.   Traditional method will not support in 12.2  .

      5.   adop phase= fs_clone this to copy run file system to patch file system

 

Note : Before starting this cut over phase to complete then PATCH   file system became run ,so now in the run file system you need to do this step, during this step RUN file system sync to patch file system

 

           

 

Scenario :

You have noticed that the on the patch edition there are lot of patches applied. You did the cutover and now customer wants to begin the next patching cycle. Since there are lots of patches applied you decided to do file system cloning , We can skip this one but next patch cycle prepare phase will take more time.

     6.   No need to enable the maintenance mode.

     7.   No need to stop and start the services adop will take care all the steps

            in the cutover phase.

    8 .   Edition based redefinition (EBR) feature allows editing the code objects in  the database it provides new object types such as editions, editioning views, and cross-edition triggers, all of which are part of the Online Patching infrastructure

9.    adop intenally calls the adpatch ,but in r12.2 we can not directly call the   adpatch.

 

  10.    We can apply multiple patches in adop in single patch cycle.

  11.    Run and patch file system must be same server.

  12.    No need to pass the driver file information and no need to go to patch directory to apply ,adop directly check the patch directly from “<s_ne_base>/EBSapps/patch" location.

  13.    adop hot patch mode ,patch shuld be run in the run file system.

  14.    ADADMIN can run only on the patch file system when the patch is in progress

           ERROR:  Patching cycle in progress - run this utility from patch file system.

            You can only run it from run file system when not patching.

15.      Few  Functionality  are Disabled During An Online Patching Cycle          (ADZDPATCH) (Doc ID 1586609.1)

prepare phase the ADZDPATCH concurrent program is run and will continue to run through the entire patching cycle (prepare, apply, finalize, cutover).

This program prevents certain concurrent programs from being run.

These programs are made incompatible with ADZDPATCH by functional developers to avoid data inconsistencies.

ERROR :

MSG-00000: OPT Currently patch application is in progress. <Name Of Failing Program> after patch application.

MSG-00000:  101504: non-ORACLE exception

REP-1419: MSG-00000: OPTCurrently patch application is in progress. Validate Application Accounting Definition after patch application

 16.   adop with merge option

          adop phase=apply patches=18359219,18838658 merge=yes workers=6

 17.      The adop utility always runs from the run edition file system. It automatically sets its environment correctly, regardless of the edition it is run from

  18.    adop prompts for the Oracle Application Object Library (APPS), SYSTEM, and WLSADMIN passwords.

  19.    ADOP default apply mode is auto , you can run interactive mode .

  20.    We cannot connect to database when patch edition is not prepared

The application-tier Patch Edition environment is configured to connect to           the database patch edition by default. If a database patch edition is not active, then attempting to connect to the database from the application-tier patch edition environment will fail.

ERROR:

ORA-00604: error occurred at recursive SQL level 1

ORA-20099: E-Business Suite Patch Edition does not exist.

ORA-06512: at line 29

21.      If you want to modify the configurations like xml changes, change the values in the patch file system and run empty patch cycle. All changes now effect in the both the file systems.

            Adop phase=prepare

            Adop phase=cutover

            Adop phase=cleanup

 

 

1. R12.2.3 file systems :

In Release 12.2, the following directory structure exists to support the run edition and patch edition file systems:

<s_base>/<sid>/fs1 (for example, /u01/122/prod/fs1)

<s_base>/<sid>/fs2 (for example, /u01/122/prod/fs2)

$RUN_BASE=/u01/122/prod/fs2

$PATCH_BASE=/u01/122/prod/fs1

EX:

/oracle/applmgr/fs1 -- patch file system

/oracle/applmgr/fs2 -- run file system

/oracle/applmgr/fs_ne

        While login it will ask for patch OR Run File system

echo $FILE_EDITION

 

 

Adop –status : ADOP status While applying  is in progress

ADOP status on phase “Apply” running

 

 

 

 

If Apply phase is Fails :

 

After Finalize completed:

 

 

After cutover and cleanup completed:

 

After starting the prepare phase of next patch cycle STATUS “NOT started “

 

adopscanlog -latest=yes – After completion of patch ,to check the log file info.

adopscanlog -latest=yes -phase=<phase_name>

adopscanlog -help

 

 

1. Examples:

 

Adop phase=prepare

Adop phase=apply patches=18672060,18242621,18454567,18617687,18616135,18219094,18423655,18172151,18336110,18289828,17984822 workers=8

 

Adop phase = cutover, cleanup

Adop phase=fs_clone allnodes=no

Adop phase=apply patches=<patch> restart=yes :To continue the failed job

Adop phase=apply patches=<patch> abandon=yes :To continue the failed job from starting
adop phase=apply patches=<patch>  apply_mode=downtime : to apply patch in downtime  this option mainly for major upgrade.


adop phase=apply patches=<patches> wait_on_failed_job=yes ---If patches fail we can continue after fixing the error with adctrl


adop phase=apply patches=<patches> options=forceapply


adop phase=apply patches=<patches> merge=yes -- For merging the patches


adop phase=apply patches=<patches> patchtop=/patches






Adop apply=<patch> hotpatch=yes : to apply the patch on Run file system without shutdown application

 

 

 

1. ISSUES :

 

1. list of patches which is applied in that list  one of the patch is error while generating forms/pll's :

 

path apply status became "FAILED status"  even rest of the patches are

applied successfully and we cannot continue the rest of the patches until fix.

How to skip the patch and manually fix the pll issue.

Adop phase=apply patches=18672060,18242621,18454567,18617687 abandon=no restart=yes flags=autoskip

 

NOTE: How To Allow ADOP To Continue As If It Were Successful After Hitting An Error While Applying Patch(es) (Doc ID 1672449.1)

 

NOTE: make sure to see the autoskip log files if you are using autoskip option also we can find using below script.

select BUG_NUMBER,STATUS,NODE_NAME from ad_adop_session_patches where status='S' and  ADOP_SESSION_ID=70

            Stauts “s” means patch applied with autoskip option.

 

1. All  adop phases are started same time  and all phases are completed only on the admin server and rest of the slaves server not completed that time we  may face node abundant and master and slaves may not contact  as already cutover completed in the master.
   Adop status will show only master node status.
   This situation we need to start the refresh of master node to slave nodes.

Oracle E-Business Suite Technology Stack and Applications DBA Release Notes for R12.TXK.C.Delta.4 and R12.AD.C.Delta.4 (Doc ID 1624423.1)

1. ERROR: /dvai8i/applmgr/fs1/EBSapps/10.1.2 is not registered in the inventory
   Corrective Action: Provide the location of a valid inventory file. If you believe the inventory is valid, you may want to attach the /dvai8i/applmgr/fs1/EBSapps/10.1.2.
   Inventory location we can check from /etc/Orainst.loc
   /dvai8i/applmgr –location of inventory
    
   SOL : This may cause due to the adop phase will update the inventory by flag “ removed” we need to remove that flag in inventory.xml
    
2. Below error while prepare phase .
   ValidateDomainEditable:

       [ERROR]: Domain might be locked by some other WLS user process

SOL :       Rename the “./user_projects/domains/EBS_domain_dvai8i/edit.lok” file in the patch file system and start the prepare again.

Please Refer :

“WebLogic Deployments Failed And Left Admin Server Locked [Deployer:149164] (Doc ID 1286134.1)

Oracle E-Business Suite Release 12.2: Validations Performed By the adop Online Patching Utility (Doc ID 1678355.1)

 

$ find . -name "edit.lok"

./user_projects/domains/EBS_domain_dvai8i/edit.lok

$ find . -name "config.lok"

/dvai8i/applmgr/fs1/FMW_Home/user_projects/domains/EBS_domain_dvai8i/servers/AdminServer/tmp

   ./user_projects/domains/EBS_domain_dvai8i/config/config.lok

WebLogic Deployments Failed And Left Admin Server Locked [Deployer:149164] (Doc ID 1286134.1)

Oracle E-Business Suite Release 12.2: Validations Performed By the adop Online Patching Utility (Doc ID 1678355.1)

 

 

1. log location ADOP :

 

<s_ne_base>/EBSapps/log/adop/<adop_session_id>/

/oracle/applmgr/fs_ne/EBSapps/log/adop/adop_20140527_160551.log

           WORKER log file location :

<s_ne_base>/EBSapps/log/adop/<adop_session_id>/apply_<no>/context_name/<patch_no>/log/

/dvai8i/applmgr/fs_ne/EBSapps/log/adop/70/apply_20140630_113810/dvai8i_vmohsvais031/17316665/log

AUTO skip log path :

<s_ne_base>/EBSapps/log/adop/<adop_session_id>/apply_<no>/context_name/<patch_no>/log/autoskil.log

/dvai8i/applmgr/fs_ne/EBSapps/log/adop/70/apply_20140630_095325/dvai8i_vmohsvais031/18660269/log/autoskip.log