Академический Документы
Профессиональный Документы
Культура Документы
Agenda
Oracle Release 12 Patching Tips Focus on E-Business Suite Patching New features for Release 12 Patching Will not discuss database patching (opatch) Performance and Availability for patching
Oracle 10gAS replaces previous version for application server with three OC4J instances New file system changes: INST_TOP Oracle 10gR2 database standard for 12.0 Oracle 11gR1 database standard for 12.1 New patching features
Completed previous failed patching or terminated sessions that have not completed. Performs automation for patch tasks which were a manual process before Release 12 Available in graphical interface (GUI) and command line (CLI) versions. Required for some patches per README.txt file instructions.
Patch Application Assistant (PAA)Incomplete patch operations: Step 2 Provides instructions to complete patches that failed to run to completion Useful tips and scripts provided
Patch Application Assistant (PAA) for Patch Configuration with Oracle EBS Release 12
Using Command Line (CLI) Patch Application Assistant (PAA) for EBS Release 12
Useful for quick generation of scripts before apply patch versus GUI version. Use admsi.pl cli help for options with PAA.
Specify options for PATCH_TOP directory Generates HELPME files with patch instructions
Use hotpatch option for Auto Patch to avoid downtime Syntax: adpatch options=hotpatch Be careful with hotpatch for adpatch No way to recover if patch fails other than restore/recovery Do not use for patches that have templates or require Auto Config!
Why use shared APPL_TOP? Simplifies patch maintenance since you can apply patch to one node for a multi-node configuration
Why use Staged APPL_TOP file system? Allows you to apply patch without incur downtime to applications tier to production system.
Distributed AD with Auto Patch Merge Patch Utility Multiple Workers for Auto Patch Compile invalid objects before patching
Example: AutoPatch session with a total of twelve workers (four workers on the local node and eight workers on a remote node): $ adpatch workers=12 localworkers=8
Node 2:
$ adctrl distributed=y Enter the worker range: 1-10
Node 3:
$ adctrl distributed=y Enter the worker range: 11-15
Merge Patch option (admrgpch) Reduces patch time in many cases Patch consolidation Fewer maintenance windows required Net result= more availability, less downtime
Maintenance Notification Restricted Mode with Apache Timing Reports for Patch Activity Patch Wizard for Automation of Patch Tasks
Manage Downtime Schedules Feature Useful for scheduling patch activity Provides communication to user community and management Easy to setup and configure
Enable Restricted Mode for Apache Useful for the Applications DBA when performing maintenance activity and need to access Oracle Applications Manager (OAM) Allows limited use of OAM interface Easy to setup Toggle on/Toggle Off as needed Uses txkrun script to configure
Best Practices Patching Release 12 Oracle Applications E-Business Suite- Maintenance How to configure Restricted Mode for Apache? Login as applmgr account to applications tier and source environment Shutdown application tier service with adstpall.sh script under $INST_TOP/admin/scripts or $ADMIN_SCRIPTS_HOME directory Run txkrun.pl script under $FND_TOP/bin directory with following options:
txkrun.pl script=ChangeApacheMode
Example:
Example Continued: Enable Restricted Mode Apache for R12 Oracle EBS
For Release 12 the default URL for Restricted access to OAM with ad_monitor:
http://<host>.<domain>:<port>/OA_HTML/weboamLocal/oamLogin
Configure ad_monitor account for Restricted Mode Access to OAM During Maintenance
Restricted Mode provides monitoring of patch activities but not all functions available from OAM
Specify Mode as Normal for Apache Enter name and location for Context file Restart application tier services (adstrtal.sh)
Timing Reports for Patch Activity Provides accurate method to measure requirements for maintenance windows Useful when apply patches between environments to estimate downtime for service level agreements (SLAs) Excellent way to troubleshoot a patch process Should be used as part of DBA patch strategy
Using Timing Reports for Patch Activity Available from Patch Wizard Utility in OAM Requires SYSADMIN level access Navigation Path: Site Map-> Maintenance->Timing Reports
Allows you to measure and track patch run times and issues during and after patch sessions.
Provides macro to micro level of detail for patch status and log files
Best Practices Patching Release 12 EBS Maintenance: Inside the Patch Wizard
Patch Wizard arrived in 11.5.10.2 (11iCU2) release for E-Business Suite Excellent tool to simplify and automate many tedious patch functions: Such as download recommended patches Also useful for patch impact analysis Helpful when you dont have a test environment for patching!
Best Practices Patching Release 12 EBS Maintenance: Inside the Patch Wizard
Best Practices Patching Release 12 EBS Maintenance: Using the Patch Wizard
Patch Wizard Patch Application Assistant (PAA) Timing Reports for Patching R12 EBS Schedule Maintenance Window
Q&A Discussion
Thank You!
Please provide feedback Email: ben@ben-oracle.com I will be available in the Oracle ACE lounge My blog has further tips on Oracle technology: http://oracle-magician.blogspot.com