2014년 11월 6일 목요일

[FA] Applications DBA Online Patching Tool (adop)

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.

See Oracle E-Business Suite Maintenance Guide for a full description of
adop features, operation, and 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 patches to apply.
        This parameter is required when executing the apply phase.
        For language patches, you must also specify the driver file:
        patches=10124646_AR:10124646.drv,10124646_KO:10124645.drv
    restart=(yes|no)  [default: no]
        Resume a failed apply action from where processing terminated. Used in
        conjunction with 'abandon'.
    abandon=(yes|no)  [default: no]
        Specify action to be taken if a patch is not applied successfully. Used
        in conjunction with 'restart'.
    apply_mode=(online|downtime|hotpatch|bootstrap)  [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 bootstrap mode when requested by
        Oracle.
    apply=(yes|no)  [default: yes]
        To run adop in test mode (without applying any patches),specify apply=no

  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 any manual steps during
        downtime.
    cm_wait=<number>
        Specifies the number of minutes to wait until the ICM will be forced
        down. If not specified, will wait forever.

  Cleanup parameters:
    cleanup_mode=(full|standard|quick)  [default: standard]
        Quick mode provides the shortest execution time, by
        skipping non-essential actions.
        In addition to the tasks done in Quick mode, Standard mode drops
        covered objects.
        Full mode performs additional processing to remove all
        unused code, data, and old editions, so takes much longer.

  Fs_clone parameters:
    force=yes/no [default: no]
        force=yes option restarts a failed fs_clone operation.

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)
        Specifies whether to execute database actions. Required
        when using the allnodes parameter.

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

    -examples
        Common usage examples, such as:
        Complete patching cycle, running all phases in a single adop command:
        adop phase=prepare,apply,finalize,cutover,cleanup patches=12345

    -help
        This help screen.

댓글 없음:

댓글 쓰기