ADOP Basic Questions & Answers

What is the concept of ADOP in R12?

Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied.

‘adop’ is the utility you use to apply application patches in R12.2

 Note: Once you enable ADOP on R12.2 system you cannot use adpatch utility



What is the patch directory in R12.2


In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to  $NE_BASE/EBSapps/patch
$NE_BASE points to <Non-Editioned-filesystem-directory> or you can use $APPL_TOP_NE/..

Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files.

If you want to use other directory to maintain the patches   then you need to use the below parameter while applying the ADOP.

i.e. adop phase=apply patchtop=/u01/R122_Patches/<Patch_number>


From which  location to ADOP command to execute?

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

RUN


How to findout on which environment we logged in?

When you set the environment file as soon as you logged in as “applmgr” it prompts  RUN/ PATCH Files system with full location and also prompts select the required files system

 
[root@R12test ~]# su - appltest

   E-Business Suite Environment Information


  RUN File System           : /u01/oracle/testappl/fs1/EBSapps/appl

  PATCH File System         : /u01/oracle/testappl/fs2/EBSapps/appl

  Non-Editioned File System : /u01/oracle/testappl/fs_ne

  DB Host: oadbph.mfc.corp.mckee.com  Service/SID: TEST

  E-Business Suite Environment Setting

  - Enter [R/r] for sourcing Run File System Environment file, or

  - Enter [P/p] for sourcing Patch File System Environment file, or

  - Enter anything else to exit
  Please choose the environment file you wish to source [R/P]: R





What happens when ADOP command is executed ?

adop will perform all the tasks required to apply the patch:

Ø  Reads patch metadata to determine patch dependencies and requirements

Ø  Attempt to recover previously failed patching session (if any)

Ø  Reads and validate the patch/product driver files

Ø  Compares version numbers of existing files against the patch files and Backs up all existing files that will be changed by the patch

Ø  Copies files

Ø  Archive files in libraries

Ø  Relinks executables, Generates forms, reports, messages, graphics, and Java archive (JAR) files

Ø  Compiles JSP files and invalid database objects. Updates database objects

Ø  Runs AutoConfig if required

Ø  Saves patch information to the database

Can we merge applications patches apply in R12.2?

 Yes,  but the application of merge patches are different as ADOP utility itself has a feature of merging multiple patches.

In earlier EBS releases, the AD Merge Patch tool was used to merge multiple patches into a single patch, so that the common tasks only needed to be performed once.



By default, adop will automatically merge all patches specified with the ‘patches’ parameter.

You can still use earlier AD Merge Patch tool but you should disable adop’s merging of patches, by adding to the adop command line > ‘merge=no’

Eg:   adop phase=apply patches= 18471329, 18132674….

Note: You can give any number of patches and with comma separated value and apply them in a single command shown above.

R12.2_ Online Patching basics

ADOP over view:

=============

In Release 12.2.0 and higher, patching is performed by running the new adop (AD Online Patching) utility. We must use adop utility instead of adpatch utility that was provided in previous releases.  Applications EBS 12.2 introduces online patching using ADOP utility. Technology patches are applied to the patch file system then ADOP is used to propagate the change into run within the context of a patching cycle.

To start Online Patching, we need to use:

 $ adop phase=prepare

To Apply Patches, we need to use:

$ adop phase=apply patches=9876789,8768904

ADOP Features:

============

To obtain help about the basics of adop operation, use:

 adop –help

 This will display the following text:

 Applications DBA Online Patching Tool (adop)

 Usage: adop [phase=<phase,phase,...>] [patches=<patch#,patch#,...>]

 [<parameter>=<value> ...] [input_file=<filename>]

 Enter adop -examples for a detailed list of parameters and their usage.

The phase parameter specifies the parts (phases) of the online patching cycle to be executed.

The five standard phases are executed in the order shown below.

 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.

There are also three special phases, for use when needed.

 Special phases:

 abort - Abort the current patching cycle.

 actualize_all - Create new copies of all code objects in the patch edition.

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

Phase-specific parameters control operation of a particular phase:

Apply parameters:

Patches=<patch#>[,<patch#>...]

 A single patch or comma-separated list of patch to apply.

 This parameter is required when executing the apply phase.

 For language patches, you must also specify the driver file:

 patches=10987654_AR:10987654.drv,10987654_KO:10124645.drv

 restart=(yes|no) [default: no]

Resume a failed apply action where processing left off.

 abandon=(yes|no) [default: no]

 Re-apply a failed patch from the beginning.

Finalize parameters:

 finalize_mode=(full|quick) [default: quick]

 Quick mode will provide the shortest execution time, by skipping non-essential additional actions.

 Full mode performs additional actions such as gathering statistics, which may improve performance after cutover.

Cutover parameters:

 mtrestart=(yes|no) [default: yes].

 Specifies whether to restart application tier servers after cutover. Leave at default unless performing manual steps during downtime.

Cleanup parameters:

 cleanup_mode=(full|quick) [default: quick]

 Quick mode provides the shortest execution time, by

 skipping non-essential additional actions.

 Full mode performs additional processing to remove all unused code, data, and old editions. May take a long time.

General parameters apply to all phases:

 workers=<number> [default: computed]

 Number of parallel workers used to execute tasks.

 Default value is computed principally according to number of available CPU cores.

input_file=<file_name>

 As well as being entered directly on the command line, adop parameters can be specified in a text file, with

 one <parameter>=<value> on each line of the file.

 Examples:

 phase=prepare,apply,finalize,cutover,cleanup

 patches=123456

 workers=4

 Command line parameters override input file parameters.

 loglevel=(statement|procedure|event|warning|error|unexpected)

 [default: event]

 Controls the level of diagnostic log detail displayed.

 allnodes=(yes|no) [default: yes]

 Specifies whether actions should be executed on all application tier nodes of a multi-node system.

 action=(db|nodb) [default: db]

 Specifies whether to execute database actions (as well as file system actions).

 -status [<session_id>]

 Display status of the latest adop session, or a specified session.

 -help

 This help screen.

 -examples

Source copied from other sites  for my reference.