EBS R12.2 ADOP options

R12.2 ADOP options

1)  To check adop status

      adop -status -detail     

2)  To apply patch in hotmode (for multiple patches use patches=patchnumber1, patchnumber2)

    adop phase=apply patches=<patch number> hotpatch=yes patchtop=<location of patch downloaded>

3) To apply patch in downtime mode (for multiple patches use patches=patchnumber1, patchnumber2)

   adop phase=apply apply_mode=downtime patches=<patchnumber> patchtop=<location of patch downloaded>

 4) Along with above adop commands you can use below options to specify workers count also adop process exists once worker fails so using wait_on_failed_job wait for you to fix FAILED workers

Example:

adop phase=apply patches=<patch number> hotpatch=yes patchtop=<location of patch downloaded>

workers=<number of workers> wait_on_failed_job=yes

5) To restart failed adop patch:  

adop phase=apply patches=<patch number> hotpatch=yes patchtop=<location of patch downloaded> restart=yes abandon=no

6) When adop fails, to check log file errors:

    adopscanlog -latest=yes

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 online patching cycle.
  actualize_all - Create actual copies of all code objects in the patch
                  edition.
  fs_clone      - Copy the run file system to the patch file system.

General parameters applicable 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.  Command line parameters override input file
        parameters.

    loglevel=(statement|procedure|event|warning|error|unexpected)
        [default: event]
        Controls the level of diagnostic log detail displayed on the console.

    prompt=(yes|no)  [default: yes]
        Specifies whether adop should prompt for user input on warnings.
        By default adop will ask user whether to continue or exit on
        some warning messages.  If this parameter is set to "no" adop
        will remain fully non-interactive, and will continue past any
        warning messages without user confirmation.

Phase-specific parameters control operation of a particular phase:

  Prepare Parameters:

    skipsyncerror=(yes|no)  [default: no]
        Specifies whether to ignore errors that may occur during incremental
        file system synchronization.  This might happen if you applied
        a patch in the previous patching cycle that had errors but decided
        to continue with the cutover.  When the patch is synchronized on
        the next patching cycle, the apply errors may occur again, but
        can be ignored.

    sync_mode=(delta|patch) [default: patch]
        Specifies the method used to synchronize the patch file system
        with the run file system.
        'delta' mode uses the file system synchronization command specified
        in $AD_TOP/patch/115/etc/delta_sync_drv.txt.
        'patch' mode reapplies the patches that were applied on
        the run file system.

  Apply parameters:

    patches=<patch#>[,<patch#>...]
    patches=<patch_directory>:<driver>[,<patch_directory>:<driver>...]
        This parameter specifies a comma-separated list of patches to be
        applied.  Patches can be specified either as the patch number or
        by the patch directory and driver file.  All patches are expected
        to be in the $PATCH_TOP directory on all tiers.  Patches are applied
        serially unless the merge=yes parameter is specified.

    restart=(yes|no)  [default: no]
        Use restart=yes to resume the previous failed apply command
        from where processing terminated.

    abandon=(yes|no)  [default: no]
        Use abandon=yes to abandon the previous failed apply command
        and start a new apply command.

    apply_mode=(online|downtime|hotpatch)  [default: online]
        Use online mode to apply a patch to the patch edition during an
        online patching cycle; downtime mode to apply a patch to the
        run edition when application services are down; and hotpatch
        mode to apply a patch to the run edition when application
        services are up. Only use hotpatch mode when explicitly
        directed by documentation.

    apply=(yes|no)  [default: yes]
        To run adop in test mode (without applying any patches), use apply=no

    options=<patch_option>[,<patch_option>...]
        Advanced options to control patching behavior.
        See adop -examples for details.

    flags=<patch_flag>[,<patch_flag>...]
        Advanced flags to control patching behavior.
        See adop -examples for details.

  Finalize parameters:

    finalize_mode=(full|quick)  [default: quick]
        Quick mode will provide the shortest execution time, by
        skipping non-essential actions.
        Full mode performs additional actions such as gathering
        statistics that 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 you need to perform manual steps during the
        cutover downtime.

    cm_wait=<minutes>  [default: forever]
        Specifies the number of minutes to wait for Concurrent Manager
        shutdown.  Adop cutover starts by requesting a concurrent manager
        shutdown and then waits for in-progress requests to complete.
        If Concurrent Manager does not shutdown within the specified
        time limit, remaining concurrent requests will be killed and
        cutover will proceed.

  Cleanup parameters:

   cleanup_mo de=(full|standard|quick)  [default: standard]
        Quick mode provides the shortest execution time, by
        skipping non-essential actions.
        Standard mode performs additional processing to drop
        obsolete code objects from old editions.
        Full mode performs additional processing to drop empty
        database editions and unused table columns.

  Fs_clone parameters:

    force=yes/no [default: no]
        Use force=yes to restart a previous failed fs_clone command from
        the beginning.  By default fs_clone will restart where it left off.

Command flags:

    -status [<session_id>]
        Display status of the latest adop session, or a specified session.

    -validate
        Runs ADOP validations for verifying the current system state.

    -examples
        Display extended help information with common usage examples.

    -help
        This help screen.


adop exiting with status = 0 (Success)
[applmgr@my-domain APPS]$