DOYENSYS Knowledge Portal




We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal




Wednesday, September 30, 2015

Using Staged Applications System to reduce patching downtime in R12



Prerequisites

1. Apply the latest AutoConfig template patch on the source system

Update the Oracle Applications file system with the latest AutoConfig template files by applying the TXK AutoConfig Template rollup patch to all application tier server nodes.

2. Apply the latest Rapid Clone patch on the source system

Update the Oracle Applications file system with the latest Rapid Clone patches posted in the Rapid Clone Documentation. Refer to My Oracle Support Knowledge Document 406982.1, Cloning Oracle Applications Release R12 with Rapid Clone, for details of the latest Rapid Clone patch for Release 12.

Create the Release 11i Staged System

Create a clone of your Production database and of each APPL_TOP of your Production Applications system. Production and Staged should have the same APPL_TOP names, as this will ensure the patching history for your Staged APPL_TOP will be correct in the Production system. Historical information is stored in the context of an APPL_TOP, and when patch history data is imported into Production it needs to have the same APPL_TOP names.

Upgrade the Staged System to Release 12.1.1

Upgrade the Staged Release 11i system to Release 12.1.1 by following Oracle E-Business Suite Upgrade Guide Release 11i to Release 12.1.1, and Oracle Applications Release Notes, Release 12.1.1
After upgrading the Staged system to Release 12.1.1, apply Patch 9794897:R12.AD.B to the Staged system.

1. Update the Production APPL_TOP

        1. Copy 12.1.1 APPL_TOP and application tier files from the Staged system to Production (This step can be done while the Release 11i Production system is running). Be sure to maintain the same directory structure of APPL_TOP and application tier on both the systems.
        2. Stop all services and enable Maintenance Mode on the Production system.
        3. On the new Release 12.1.1 Production APPL_TOP, run $COMMON_TOP/clone/bin/adclonectx.pl to generate a new context file for the Production instance, as outlined in My Oracle Support Knowledge Document 384248.1, Sharing The Application Tier File System in Oracle E-Business Suite Release 12, Appendix B, "Step 2: Create applications Context File and Instance Home". Follow the instructions on running the script.
        4. Regenerate the environment files by running AutoConfig, using the new context file on the new Production system Release 12.1.1 APPL_TOP.
        5. Re-source the environment to discard any remaining values set when the previous environment file was run.

2. Update the Production Database

         1. The database upgrade should be performed according to the instructions in Oracle E-Business Suite Upgrade Guide, Release 11i to Release 12.1.1.
         2. Once the database upgrade is complete, apply all the AD patches mentioned in the Upgrade Guide and release notes, in their entirety first, followed by database portion of all the patches that were applied on the Staged system. Use the AutoPatch option 'nocopyportion,nogenerateportion' on the Release 12.1.1 APPL_TOP of the Production system.
                   
 An example of using the adpatch command in this context is:
           $ adpatch options=nocopyportion,nogenerateportion driver=u_merged.drv

Start the services, disable Maintenance Mode using AD Administration, and check all is   running normally.
                   
 An example of the command to start the services is:
           $ $INST_TOP/admin/scripts/adstrtal.sh <APPSUSER>/<APPSPASSWORD>
                
         3. Synchronize the Patch Histories as mentioned below

Export Patch History

Use the adphmigr.pl utility, located in the bin directory under AD_TOP. You can enter adphmigr.pl -help to see all valid options for the utility.
Note: Patch history should be exported for each APPL_TOP separately, as you will need to import it for each APPL_TOP separately.
Ensure you specify nodatabaseportion=Y on the adphmigr.pl command line.

Export example
$ perl $AD_TOP/bin/adphmigr.pl userid=apps/apps \
startdate='2007/10/10 00:00:00' enddate='2007/14/10 00:00:00' \
appsystemname=stage appltopname=tafnw1 nodatabaseportion=Y

This command will generate two data files for each run of AutoPatch on the Staged APPL_TOP, one for Java updates (javaupdates<TIMESPAMP>.txt), and one for all other patch actions (adpsv<TIMESPAMP>.txt).
Check the adphmigr.log file to ensure that the data files represent the patch runs you wish to export, and that the start and end times specified did not include any unwanted AutoPatch runs.

Import Patch History

By now, you should have extracted a separate set of data files for each APPL_TOP in your Staged Applications system. For each APPL_TOP in your Production Applications system, copy the data files extracted for the corresponding Staged APPL_TOP to the $APPL_TOP/admin/<DB NAME> directory. AutoPatch will automatically upload these data files the next time it runs in this APPL_TOP. To load the data files immediately, start AutoPatch in interactive mode, answer the prompts until prompted for the name of the patch driver file, then exit AutoPatch by entering "abort" at the patch driver file prompt.

Reference - Using a Staged Applications System (APPL_TOP) to Reduce Patching Downtime in Oracle E-Business Suite Release 12 (Doc ID 734025.1)

1 comment:

Sridevi K said...


Regards
Sridevi Koduru (Senior Oracle Apps Trainer Oracleappstechnical.com)
LinkedIn profile - https://in.linkedin.com/in/sridevi-koduru-9b876a8b
Please Contact for One to One Online Training on Oracle Apps Technical, Financials, SCM, SQL, PL/SQL, D2K at training@oracleappstechnical.com | +91 - 9581017828.