2. Best Practices For Patching and Maintaining Oracle E-Business Suite Session # CON8478
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
William Burbage
Jason Brincat
Senior Principal Technical Support Engineers
Date: 2nd October 2014
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |

3. This is a Safe Harbor Front slide

4. William Burbage (Bill) E-Business, Applications Technology Group
Senior Principal Technical Support Engineer
Proactive Support Delivery
Orlando, FL
16 Years Oracle Support
5 Years Center of Expertise
3 Years Proactive Support
Workflow Expert, Patch Wizard Expert

5. Agenda
How to find EBS & EBS Technology Stack Patches on My Oracle Support
RPCs
EBS Patch Wizard
EBS Patch Advisor
Application Management Pack (AMP) an EBS Plug In
12.2 Online Patching
12.2 Patching Best Practices
12.2 Patching Advisor
12.2 Information Center
This session is about Best Practices for Patching and Maintaining Oracle Applications (EBS)
We'll cover some new ways to find patches using My Oracle Support.
Both EBS and Techstack patching,
We'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 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 is now available for use with Oracle Enterprise Manager 12c. 
Oracle E-Business Suite Plug-in 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.

6. NEW How to Find E-Business Suite & E-Business Suite Technology Stack Patches (Doc ID 1633974.2)
TABBED NAVIGATION
This is a new note, for 1 stop shopping of all the EBS patching information

7. EBS Patches Tab

8. 1633974.2 for How to find E-Business Suite & E-Business Suite technology stack patches.
Doc ID –RPC 1- superseded 24SEP2014
Doc ID –RPC2

9. Recommended Patch Collections for EBS 12.1.3
Released
RPC 2
Recommended Patch Collections for EBS
One Consolidated patch across product families
Recommended Patch Collection 2 (RPC2) includes:
Applications Technology (ATG)
Customer Relationship Management (CRM)
Financials (FIN)
Human Resources Management (HRMS)
Procurement (PRC)
Projects (PJ)
Supply Chain Management (SCM)
Value Chain Planning (VCP)
Doc ID – R RPC2- superseded RPC1 on 24SEP2014
Release has been out since Dec 2009… almost 5 years…
RPC1 was released Mar 28th, (closed as of Dec 4th, 2013)
RPC2 superseded RPC1 Sept 24th, (closed as of July 24th, 2014)
Use Patch Wizard for any recommended patches on R available after July 24th.
Oracle E-Business Suite Recommended Patch Collection 2 [RPC2]
Note

11. Patch Wizard
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
Patch Wizard analyzes and compares patches currently applied in your instance with the ones included in the Recommended Patch List

12. Patch Wizard - Patch Impact Analysis
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.

13. Patch Wizard – Responsibility & Menu Navigation Paths

15. Patching Community
The Patching Community changes the way to get information on EBS Patches.
Start a thread directly in order to receive expert advice around your patching needs.

16. Patching and Maintenance Advisors

17. Patching and Maintenance Advisors
Contains proven methodologies for patch application
Shares full details to successfully complete pre-patch, patch application, and post- patch requirements
Provides tracking lessons learned in testing your original patch plan
Checks to ensure satisfactory patch and code levels are in place
, 12.0, 12.1 DOC ID: 313.1
12.2 – DOC ID:

20. Jason Brincat E-Business, Applications Technology Group
Senior Principal Technical Support Engineer
Advanced Resolutions Support, Security Engineer
Adelaide, Australia
15 Oracle
Procurement, Cloud, ATG
2 Customer
Implementing EBS 10.7
Focus areas
Technology stack, Applications tier performance tuning, 12.2 patching, installation and security

21. 12.2 Online Patching Best Practices
The online patching cycle
Upgrade / Install
AD and TXK Code levels
Technology Patches
Patching Modes
Tips and Tricks
Information Resources
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 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

22. Oracle E-Business Suite 12.1 Patching
Enable Maintenance Mode 2
Users Log-off the System 3
Shutdown Services 4
Apply Patch
adpatch 5
Disable Maintenance Mode 6
Start Services 7
Users Log-in

23. The Online Patching Cycle
Abort
Prepare
Apply
Finalize
Cutover
Cleanup
Create patch edition in the database
Sync run to patch file system.
ADZDPATCH
Cleanup
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
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)
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 "adop" command line tool.
You can check the status of the patching cycle by running "adop -status".
Discuss the above with reference to the dual file system (run and patch) (fs1 and fs2)
Users
Online
Users
Offline
Users
Online
Users offline
Users online
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.

24. 12.2 Patching Best Practices
Upgrade / Install
Use the latest startCD and latest documentation – Current recommended startCD is startCD48 – patch
Start topology simple, patch up, then add complexity (tiers, DMZ, LBR, OAM etc)
Apply latest Cumulative update patches during upgrade. Merge AD patch with latest AD CUP. Merge upgrade driver (u drv) with latest EBS CUP. New installation customer should apply the consolidated seed table upgrade patch. See release notes ( ).
Read the release notes before during and after install/upgrade. Follow any required steps and apply patches
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
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 u 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.

