Logo Background

Patching Steps In Oracle Applications

  • By on June 20, 2009 | No Comments

    Oracle E-Business Suite or Applications 11i often came out with their patch (patchset or one-off patch) to fix the bug in the application.

    So it was recommended to apply those patch as it will reduce the issue in terms of functionality or performance issue.

    You need to performs the patching step by step on top of the Oracle Applications, please check on the details as below.

    Check pre-requisites on the patch

    Before you apply the patch, ensure that you have read the READ ME section of the patch to check on if there’s any pre-requisites patch required.

    If there’s a pre-requisites patch list, check in the database of the Oracle Applications to see if the pre-requisites patch or the patch itself already applied before.

    SELECT * FROM ad_bugs
    WHERE bug_number=<patch number>

    Sometimes the pre-requisites patch was superseded by another new patch, so I advise you to check carefully

    Backup the Apps Server & DB Server

    Application Server Backup

    Let’s assume all the application files was resides in /oracle/apps directory in prodappl, prodcomn and prodora. You can backup all the application files to a location before transferring the backup files to tape

    $ mkdir /support/PROD_backup/  
    $ cd /oracle/apps
    $ tar -cvf /support/PROD_backup/PROD_backup_<DDMMYY>.tar prodcomn prodappl prodora

    Database Server Backup

    The DBA has to perform the database backup activities just before the patching activities start
    1. Shutdown Oracle Application and Oracle Database
    2. Start the synchronization between database storage with BCV mirror
    3. Disconnect database storage from BCV mirror
    4. Startup Oracle Database
    5. Backup BCV mirror copy to tape

    Notes: In case there’s no BCV, then DBA should work with server guy on the backup procedure to tape without involving BCV in picture.

    Oracle Shutdown Steps

    In this case, I assume your Oracle Applications was configured to have concurrent, reports, form server and Apache server was sitting in 1 box. While Oracle Database was running on single instance.

    Oracle Applications Shutdown

    Shutdown Application and Concurrent on Application Tier using the command below: -

    $ $COMMON_TOP/admin/scripts/$CONTEXT_NAME/adstpall.sh apps/<password>

    Notes: Please make sure no lines is selected when perform ps -ef | grep LIB or ps -ef | grep FND where these are the running concurrent process.

    Oracle Database Shutdown (optional)

    $ lsnrctl stop <listener name>
    $ sqlplus /nolog
    SQL> connect / as sysdba
    SQL> shutdown immediate

    Notes: The database shutdown script should be executed by DBA and make sure no lines is selected when perform ps -ef | grep mon. Sometimes if the shutdown immediate command took a long time run, use the command ps –ef | grep smon. smon is a system monitor for table monitoring and use the command below to see the details on smon processes

    $ truss –p <smon Unix PID>

    Oracle Startup Steps

    Again, I assume your Oracle Applications was configured to have concurrent, reports, form server and Apache server was sitting in 1 box. While Oracle Database was running on single instance.

    Oracle Applications Startup

    Shutdown Application and Concurrent on Application Tier using the command below: -

    $ $COMMON_TOP/admin/scripts/$CONTEXT_NAME/adstrtal.sh apps/<password>

    Oracle Database Startup (optional)

    $ lsnrctl start <listener name>
    $ sqlplus /nolog
    SQL> connect / as sysdba
    SQL> startup

    Begin Oracle Applications Patching

    Run adadmin to enable the maintenance mode

    You have to enable the maintenance mode before proceed to patching.

    $ adadmin
     
    AD Administration Main Menu
    --------------------------------------
     
    1. Generate Applications Files menu
     
    2. Maintain Applications Files menu
     
    3. Compile/Reload Applications Database Entities menu
     
    4. Maintain Applications Database Entities menu
     
    5. Change Maintenance Mode
     
    6. Exit AD Administration

    Select option (5) Change Maintenance Mode and Enable Maintenance mode. Remember, you need to have SYSTEM password and APPS password in order to run adadmin utility.

    Run adpatch to apply the application patch

    1. Upload patch files to server and run unzip
    2. Go through the READ ME files before you start the patching.
    3. Run adpatch (also requires SYSTEM password and APPS password)
    4. Run autoconfig (optional) if there’s any changes of the $CONTEXT_FILE on the patching activity

    $ cd $COMMON_TOP/admin/scripts/$CONTEXT_NAME
    $ ./adautocfg.sh

    Run adadmin to disable the maintenance mode

    You have to disable the maintenance mode after patching and before you startup Oracle Applications

    $ adadmin
     
    AD Administration Main Menu
    --------------------------------------
     
    1. Generate Applications Files menu
     
    2. Maintain Applications Files menu
     
    3. Compile/Reload Applications Database Entities menu
     
    4. Maintain Applications Database Entities menu
     
    5. Change Maintenance Mode
     
    6. Exit AD Administration

    Select option (5) Change Maintenance Mode and Disable Maintenance mode. Remember, you need to have SYSTEM password and APPS password in order to run adadmin utility.

    After the patching was completed, ensure there’s no error in the log file and the patch entry was inserted to ad_bugs table. You may startup the Oracle Applications after verifying and let the functional team and end user to test the applications.

    Previous
    Next
    » Create Symbolic Link In Unix
Leave a Comment