Adop and maintenance task presentation 151015
•Als PPT, PDF herunterladen•
0 gefällt mir•878 views
How to patching and maintain oracle e-business suite 12.2.5. For Techical Engineer and Developer Users.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (14)
Ähnlich wie Adop and maintenance task presentation 151015
Ähnlich wie Adop and maintenance task presentation 151015 (20)
Mehr von andreas kuncoro
Mehr von andreas kuncoro (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Adop and maintenance task presentation 151015
- 2. Best Practices For Patching and Maintaining Oracle E-Business Suite Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Andreas Sandhi Kuncoro Technical Consultant Support Engineers Date: 15th October 2015
- 3. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 3
- 4. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Agenda • Hands on EBS Maintenance Procedure • How to find EBS & EBS Technology Stack Patches on My Oracle Support 12.2.4 RPCs EBS Patch Wizard EBS Patch Advisor Application Management Pack (AMP) an EBS Plug Ins 5
- 5. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Hands on / Preventive Maintenance CheckUp • Standard Procedure on EBS Startup Database, Application and Shutdown Application and Database • Check Log Usage on EBS • Add Tablespace on EBS 6
- 6. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Standard Procedure StartUp / Shutdown Application Server # su – oraprod $ . /u01/PROD/<SID_Hostname).env – Set Apps Env. $ cd $ADMIN_SCRIPT_HOME $ ./adstrall apps/apps or $ ./adstpall apps/apps 7
- 7. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Standard Procedure StartUp / Shutdown Database Server # su – oraprod $ . /u01/../11.2.0/<SID_Hostname).env – Set DB Env. $ sqlplus / as sysdba SQL> startup or SQL> shutdown immediate SQL> exit $ lsnrctl start <SID> or $ lsnrctl stop <SID> 8
- 8. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Preventive Maintenance on Database Server • Clear log of Database (*.trc, *.trm) from log location : SQL> show parameter back; • Check alert log (alert_<SID>.log) • Check workflow_analyzer.sql • Check addmrpt.txt • Check awrrpt.html • Check Tablespace 9
- 9. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Preventive Maintenance on Application Server • Check Log Size Usage Forms dump files : $INST_TOP/logs/ora/10.1.2/forms Reports Cache : $INST_TOP/logs/ora/10.1.2/reports/cache Apache logs : $INST_TOP/logs/ora/10.1.3/Apache OPMN Logs : $INST_TOP/logs/ora/10.1.3/opmn Service Management : $INST_TOP/logs/appl/admin/log Concurrent Manager logs : $INST_TOP/logs/appl/conc/log Concurrent Manager out files : $INST_TOP/logs/appl/conc/out 10
- 10. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 12.2 Online Patching Best Practices • 12.1 patching • The online patching cycle • Upgrade / Install • AD and TXK Code levels • Technology Patches • Patching Modes • Tips and Tricks • Information Resources 28
- 11. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | The Online Patching Cycle 30 • adop – AD Online Patching, utility to apply patches to EBS • 12.2 patching is online. EBS is available while most of the patching operations are performed • Application is only offline during the Cutover phase • See technical planning guide, maintenance guide and concepts guide. CleanupFinalizeApply • Create patch edition in the database • Sync run to patch file system. • ADZDPATCH • Cleanup Prepare Users Online Users Online Users Offline • Apply one or more patches to the patch edition/fs • Adop tool is used • Ready the system for cutover. • Compile invalid objects • Run by cutover if not explicitly run Users offline Users online • Cutover to patch edition of the database & fs • Run finalize if not already run • Shutdown and start services • Cleanup old editions and objects to recover space Dual file system (run/patch) Abort
- 12. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | The Online Patching Cycle 31
- 13. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | $ adop -status -detail $ adop phase=cleanup cleanup_mode=full $ adop phase=apply patches=<patch_id> hotpatch=yes $ adop phase=fs_clone $sqlplus apps/<passwd> SQL> set markup html on spool adop_sessions_<cust_name>.html set timing on set linesize 120 set pagesize 300 show user select release_name from FND_PRODUCT_GROUPS; select * from FND_NODES; select * from FND_OAM_CONTEXT_FILES; select * from AD_ADOP_SESSIONS; select * from AD_ADOP_SESSION_PATCHES; select * from AD_APPL_TOPS; select codelevel FROM AD_TRACKABLE_ENTITIES where abbreviation in ('txk','ad'); set timing off set markup html off spool off ADOP Best Practice 32
- 14. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Identifying Missing appTier and dbTier Patches for EBS 12.2 • EBS Technology Codelevel Checker (ETCC) – checkDBpatch.sh (Database EBS Technology Codelevel Checker – DB-ETCC) – CheckMTpatch.sh (Middle Tier EBS Technology Codelevel Checker – MT-ETCC) – Always use the latest version of ETCC 33
- 15. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Always Apply Latest Technology Patch • 18274429 1-Off R12.AD.C.Delta.4: script to fix ldt invalidation issue during main divisional upgrade (Patch) • 20927952 Fix for Bug 20927952 (Patch) • 19371817 Fix for Bug 19371817 (Patch) • 21111894 Fix for Bug 21111894 (Patch) • 20486861 Fix for Bug 20486861 (Patch) • 20083253 Fix for Bug 20083253 (Patch) • 21360713 Fix for Bug 21360713 (Patch) • 20953338 ORACLE APPLICATIONS RELEASE 12.2: CPU PATCH FOR JUL 2015 (Patch) • 20311216 CHECKEDTOUNCHECKEDEXCEPTION: RESULT SET ALREADY CLOSED WHEN BOOKING SO (Patch) 34
- 16. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 12.2 Patching Best Practices Uptake the latest AD and TXK Code Levels •Currently AD and TXK Delta 6: Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 Note 1617461.1. Check for additional critical patches! Check for known issues and understand new features •Follow the correct path. Path A or B for release update packs (AD/TXK/EBS) •Do not start patching/cloning/integrations etc.. until your system is on the latest AD and TXK code levels. •Apply latest EBS Release Update Pack: Oracle E-Business Suite Release 12.2.4 Readme Note 1617458.1 37
- 17. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 12.2 Patching Best Practices Applying Applications Technology Patches and Database Patches •These patches are required to be applied before moving to latest AD and TXK code levels. Try and apply any newly recommended patches to maintain system stability. •Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes Note 1594274.1 •Use the EBS Technology Codelevel Checker (ETCC) (patch 17537119) to check database patch levels. Warns of essential missing database bug fixes. Must be done for upgrade and new installation customers before upgrade and/or before AD and TXK patching. Patches to be applied will depend on startCD used for fresh install customers. Shows bug fixes to be applied, not patches. 38
- 18. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 12.2 Patching Best Practices Applying Applications Technology Patches and Database Patches cont.. •Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E- Business Suite Note 1147107.1 resource for database patch conflicts •How to Use the My Oracle Support Conflict Checker Tool [Video] (Doc ID 1091294.1) •Use the txk inventory report to generate a list of applied middle tier patches. $ADPERLPRG $FND_TOP/patch/115/bin/TXKScript.pl -script=$FND_TOP/patch/115/bin/txkInventory.pl -txktop=$APPLTMP -outfile=$APPLTMP/Report_Inventory.html •Oracle E-Business Suite 12.2 Patching Technology Components Guide (Doc ID 1355068.1) 39
- 19. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 12.2 Patching Best Practices Understand The Available Patching Modes • Online mode: Default mode. Involves a patching cycle which is initiated with a prepare phase. Changes made available only after cutover. Patch is abortable • Hotpatch mode: Patch is applied directly to the run file system when services are running. No patch cycle is required. Patch is not abortable. Patches can only be applied in hotpatch mode when instructed in the readme • Downtime mode: Introduced in AD.C.Delta.5. Patch is applied directly to the run file system when services are down. Patch is not abortable. Only supported for production use where explicitly documented, or when directed by Oracle Support or Development. Before system scale up, single node dev or test environment where high availability and prod support is not required 40
- 20. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 12.2 Patching Best Practices Tips and Tricks • adop is always executed from the run file system • adop logs can be found in fs_ne file system $ADOP_LOG_HOME • Apply multiple patches in one cycle • Can run multiple phases automatically adop phase=prepare,apply patches=XXX, finalize • Keep patches in $PATCH_TOP directory until the next prepare phase is complete • In a non-shared multi- node system, patches must be downloaded to all nodes 41
- 21. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 12.2 Patching Best Practices Tips and Tricks • To improve apply phase completion times set workers to maximum number that your system will support; Utilize distributed AD remote worker invocation when running multiple application tiers to utilize resources on other application tiers. Requires shared FS. • Reduce cutover by: running explicit finalize, shutting down managers before running cutover • Run adscanlog utility to quickly collect adop failure information from log files: adopscanlog; adopscanlog -session_id=<number>; adopscanlog –help • Run the adop diagnostic script to collect logs, configuration and other information to diagnose issues with adop and other AD/TXK utilities. Upload results to support. Note 1901242.1 42
- 22. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Q&A
- 23. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Appendix
- 24. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | EBS Patching Documents • E-Business Suite and EBS Technology Stack Patches – Doc 1633974.2 • EBS Patch Wizard – Doc 976188.1 • EBS R12.1.3+ Recommended Patch Collection 1 (RPC1) – Doc 1638535.1 • Patching Advisor (11i - 12.1) – Doc 313.1 • Patching Advisor (R12.2) – Doc 1590494.1 • Oracle AMP for EBS Plug-In – Doc 1532970.1 47
- 25. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Safe Harbor Statement The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 52
- 26. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 53
Hinweis der Redaktion
- We have 45 mins to present these slides, We’ll take 15 mins at the end to have a Q&A and we’ll make ourselves available outside after the session if there are any specific questions that we don’t get to Q & A will be handled at the end if time permits and Jason & I will be available outside the room
- This is a Safe Harbor Front slide
- This session is about Best Practices for Patching and Maintaining Oracle Applications (EBS) We&apos;ll cover some new ways to find patches using My Oracle Support. Both EBS and Techstack patching, We&apos;ll look at the EBS Patch Wizard tool, and the Patching & Maintenance Advisor, and if time permits the Application Management Pack, an EBS Plug-In 12.1.0.2.0 is now available for use with Oracle Enterprise Manager 12c and Jason will discuss patching in Release 12.2. Oracle E-Business Suite Plug-in 12.1.0.2.0 is now available for use with Oracle Enterprise Manager 12c. Oracle E-Business Suite Plug-in 12.1.0.2 is part of Oracle Enterprise Manager 12 Application Management Suite for Oracle E-Business Suite. This latest plug-in extends EM 12c Cloud Control with E-Business Suite specific system management capabilities and features enhanced change management support. The Oracle Enterprise Manager 12c Application Management Suite for Oracle E-Business Suite includes: Functionality that was available in the previously-standalone Application Management Pack for Oracle E-Business Suite and Application Change Management Pack for Oracle E-Business Suite Oracle Real User Experience Insight Oracle Configuration & Compliance capabilities Licensing information A license for Oracle Enterprise Manager 12c Cloud Control is required to use this product. There is an additional licensing cost for the Application Management Suite for Oracle E-Business Suite. A license for the Application Management Suite includes licenses for the E-Business Suite Plug-in, Oracle Real User Experience Insight, and Oracle Configuration & Compliance products. Learn to minimize manual labor using the PatchWizard. It assists in tracking & comparing customized files through alert flagging; helps you stay current with EBS Dev Recommended Patches, assists in identifying test paths affected by patches via menu navigation trees. We will explore the MOS Patching Community where you can see customer feedback on patches.
- This is a new note, for 1 stop shopping of all the EBS patching information
- 1633974.2 for How to find E-Business Suite & E-Business Suite technology stack patches. Doc ID 1638535.1 –RPC 1- superseded 24SEP2014 Doc ID 19020628.1 –RPC2
- Doc ID 19020628.1 – R12.1.3 RPC2- superseded RPC1 on 24SEP2014 Release 12.1.3 has been out since Dec 2009… almost 5 years… RPC1 was released Mar 28th, 2014 (closed as of Dec 4th, 2013) RPC2 superseded RPC1 Sept 24th, 2014 (closed as of July 24th, 2014) Use Patch Wizard for any recommended patches on R12.1.3 available after July 24th.
- Patch Wizard analyzes and compares patches currently applied in your instance with the ones included in the Recommended Patch List
- Patch Wizard performs an impact analysis, and allows for easy download of patches you decide to apply It shows what percentage of a patch is really going to be applied, It includes details which show how many responsibilities and users are affected by a patch… this is very useful when planning your testing of the patch.
- 11.5.10, 12.0, 12.1 DOC ID: 313.1 12.2 – DOC ID: 1590494.1
- During this portion of the presentation we will be looking at 2.2 patching best practices. This is an exciting topic as 12.2 delivers a wonderful groundbreaking and innovative feature called “online patching” The aim of this portion of the presentation is to provide you with the best practices for patching 12.2. Obviously with limited time this will be a non-exhuastive list. Essentially we will be looking at what can give you the greatest benefit and how to avoid the most common mistakes. We will firstly be looking at the online patching cycle. Next, common patching mistakes during upgrades and installs. The important of AD and TXL code levels. How to effectively apply technology patches. The various patching modes and finally we will go through a list of tips and tricks. Give you the tools to perform a smooth upgrade / install and effectively maintain your 12.2 system
- No discussion on 12.2 online patching would be complete without an explanation of the online patching cycle All patches to an editioned system are applied within the context of an Online Patching Cycle. The patching cycle has several phases which proceed in order. Prepare - creates the patch edition, synchronizes run fs to patch fs effectively preparing the patch fs for patching Apply – applies patches to the patch edition / file system Finalize - perform any actions required to prepare for cutover. Cutover - Promote Patch Edition to be the new Run Edition. Cleanup - remove obsolete code and data from old editions. Online Patching Cycle phases are executed using the new &quot;adop&quot; command line tool. You can check the status of the patching cycle by running &quot;adop -status&quot;. Discuss the above with reference to the dual file system (run and patch) (fs1 and fs2)
- No discussion on 12.2 online patching would be complete without an explanation of the online patching cycle All patches to an editioned system are applied within the context of an Online Patching Cycle. The patching cycle has several phases which proceed in order. Prepare - creates the patch edition, synchronizes run fs to patch fs effectively preparing the patch fs for patching Apply – applies patches to the patch edition / file system Finalize - perform any actions required to prepare for cutover. Cutover - Promote Patch Edition to be the new Run Edition. Cleanup - remove obsolete code and data from old editions. Online Patching Cycle phases are executed using the new &quot;adop&quot; command line tool. You can check the status of the patching cycle by running &quot;adop -status&quot;. Discuss the above with reference to the dual file system (run and patch) (fs1 and fs2)
- Use the latest startCD to obtain the latest fixes, enhancements and applications tech patches Best practice is to add complexity after the latest code levels have been reached. Ideally install/upgrade with 1 application tier. Add applications tiers, preferably via shared FS configuration after: Latest AD and TXK patches Latest EBS Family Pack e.g. 12.2.4 Add further complexity such as load balancing, SSL, OAM and other integrations after the latest code levels are reached StartCD49 will be disabling the ability to add multiple application tiers during Rapid Install. Only the Primary node will be able to be defined during Rapid Install A very common mistake we see is during upgrades customers sometimes miss merging the required AD patch with the AD CUP (at present CUP 5). This merge is applied prior to the main upgrade driver. Do not forget to run adgrants It is also just as important that the EBS CUP (CUP5) be installed in preinstall mode and then merged with the main upgrade driver u10124646.drv. The merged driver is then run the perform the main upgrade. New installation customers need to apply the latest consolidated seed table upgrade patch. All of these steps are mentioned in the release notes. Perfect segway to the next point which is the importance of following the release notes. It is important to view the release notes before, during and after upgrade/installation. The release notes are absolutely essential to a successful installation. They include critical patches, steps and known issues.
- During an upgrade it is essential that one follows the post upgrade steps. The steps I am referring to here are those steps after the upgrade driver and before the rapid install configure process is run. Some examples of the steps performed here include: Autoconfig runs on both applications and database tiers and cleaning of fnd_nodes. Do not forget to clean the system topology such as fnd_nodes as this will have impact later during online patching. There are complexities around cleaning fnd_nodes post upgrade so it is vital that it is performed at precisely the right moment. Best practice when configuring multiple application tiers after installation is to adopt the shared file system. This architecture simplifies patching, maintenance and administration and allows for simple addition and removal of application tiers. Enable SSH to facilitate adop remote invocation. In a multi-node environment, adop commands are invoked by a user on the primary node. Internally, adop uses Secure Shell (ssh) to automatically execute required patching actions on all secondary nodes. You must set up passwordless ssh connectivity from the primary node to all secondary nodes. If running a DMZ the recommendation is to enable one way SSH connectivity from the primary node to the DMZ. See the maintenance guide for more information As per the release notes and upgrade guides it is essential that services are not started until the 12.2.2+ code level is reached. Forms based applications will not work/launch if code level is 12.2.0 + AD and TXK patches. With upgrades, concurrent requests should not be processed until 12.2.2+ code levels
- Ensure you are running the latest AD and TXK patches to ensure a your system runs smoothly. This will ensure components such as online patching, autoconfig, rapidclone, general system maintenance etc run smoothly. Make sure that you are on the same AD and TXK Delta RUP codelevel. You must therefore apply both R12.AD.C.Delta.5 and R12.TXK.C.Delta 5, not just one of them. Check for known issues before starting installation/upgrade in Oracle E-Business Suite Technology Stack and Applications DBA Release Notes for R12.TXK.C.Delta.5 and R12.AD.C.Delta.5 Note 1644660.1 Make sure to follow the correct path when installing AD and TXK release update packs REMEMBER – RELEASE UPDATE PACKS ARE A MAINTENANCE STRATEGY. DON’T JUST UPDATE AND FORGET. KEEP UP TO DATE! If you are... Upgrading to Oracle E-Business Suite Release 12.2 from Release 11i, 12.0, or 12.1 Path A Installing a new Oracle E-Business Suite system Path A Already using Oracle E-Business Suite Release 12.2 (below AD/TXK R12.AD.C.Delta.5 and R12.TXK.Delta.5 codelevel) Path B Path A is generally hotpatched while path B involves applying patches in a standard patching cycle. Do not start patching/cloning/integrations etc.. until your system is on the latest AD and TXK code levels. Self explanatory. You want to ensure your on the latest code of the utilities used in configuring your system post install. Try and keep up to date with the latest EBS release update packs. The latest available right now is 12.2.4. This is a streamlined method to quickly obtaining the latest code for EBS products. Do not forget to apply the associated help patch. EBS release update packs and their associated help patches are cumulative Ensure all middle tier and database patches are applied – segway to the next slide
- Make sure Middle tier patches for the various oracle homes as well as the database are applied before moving to the latest AD and TXK code levels or before applying the latest EBS release update pack. Try and keep up to date with these recommended patches. The patches are listed in note 1594274.1 EBS Technology Codelevel Checker (ETCC) The Codelevel checker utility analyzes an Oracle Database Oracle Home and warns of missing database bug fixes required for Oracle E-Business Suite Release 12.2. Oracle strongly recommends the use of the codelevel checker utility to ensure that required database bug fixes were installed. The EBS Technology Codelevel Checker (ETCC) is downloaded via Patch 17537119 and instructions to run the EBS Technology Codelevel Checker (ETCC) (checkDBpatch.sh or checkDBpatch.cmd for Windows) are available in the patch&apos;s readme. Upgrade Customers If you are upgrading to Release 12.2 using an existing Oracle Database 11.2.0.3 ORACLE_HOME, you must check that you have all the required 11.2.0.3 one-off patches by running the codelevel checker utility (checkDBpatch.sh or checkDBpatch.cmd for Windows) before you run Rapid Install to create the upgrade file system. If you are upgrading to Release 12.2 from a pre-12.2 Installation, review My Oracle Support Knowledge Document 1349240.1, Database Preparation Guidelines for an Oracle E-Business Suite Release 12.2 Upgrade as well as My Oracle Support Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes, and apply all technology patches for your database version (11.2.0.3 or 11.2.0.4). New Installation Customers New Installation customers should also run the codelevel checker utility (checkDBpatch.sh or checkDBpatch.cmd for Windows) to identify and apply required patches for Database 11.2.0.3. After the release of the startCD, new required patches may have been discovered. Therefore, it is important to perform this check. In addition, a Release 12.2 New Installation Customer must review My Oracle Support Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes and apply all technology patches for your database version (11.2.0.3 or 11.2.0.4).
- Run the txk inventory report to generate a list of patches which are applied. Use this list along with Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes Note 1594274.1 to determine what patches need to be applied to the application tier technology homes. For assistance on how to check the inventory, install patches and de-install patches to these oracle homes please refer to the Patching technology components guide note When encountering conflicts applying recommended database patches from the ETCC utility please consult note Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite Note 1147107.1 . This provides a list of overlay patches for various PSU’s which will help avoid patch conflicts If after following the above not your still have conflicts then we recommend following Note 1091294.1. This is a vide which demonstrates the use of the conflict checker utility which can further aid in conflict resolution.
- Online mode: Default mode. Involves a patching cycle which is initiated with a prepare phase. Changes made available only after cutover. Patch is abortable Hotpatch mode: Patch is applied directly to the run file system when services are running. No patch cycle is required. Patch is not abortable. Patches can only be applied in hotpatch mode when instructed in the readme Downtime mode: Introduced in AD.C.Delta .5. Patch is applied directly to the run file system when services are down. Patch is not abortable. Only supported for production use where explicitly documented, or when directed by Oracle Support or Development Downtime mode is appropriate for all patching (including post-upgrade patching) that is done as part of the 12.2 upgrade process, meaning before the application services are started and the system is open for user login. The purpose of downtime mode is to complete the 12.2 upgrade process as quickly as possible (since the entire upgrade process is a downtime from the business perspective). Once users are online, all subsequent patching on a production system should use online mode unless alternative instructions are documented in the patch readme. Downtime mode is only appropriate for - Patches applied on top of Release 12.2 that are part of the 12.2 upgrade process (before system scale up, and before users are allowed on the system) - Single-node development or test environments where high availability and production support is not required
- I often get the question. Which environment should I source before running ADOP. Always source the run environment file. ADOP is smart enough to correct the environment if you accidently source the patch environment file. For debugging purposes and for checking patch activity one can observe ADOP logs which are always stored in the non-editioned file system in $ADOP_LOG_HOME To save time you can apply multiple patches in the same patch cycle either merged or non-merged. Adop phase=apply patches=xxxx,xxxx,xxxx merge=yes. Default is merge=no You can also save time by running multiple phases automatically. This saves time as you do not need to return to the terminal to initiate the next phase. Also note that the cleanup and finalize phases are optional. Don’t run cutover this way. Run it separately. During the prepare phase patches applied in the previous cycle are synchronized. For this reason it is critical that patches applied remain in $PATCH_TOP for the duration of the next patch cycle after application. During cutover, managers are shutdown so that the file system switch can occur. Because there is a small period of downtime during cutover and considering the fact that cutover will wait for managers to shutdown, one can reduce downtime by ensuring managers are shut down before cutover is run, or long running requests are completed. Also consider running an explicit finalize to reduce the overall time taken for cutover.
- Distributed AD is a special parallel processing feature that can be employed to decrease the time needed for patch application (and other tasks) by allocating the associated worker processes to multiple application tier nodes. See maintenance guide for instructions workers=&lt;total number of workers&gt; localworkers=&lt;number of workers on primary node&gt;
- The Patching & Maintenance Advisor is an E-Business Suite patching advisor that provides easy-to-follow steps with detailed information to guide you through your patching process for R12.2.x. Provides a high level overview of the new Oracle E-Business Suite R12.2.x Online Patching feature Look at advanced patching techniques, discover options for finding tools and information on the latest E-Business Patches, and look at backup/recovery options Includes information on the Online Patching Cycle, Patching Features, Patching Tooling and Patching Resources Points you in the right direction to begin reviewing the five steps (Online Patching Overview, Evaluate, Plan, Test and Implement) needed to perform your system patching or maintenance Provides everything you need to move forward with your R12.2 patching strategy
- Finally to end of the presentation we have the 12.2 information center Central location for everything 12.2 Multiple Tabs for more information Home Tab: New Features Planning Guide Online Patching FAQ Training Documentation Tab Announcements Tab Install Tab: Concepts & Requirements Globalization/Localization Release Notes
- Everyone will get a copy of this and every presentation, so here is a quick list of useful Notes for patching in Oracle E-Business Suite Learn to minimize manual labor using the PatchWizard. It assists in tracking & comparing customized files through alert flagging; helps you stay current with EBS Dev Recommended Patches, assists in identifying test paths affected by patches via menu navigation trees. We will explore the MOS Patching Community where you can see customer feedback on patches.
- Please note that &apos;Oracle Application Management Pack for Oracle E-Business Suite&apos; is also known as &apos;Oracle E-Business Suite Plug-in&apos; or &quot;Enterprise Manager for Oracle E-Business Suite&quot;. The documentation is under the name &apos;Oracle Application Management Pack for Oracle E-Business Suite&apos;. The following Oracle Enterprise Manager Cloud Control releases, Oracle E-Business Suite releases, and platforms are supported: Oracle Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4.0) Release 3 (12.1.0.3.0) Oracle E-Business Suite: 12.2: Releases 12.2.2 and 12.2.3 12.1: Release 12.1 with R12.ATG_PF.B.delta.3 12.0: Release 12.0.4 with R12.ATG_PF.A.delta.6 11i: Release 11.5.10 CU2 with ATG_PF.H RUP6 or higher Certifications: You can search the certification under Oracle Enterprise Manager. Select Enterprise Manager Base Platform - OMS (Cloud Control, Grid Control, Plug-in, OEM, emagent, emoms, core, framework, ACC, CCC, CMDB Console) from the list of values and look for Oracle E-Business Suite (Managed Target) under Enterprise Applications. Supported Platforms: Oracle Application Management Pack for Oracle E-Business Suite (or &quot;EBS Plug-in&quot; or &quot;AMP&quot;) is generic and can be installed on many platforms with the exception of Microsoft Windows. AMP is available on Linux, IBM AIX, Oracle Solaris, and HP-UX Itanium. For a complete list of supported platforms and operating systems refer to the certification pages of Oracle E-Business Suite. Also, for a complete list of Enterprise Manager supported platforms and operating systems refer to the certification pages of Oracle Enterprise Manager.
- Highlighting 4 key offerings from the Proactive offerings. The 12.2 Upgrade Information Center Analyzers Premier tool for Diagnoising and maintaining the health of your functional area This is a Read only tool that will not modify or impact your data. Proactively run these diagnostics to see if you have any problems or trouble areas They provide easy to read, graphical HTML style reports Each problem is tied to the solution to resolve or address the issue Run from concurrent process, or stand-alone. They can add tremendous troubleshooting help to your functional people. They can resolve many issues without the need to involve the help desk Guided Resolutions These are new decision tree type tools that assist users locate identified solutions during the SR creation process. They replace the old manual templates. AS you create the SR, if a direct solution is available, it will be presented to you. If not, it will create the SR and provide the captured information to the Oracle Support Engineer The result is a finely tuned SR that can enable a more rapid troubleshooting process. We encourage you to use them. The goal is to provide you with an immediate answer to your issue if there is a known solution. Future offering: File uploads and Analysis during the SR creation process We will be releasing these in stages. Step 1: Automate the file upload and validation process Step 2: Analyze the files that are uploaded and search for problem signatures. Step 3: Match those signatures to our knowledge of known solutions. If a match, can quickly provide the solution. If not, have a very strong start in the troubleshooting process.
- We have a lot of ways to stay connected and learn about our proactive offerings. Please use the Social Media channel of your choice!
- This is a Safe Harbor Back slide