Scribd Logo
Upload

Welcome to Scribd!

  • 41 views

    Step by Step To Apply Patches in Oracle Apps R12

    Uploaded by

    rap0777
    The document discusses the steps to apply patches in Oracle Apps R12.2 using the adop utility. There are three file systems - FS1 for the production system, FS2 which is an exact copy for patching, and FS-NE for non-edition files. The five phases of online patching with adop are prepare, apply, finalize, cutover, and cleanup. The steps are to download the patch, run adop with the prepare phase, check the status, run apply with the patch number, run finalize, run cutover, and finally run cleanup after go-live. If patching fails, run abort followed by a full cleanup.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Step by Step To Apply Patches in Oracle Apps R12

    Uploaded by

    rap0777
    41 views3 pages
    The document discusses the steps to apply patches in Oracle Apps R12.2 using the adop utility. There are three file systems - FS1 for the production system, FS2 which is an exact copy for patching, and FS-NE for non-edition files. The five phases of online patching with adop are prepare, apply, finalize, cutover, and cleanup. The steps are to download the patch, run adop with the prepare phase, check the status, run apply with the patch number, run finalize, run cutover, and finally run cleanup after go-live. If patching fails, run abort followed by a full cleanup.

    Original Description:

    Original Title

    Step by Step to Apply Patches in Oracle Apps R12

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the steps to apply patches in Oracle Apps R12.2 using the adop utility. There are three file systems - FS1 for the production system, FS2 which is an exact copy for patching, and FS-NE for non-edition files. The five phases of online patching with adop are prepare, apply, finalize, cutover, and cleanup. The steps are to download the patch, run adop with the prepare phase, check the status, run apply with the patch number, run finalize, run cutover, and finally run cleanup after go-live. If patching fails, run abort followed by a full cleanup.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    41 views3 pages

    Step by Step To Apply Patches in Oracle Apps R12

    Uploaded by

    rap0777
    The document discusses the steps to apply patches in Oracle Apps R12.2 using the adop utility. There are three file systems - FS1 for the production system, FS2 which is an exact copy for patching, and FS-NE for non-edition files. The five phases of online patching with adop are prepare, apply, finalize, cutover, and cleanup. The steps are to download the patch, run adop with the prepare phase, check the status, run apply with the patch number, run finalize, run cutover, and finally run cleanup after go-live. If patching fails, run abort followed by a full cleanup.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    Step by Step to apply patches in Oracle Apps R12.2.

    by
    using adop utility

    Note: The classic patching model is designed to minimize downtime by running


    as fast as possible, using whatever resources are needed. In contrast, the
    online patching model is designed to minimize downtime by allowing patching
    operations to be performed while users remain on the system.

    As we know in R12.2, There are 3 File System Installed.

    1: FS1 – (RUN_EDITION) Production file system that is used by online users


    when system is being patched.

    2: FS2 – (PATCH_EDITION) Exact copy of production(fs1) used by the patching


    tools. Changes do not affect the running application(RUN_EDITION). 

    When patching is completed and we do CUTOVER, then patching tool swaps


    the FS1 and FS2 file systems. 

    It means, FS2  file system will become FS1 , which will be access by the users.

    3: FS-NE (Non-Edition) – This is a non-edition file system which stores data that
    is stored in a file system like log file, report file and patch top files.

    There are below 5 Phases of ADOP(online patching):

    1) PREPARE
    2) APPLY
    3) FINALIZE
    4) CUTOVER
    5) CLEANUP

    Steps:-
    1. Download the patch and unzip on patch_top.

    2. Must go through Readme.html or readme.txt.


    3. Prepare the system for patching

         a.  we can run the .env file . or the adop utility sets its own environment.
         b. Then run the below command for prepare the System for patching:

    $ adop phase=prepare

    4. Wait for the prepare phase to be complete.


    Please check the status from below points:

    $ adop -status 
    Enter the APPS username: apps 
    Enter the APPS password: 

    5. After completion Prepare phase, go to next phase called Apply phase:


    $adop phase=apply patches=1234567
    Enter the APPS password:
    Enter the SYSTEM password:
    Enter the WLSADMIN password:
    Please wait. Validating credentials...

    6 . After completion of apply phase, goto next phase called Finalize phase:
    i.e like Ready the instance for cutover

    $ adop phase=finalize
    Enter the APPS password:
    Enter the SYSTEM password:
    Enter the WLSADMIN password:
    Please wait. Validating credentials...

    7. After completion of Finalize phase, goto next phase called Cutover:


    $ adop phase=cutover
    Enter the APPS password:
    Enter the SYSTEM password:
    Enter the WLSADMIN password:
    Please wait. Validating credentials...

    Note: Keep checking Status after every Phases.

    8. After completion of Cutover phase, run next Cleanup Phase


    We can do this step after instance is released to Customer.
    $adop phase=cleanup
    Enter the APPS password:
    Enter the SYSTEM password:
    Enter the WLSADMIN password:

    Note: 
    If there are some reason either the prepare or apply phase failed or any
    problems then you can abort this patching cycle.

    $adop phase=abort

    But always remember, after running abort, you must always run a full
    cleanup as: 

    $adop phase=cleanup cleanup_mode=full

    So, this will remove all columns that were added by the patches but are no
    longer needed because of the abort. 
    And If that columns are not removed, then that may create problems in a later patching
    cycle.

    You might also like