Forgot your password?    
+ Reply to Thread
Results 1 to 1 of 1

Thread: Speed Patch Application / Reduce Downtime

  1. #1
    Expert Oracle Administrator
    Join Date
    Oct 2011
    Location
    New Delhi, India
    Posts
    427

    Speed Patch Application / Reduce Downtime

    Following suggestions can substantially reduce your system downtime during the application of patches:

    1.Consolidate Patches
    Using AD Merge Patch to merge multiple patches into a single patch eliminates the time it takes to start a new AutoPatch session. It also eliminates generic processes that are common to all patch applications.

    2.Apply Patches in Non-interactive Mode
    You can automate much of the patching process by applying patches in non-interactive mode. This process allows you to store the responses to the patching prompts in a defaults file, and then specify the name of this file when you run AutoPatch.

    3.Defer Database Tasks
    Use AutoPatch options=nocompiledb,nomaintainmrc to defer system-wide tasks such as “Compile APPS schema” and “Maintain MRC” until all patches have been applied. AutoPatch automatically compiles the APPS schema and maintains the MRC schema during the application of standard patches. Try deferring the compilation of database objects so users can log back in sooner. “Compile APPS schema” in AD Administration after all patches are applied orimmediately after you return your system to the user community.

    4.Defer Upload of Patch Information
    AutoPatch uploads patch history information to the database automatically each time it successfully applies a patch. The time required for the upload may be substantial depending on the size of the patch. You can defer this task during the AutoPatch session and upload the patch history information later, after you have made the system available to users. Use options=phtofile during the downtime patching session to defer the information upload. Then, after your system is up and users have returned, run AutoPatch again with the argument uploadph=y to upload the patch history information from the patch history files to your database. AutoPatch performs the upload and then exits.

    5.Consider using more number of workers. I recommended 2*the number of CPU threads on the server.
    Using certain AutoPatch command line options and managing the number of workers can minimize patch application time.
    The norevcache option can save 5 to 10 minutes. Use this option when zero or only a few PL/SQL packages and views become uncompiled.
    The nolink option can save several minutes to hours. Use it when you apply several patches or when you plan to relink or regenerate the affected Applications (using AD Administration) after you apply a patch. Note: Be sure to always link AD and FND.
    The nogenform and nogenrep options can save several minutes to hours. Use them in the same way that you use nolink.
    AutoPatch can use parallel workers for all database tasks and for specific file system tasks such as forms generation.
    Choose the number of workers appropriate for the machine, load and type of tasks.

    6. Consider using a staged Applications system.
    See Using a Staged Applications System to Reduce Patching Downtime (OracleMetaLink Note 242480.1) for details.

    7.Use a Shared Application Tier File System
    Creating a multi-node system with a shared application tier file system saves patching time because you apply patches only once, on the primary node. See Sharing the Application Tier File System in Oracle Applications 11i (OracleMetaLink Note 233428.1) for details on creating a shared application tier file system.

    8.Use Distributed AD
    Distributed AD is a parallel processing feature that can reduce downtime by efficiently utilizing all the available resources on a shared application file system. AD Administration and AutoPatch run on the primary node and direct workers running on that node and other nodes in the system. The AD Controller utility controls and monitors the actions of the workers that you specify. Refer to : Distributed-AD-to-apply-a-patch

    9.Reduce Resource Related Issues
    Modify rollback segment sizing and temporary segment space to optimize resources during patch application.
    Match batch commit size with your rollback segment sizing.A larger batch commit size processes data more quickly, but requires larger rollback segments.
    Use as much temporary segment space as practical.

    Temporary tablespace (usually TEMP) should be created as a locally managed tablespace using the temporary file option with a uniform allocation size. Some scripts can run up to an order of magnitude faster by having sufficient temporary segment space (for example, 20 GB) to allow hash-join operations to be performed within the data server.

    10.Manage Patching During an Upgrade
    You need to apply the database upgrade driver and specific functional patches during an upgrade to Release 11i or 12. Here are some tips to reduce downtime:

    11. Relink and regenerate all executables, forms, reports, libraries and Java archives on the test system, and then copy this file system to your production system.
    Run the copy, database and generate actions in a test environment. Then, copy this file system to your production system, where you need to run only the database actions to complete the upgrade.
    Use a copy of the test system’s APPL_TOP with all file system patches pre-applied. This way, only the consolidated database driver created by AD Merge Patch needs to be run during the Production upgrade. In addition, generation of files such as forms, reports and message files is not required as this has been performed already when the original patch was applied.

    12.Merge NLS (Translation) Patches and Apply Them During Uptime
    If you have multiple patches for multiple languages, merge all US patches into a single patch. Then, merge the NLS translation patches for each active language in your system into a single patch for each language. Apply the US patches first during downtime. Then, you can apply the merged NLS translation patches during uptime.

+ Reply to Thread

Similar Threads

  1. How to Speed Instance Recovery for RAC
    By Hemant in forum RAC Performance,LoadBalancing,TAF,FAN,Troubleshooting
    Replies: 0
    Last Post: 12-09-2011, 09:28 AM
  2. Patch Application History
    By Amit in forum SCRIPTS : Users,Profiles,Applications,Responsibilities,Forms,JDBC,Patch,Versions,Products
    Replies: 0
    Last Post: 11-04-2011, 09:39 AM
  3. Count Current Forms Application Users Connected to the Application
    By Amit in forum SCRIPTS : Users,Profiles,Applications,Responsibilities,Forms,JDBC,Patch,Versions,Products
    Replies: 0
    Last Post: 11-01-2011, 03:25 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

DBA Lounge (P) Ltd. deals in Oracle Technologies on Consulting, Resourcing, Corporate Training


Online and corporate training available on Oracle Database 11g, Oracle 11g Real Application Cluster (RAC), Oracle Applications 11i/R12, Oracle Fusion Middleware 11g, Oracle Identity Management-OIM, Oracle Internet Directory 11g-OID, Oracle Business Intelligence Enterprise Edition-OBIEE, Oracle Golden Gate, Oracle Access Management-OAM, Oracle Internet Directory-ODS, Oracle Identity Analytics Architecture-OIA Statistics