25. 12.2 Patching Best Practices
Upgrade / Install cont...
Follow post upgrade steps in the upgrade guide carefully. These steps are run after laying down the file system and before Rapid Install configure is run. Do not forget to clean topology references to old instance if they exist - run fnd_conc_clone.setup_clean ! Only run it at as per the upgrade guide !
Use shared application tier configurations for multi-app-node configurations. All application servers share the same file system including inventory. Simplifies patching, administration.
Enable SSH for adop for remote invocation. Mandatory. One way SSH connectivity across DMZ.
Do not start services until reaching code level
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 code level is reached. Forms based applications will not work/launch if code level is AD and TXK patches. With upgrades, concurrent requests should not be processed until code levels

26. 12.2 Patching Best Practices
Uptake the latest AD and TXK Code Levels
Currently AD and TXK Delta 5: Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 Note 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 Readme Note
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
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 (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 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

27. 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
Use the EBS Technology Codelevel Checker (ETCC) (patch ) 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.
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
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 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 and instructions to run the EBS Technology Codelevel Checker (ETCC) (checkDBpatch.sh or checkDBpatch.cmd for Windows) are available in the patch's readme.
Upgrade Customers
If you are upgrading to Release 12.2 using an existing Oracle Database ORACLE_HOME, you must check that you have all the required 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 , Database Preparation Guidelines for an Oracle E-Business Suite Release 12.2 Upgrade as well as My Oracle Support Knowledge Document , Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes, and apply all technology patches for your database version ( or ).
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 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 , Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes and apply all technology patches for your database version ( or ).

28. 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 resource for database patch conflicts
How to Use the My Oracle Support Conflict Checker Tool [Video] (Doc ID )
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 )
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 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 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 This is a vide which demonstrates the use of the conflict checker utility which can further aid in conflict resolution.

29. 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
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 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

30. 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
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.

31. 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
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=<total number of workers> localworkers=<number of workers on
primary node>

32. 12.2 Patching Advisor –
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

33. 12.2 Information Center DOC ID: 1581299.1 One Stop Shop for 12.2
Multiple Tabs for more information
Home Tab:
New Features
Planning Guide
Online Patching FAQ
Training
Documentation
Announcements
Install Tab:
Concepts & Requirements
Globalization/Localization
Release Notes
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

34. Q&A

35. Appendix

36. EBS Patching Documents
E-Business Suite and EBS Technology Stack Patches – Doc
EBS Patch Wizard – Doc
EBS R Recommended Patch Collection 1 (RPC1) – Doc
Patching Advisor (11i ) – Doc 313.1
Patching Advisor (R12.2) – Doc
Oracle AMP for EBS Plug-In – Doc
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.

37. Oracle Application Management Pack for Oracle E-Business Suite, Release 12.1.0.2.0. – Doc 1532970.1
The Oracle Application Management Pack for Oracle E-Business Suite includes functionality that was available in previous releases of the Oracle Application Management Pack for Oracle E-Business Suite (AMP) and the Oracle Application Change Management Pack for Oracle E-Business Suite (ACMP).
"Previous releases" specifically refers to AMP , AMP/ACMP 4.0, AMP/ACMP 3.1 and AMP/ACMP 3.0
All of the functionality that was previously available for AMP is now classified as "System Management for Oracle E- Business Suite".
All of the functionality that was previously available for ACMP is now classified as "Change Management for Oracle E- Business Suite".
The term 'AMP' now refers to the single pack, Oracle Application Management Pack for Oracle E-Business Suite
Please note that 'Oracle Application Management Pack for Oracle E-Business Suite' is also known as
'Oracle E-Business Suite Plug-in' or "Enterprise Manager for Oracle E-Business Suite".
The documentation is under the name 'Oracle Application Management Pack for Oracle E-Business Suite'.
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 ( )
Release 3 ( )
Oracle E-Business Suite:
12.2: Releases and
12.1: Release 12.1 with R12.ATG_PF.B.delta.3
12.0: Release with R12.ATG_PF.A.delta.6
11i: Release 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 "EBS Plug-in" or "AMP") 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.

38. Spotlight on some key offerings
Patching and Upgrading
How to find EBS patches ( )
Advisors and Patch Wizard updated for 12.2
12.2 Info center ( )
Pre-Install patches ( )
EBS Support Analyzers
31 EBS Analyzers
Diagnose and Maintain
Read Only
Enable Functional Users
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.
SR Guided Resolutions
SR create decision tree
Targeted solutions
Expedite resolution
WIP: Simplify template selection and routing
Future: SR File Uploads and Analysis
Step 1 – Automated file handling and validation
Step 2 – Analyze data, find problem
Step 3 – Match to solutions

40. Stay Informed
Follow Oracle Premier Support through social media channels to hear the latest on Proactive Offerings!
Blog
Newsletters – now news consolidations from Blog articles
Twitter | Oracle_EBS | myoraclesupport
My Oracle Support Community
Facebook
Participate in Advisor Webcasts and hear from Oracle Premier Support subject-matter experts who will offer methods and solutions to help you avoid potential pitfalls
Expand your existing knowledge with E-Business Suite accreditation. ( ). A guided learning path of best practices, product-based use cases and recommendations from subject-matter experts.
We have a lot of ways to stay connected and learn about our proactive offerings.
Please use the Social Media channel of your choice!

41. This is a Safe Harbor Back slide