EBS Upgrade Reducing Downtime Doc Id 1578187 1 V15

1 Copyright © 2012, 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.
E-Business Suite Upgrade
Reducing Downtime
Upgrading to 12.1 or 12.2
10OCT2017 – Version 15
Doc ID: 1578187.1
Table of Contents
SECTION 1 SLIDES
 About this Document Slides: 05-16
 Holistic Considerations & E-Business Upgrade Resources Slides: 17-32
 Customization Considerations Slides: 33-41
 Data Set & Cleaning Data Slides: 42-56
 Pre Upgrade & Configuration Setting Considerations Slides: 57-74
 Method of Upgrade Slides: 75-85
 Re-Review for Every run Slides: 86-91
 Testing & Troubleshooting & Performance Slides: 93-110
 Support Call outs/Post Go Live Slides: 112-122
 Platform Migrations DB Slides: 123-138
 Application Tier Migration Slides: 139-139
 Appendix – FIN Upgrade by Request example Slides: 141-148

About this Document
 Intended Use
 This Document is meant to outline some key E-Business Upgrade Considerations.
 Considerations are in Oracle E-Business Product documentation, but we are highlighting items
that Support & Customers find useful in reducing upgrade “cut over downtime”.
 This is not an exhausted list but a list that has highlighted some of the key items to review
 See Doc ID: 1581549.1 for more key items
 See Doc ID: 1581299.1 for key 12.2 items
Open World 2016 Development Presentations

 CON6714_Parvate-TechnicalUpgradeBestPracticesforOracleE-BusinessSuite_12-2
 CON6711_Barakat-EBS_Performance_Best_Practices_OOW15
Back to Table of Contents

About this Document
 Intended Audience
 System administrators
 Applications DBA’s
 Architects/Developers
 Project managers
 The items in the document are considerations. The

technical and project upgrade team should review
options and discuss if any recommendations could
assist in reducing downtime.
About this Document
 How to use this Document
 Review the contents for considerations prior to upgrade
 Use the table of contents to explore considerations
 Project/Technical team should discuss as a group the options
 When to use this document

 Prior to the upgrade review materials, keep ideas available
 After you complete first technical upgrade/run on a test/dev
environment-re-review options
 Explore options for your upgrade that could improve your cut-
over downtime window.
About this Document
 What this document is “NOT”
 This document is not the upgrade/upgrade tasks
 It does not substitute Oracle E-Business Upgrade documentation
 The following are not requirements, these are recommendations
for each Customers consideration and review
 This is not meant as a consultative platform
 These are not all the options that could be considered, but a
collection from Support working with Customers

About this Document
 How can Support improve the document
 Provide feedback via the My Oracle Support Document option

About this Document
 Use Cases
 Next 6 slides have some use cases on how the document
assisted customers in reducing downtime
 This document was used by Support with Customers and
developed over time

Use Case 1 12.1 Upgrade - Customer ABC
 CUSTOMER DATA POINTS:
 Upgrading R11.5.10.2 to R12.1.3 + Latest 12.1.3 RPC
 DB Version is 11.1.0.7 and planning to upgrade DB 12.1.0.2
 5 Languages
 DOWNTIME REDUCTIONS:
 REDUCE DOWNTIME: The customer uses this document to find out that they can
do the DB upgrade in a different downtime window.
 REDUCE DOWNTIME: The customer realized that their company can get the
American English going on cut over, and bring up the other languages after
 REDUCE DOWNTIME: Parallel processing ideas and continuously run the RDBMS
script “$ORACLE_HOME/rdbms/admin/utlprp.sql 1” from the database techstack
during the upgrade run will save them time on recompiling invalids.

Use Case 2 12.2 Upgrade - Customer ZYZ
 Upgrading R11.5.10.2 to R12.2.7
 DB Version is 11.1.0.7 and planning to upgrade DB 12.1.0.2
 5 Languages
 REDUCE DOWNTIME: The customer uses this document to find out that they can
do the DB upgrade in a different downtime window.
 REDUCE DOWNTIME: The customer realized that their company can get the
American English going on cut over, and bring up the other languages after
 REDUCE DOWNTIME: Parallel processing ideas and continuously run the RDBMS
script “$ORACLE_HOME/rdbms/admin/utlprp.sql 1” from the database techstack
during the upgrade run will save them time on recompiling invalids.

Use Case 3 12.1 Upgrade - Customer 123
 Upgrading from R11.5.10.2 to R12.1.3 + Latest 12.1.3 RPC
 DB Upgrade completed
 Over 10 Years of data they are upgrading
 Have not evaluated, Staged appl_top; shared appl_top or Distributive AD
 REDUCE DOWNTIME: The customer will evaluate the Upgrade Request Data Set
option and bring over 2 years of data and bring over the other 8 at another time
 REDUCE DOWNTIME: After review of Shared appl_top; distributive AD and Staged
appl_top the customer will realize considerable savings

Use Case 4 12.2 Upgrade - Customer 976
 Upgrading from R11.5.10.2 to R12.2.7
 DB Upgrade completed
 Over 10 Years of data they are upgrading
 REDUCE DOWNTIME: The customer will evaluate the Request Data Set option and
bring over 2 years of data and bring over the other 8 at another time

Use Case 5 12.1 Upgrade – Customer AAA
 Upgrading from R11.5.10.2 to R12.1.3 + Latest 12.1.3 RPC
 DB is already upgraded
 Using Upgrade request set to minimize data at upgrade
 Functional purging & archiving-completed; Support analyzers ran and reviewed
 Using staged appl_top; shared Appl_top; Distributive AD
 All Upgrade Preinstall Patches from Doc id: 1448102.1 are in project plan
 REDUCE DOWNTIME: Customer reviewed items to do in parallel with configuration settings and
saved time
 REDUCE DOWNTIME: The customer saw some long running scripts and was able to pre-create
some indexes after the first run to reduce downtime. Other long running items, customer logged
SR’s to solve before the Go Live Dates

Use Case 6 12.2 Upgrade – Customer ZZZ
 Upgrading from R11.5.10.2 to R12.2.7
 DB is already upgraded
 Using Upgrade request set to minimize data at upgrade
 Functional purging & archiving-completed; Support analyzers ran and reviewed
 REDUCE DOWNTIME: Customer reviewed items to do in parallel with configuration settings and
saved time
 REDUCE DOWNTIME: The customer saw some long running scripts and was able to pre-create
some indexes after the first run to reduce downtime. Other long running items, customer logged
SR’s to solve before the Go Live Dates

Holistic
Considerations
&
Resources

Gather Instance Specifics
 Full Technical Project team should know the scope of the following items:
TECH ITEMS:
 E-Business Applications Release xx to Release xx:
 Oracle DB version; (RAC?)
 Customization Evaluation and plan:
 Any OS, Platform Migrations:
 DB Size:
 Number of instances upgrading:
 How many languages:
 VM?; DMZ?; EXA-stack items?
Current Testing:
 Estimated Downtime / Cutover window:
 How many runs completed to date:
 Last timing of upgrade run:
TIMELINES:
 GO LIVE:
 Date(s):
 UAT/CRP’s:
 Dates
 Acceptance Guidelines
 Period/Quarter/Year End Close – Dates after go live

Holistic Best Practices
Know your Oracle Resources
Do several complete practice upgrades
 Use similar hardware as production environment during upgrade practices
 Use same data set in practice upgrades that you expect for production upgrade
Consider doing related systems changes during separate downtime(s)
 Examples: database upgrade, platform migration, OATM conversion.
Time all activities and try to fix bottlenecks
Optimize your timing
 Tune performance of the core upgrade driver… See
 Oracle E-Business Suite Upgrade Guide, Release 11i to 12.1.1
 Oracle E-Business Suite Upgrade Guide Release 11i to 12.2
 Oracle E-Business Suite Upgrade Guide Release 12.0 and 12.1 to 12.2
 Minimize duration of tasks performed before & after core upgrade driver runs
 Interim backups, final acceptance testing
Establish that the upgrade will fit into your downtime window

Oracle Resources to Help with Upgrade
Available to Customers on oracle.com and My Oracle Support (MOS)
Why Upgrade Planning and Executing Upgrade

 EBS 12.2 Upgrade Page  Upgrade Best Practices White Paper
Value, Cost and Service Plan roadmap & scope, Upgrade vs reimplement, Financials setup,
Oracle E-Business Suite Release 12.2 Helps Organizations Make Customizations, Related system changes, Minimize downtime,,
Better Decisions, Reduce Costs and Increase Performance Testing, Training, more
MOS Doc 1406960.1
 EBS 12.1 Upgrade page
Value, Cost, Service  EBS 12.2 Info Center, 12.1 Info Center
www.oracle.com/goto/upgrade-ebs-12-1 Release Content Documents (RCDs), Release Value Propositions
(RVPs), Online Training, Online Documentation, TRM, Proactive
 Learning Streams Support Tools, more
education.oracle.com/streams/ebusinesssuite MOS Doc 806593.1 for 12.2 1581299.1
 EBS Youtube Channel  Proactive Support Tools (aka 432.1)

EBS Strategy by Cliff Godwin, EBS Endeca demos, more Prevent: Patch Wizard, Workflow Analyzer, Newsletters, Advisor webcasts
http://www.youtube.com/oracleebsdemos Resolve: Period Close Advisor, EBS Patch Community, Product Info Center
Upgrade: Upgrade Advisor (Doc 269.1, 1614508.1 & 1593640.1),
 Customer Successes Maintenance Wizard, Patch Wizard, Comparison Reports
EBS Customer Success Search MOS Doc 432.1
http://www.oracle.com/search/customers/browse/_/N-1z13xx4

Oracle Services to Help with Upgrade
Expert Resources Readily Available
• Upgrade Best Practices White Paper (MOS Doc 1406960.1)
• EBS Info Centers: RCDs, RVPs, Training, Doc, more. (MOS Doc: 12.1 806593.1, 12.2 1581299.1)
Support • Proactive Support Tools Doc 432.1: Upgrade Advisor 12.1 Doc 269.1 12.2 Docs 1593640.1 1614508.1
Resources • Support Communities: Upgrade, Customizations, Patching, more
• Advisor Webcasts (MOS Doc 1455369.1)
• Available to all customers with active support contract
Advanced Support • Oracle Advanced Customer Services (ACS) : Tailored advanced services for your needs, including technical
Services expert onsite for few weeks for upgrade assessment at very low cost
• Oracle Consulting (OCS) : Upgrade assessments; upgrades & implementation projects

Consulting Complementary CEMLI Analysis (North America)
Services • Broad expert partner ecosystem
Managed Private • Oracle Managed Cloud Services: Your Oracle Applications managed any way you want; choice of hosting
@ Oracle, @customer, @ partner, or hybrid options
Cloud • Oracle EBS Upgrade Factory: Upgrade AND move from on-premises to managed cloud
Services • Many partner offerings

Resources 12.1 Upgrade
 Best Practices for Minimizing Oracle E-Business Suite Release 12 Upgrade Downtime Doc ID: 1581549.1
 R11i / R12 : Planning Your Oracle E-Business Suite (EBS) Upgrade from Release 11i to Release 12Doc ID:1406960.1
 Oracle® E-Business Suite Upgrade Guide Release 11i to 12.1.1 Part No. E16342-04
 http://docs.oracle.com/cd/B53825_08/current/acrobat/121upgrade.pdf
 Oracle E-Business Suite Release 12.1.3 Readme (Doc ID 1080973.1)
 Review the latest Release notes:
 Oracle Applications Release Notes, Release R12.1.3 (Doc 1080973.1)
 Oracle Applications Release Notes, Release 12.1.1 (Doc 798258.1)
 Review Pre Install Patch (Doc 1448102.1)
 Apply Consolidated Upgrade Patch (CUP) for fixes to upgrade code
 Oracle Applications Patching FAQ for Release 12 (Doc 459156.1)
 Oracle Applications Patching FAQ for Release 11i (Doc 457566.1)
 How to find E-Business Suite and E-business Suite Technology Patches (Doc id 1633974.2) – Latest 12.1.3 RPC Patches
 Related Articles on Oracle E-Business Technology Blog- https://blogs.oracle.com/stevenChan
 E-Business Suite Release 12.1.3 Now Available
 Distinguishing Between E-Business Suite 12.1 and 12.0 Patches
 Comparisons of E-Business Suite Release 12 Rapid Install Techstacks
 Whitepaper Update: Planning Your E-Business Suite 11i Upgrade to R12.1 (Third Edition)
 New Whitepaper: Upgrading your Customizations to Oracle E-Business Suite Release 12

Additional 12.1 Resources
Planning your Oracle E-Business Suite (EBS) Upgrade from Release 11i to Release 12(Doc 1406960.1)
 35 Tips
AD Command Line Options for Release R12 (Doc Id 1078973.1)
Cloning Oracle Applications Release 12 with Rapid Clone (Doc Id 406982.1)
Patching Best Practices And Reducing Downtime (Doc: 225165.1)
Patching Shared Oracle E-Business Suite Products (Doc:1069099.1)
Oracle E-Business Suite Release 12.1 Info center (Doc ID 806593.1)
R12 Upgrade Sizing & Best Practices (Doc Id 399362.1)
Database preparation guidelines for R12.1 upgrade (Doc Id 761570.1)
Oracle Applications Documentation Resource, Release 12.1 (Doc ID 790942.1)
Release 12.1 Reducing downtime:

 E-Business Suite Release 12.1 Upgrade Best Practices - Technical Insight
 Minimizing Oracle E-Business Suite Maintenance Downtimes
23 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. UG = Oracle E-Business Suite Upgrade Guide Release 11i to 12.1
Resources 12.2 Upgrade
 12.2 Information Center: Doc ID: 1581299.1
 Oracle E-Business Suite Release 12.2: Upgrade Sizing and Best Practices Doc ID: 1597531.1
 Best Practices for Minimizing Oracle E-Business Suite Release 12 Upgrade Downtime Doc ID: 1581549.1
 R11i / R12 : Planning Your Oracle E-Business Suite (EBS) Upgrade from Release 11i to Release 12 Doc ID:1406960.1
 Oracle® E-Business Suite Upgrade Guides
 http://docs.oracle.com/cd/E26401_01/doc.122/e48839.pdf 12.0 – 12.1 to 12.2
 http://docs.oracle.com/cd/E26401_01/doc.122/e87011.pdf 11.5.10.2 to 12.2
 Oracle E-Business Suite Release 12.2.7 Readme (Doc ID 2230783.1)

 Review the latest Release notes:
 Oracle E-Business Suite Release Notes, Release 12.2 (Doc 1320300.1)
 Apply Consolidated Upgrade Patch (CUP) for fixes to upgrade code
 Oracle E-Business Suite Release 12.2.5 Readme (Doc 1983050.1)
 Oracle E-Business Suite Release 12.2.6 Readme (Doc 2114016.1)
 Oracle E-Business Suite Release 12.2: Online Patching FAQ (Doc 1583902.1)
 Related Articles on Oracle E-Business Technology Blog- https://blogs.oracle.com/stevenChan
 Oracle E-Business Suite Release 12.2.7 Now Available
 Oracle E-Business Suite Release 12.2.6 Now Available
 Should You Upgrade to E-Business Suite 12.1.3 or 12.2?
 Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)
 Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)
 Database preparation guidelines for an E-Business Suite Release R12.2 upgrade (Doc Id 1349240.1)

General Upgrade Resources
How to Find E-Business Suite and E-Business Suite Technology Patches (Doc 1633974.2)
Reduce data volume using archive and purge (Doc 752322.1)
Use Subledger Accounting “Upgrade by Request” (Doc 604893.1)
Run “The Upgrade Manual Script” to identify tasks you can omit
Complete functional pre-upgrade tasks in Reducing Downtime section of the Upgrade Guide
Use a shared APPL_TOP (Doc 384248.1)
Use a staged APPL_TOP (Doc 734025.1)
Distributed AD (Doc 236469.1)
Isolate post-upgrade concurrent programs in a special queue (Doc 399362.1)
OAM “Patch Wizard” overview and FAQ (Doc Id 976188.1, 976688.1)
Patching FAQs (Doc Id 459156.1, 225165.1, 1583902.1)
My Oracle Support - Certifications Tab
Lifetime Support Policy - http://www.oracle.com/us/support/lifetime-support/index.html
Recommended Performance Fixes (Doc Id 244040.1)
25 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. UG = Oracle E-Business Suite Upgrade Guide Release 11i to 12.1
OOW 2016 - Materials
 CON6714_Parvate-TechnicalUpgradeBestPracticesforOracleE-BusinessSuite_12-2
 CON6711_Barakat-EBS_Performance_Best_Practices_OOW15
EBS Technology Blog

 Getting Started: 12.2: https://blogs.oracle.com/stevenChan/entry/revised_ebs_12_2_getting
 Customizations: https://blogs.oracle.com/stevenChan/entry/preparing_your_customizations_for_ebs
 ETCC Tool: https://blogs.oracle.com/stevenChan/entry/etcc_patch_tool_enhancements_feb
 Quarterly EBS Upgrade Recommendations: Jul 2017 Edition : (always check for newest) https://blogs.oracle.com/stevenchan/quarterly-
ebs-upgrade-recommendations%3a-july-2017-edition
 Example: When new Start Cd’s come out
https://blogs.oracle.com/stevenChan/entry/rapid_install_startcd_51

Prevent.
Oracle E-Business Suite Proactive Portfolio
Resolve.
Leverage the capabilities below to reduce risk, solve problems, and focus on preventative maintenance. Upgrade.
All offerings are part of your Oracle Premier Support contract and available at no additional charge.
PREVENT Product Based Analyzers How to find EBS Patches, Patch EBS Period Close Advisor EBS Accreditation
Over 60 Analyzers provide Wizard & Maintenance Advisors This Period Close Advisor allows Self-paced learning experience.
recommendations & early warning 1633974.2 is a one stop shop. you to get proactive by providing
detection as part of a production Includes Patch Wizard & guidance on recommended period Stay Informed
strategy. Many are executable by maintenance advisors. Stay end procedures for E-Business Take advantage of Advisor
end-users. current with Recommended Release 12.x. webcasts on EBS products. Follow
New Analyzer Bundle Menu Tool patches. us on Twitter and our blogs to get
assists with provisioning & the latest news.
maintenance of EBS Support
Analyzers.
RESOLVE Assistants (Search Helpers) & E-Business Community Finding Answers and Working ORAchk
Product Information Centers Connect and collaborate with Effectively with Support (WEWS) ORAchk scans and provides a high
Assistants (Search Helpers) and Oracle and peer experts on topics Learn best practices, tips, and tricks level report showing your system
Product Information Centers guide such as Patching, Upgrade and through videos and labs to health risks with the ability to drill
you to important E-Business Suite many more. effectively search in My Oracle down into specific problems and
information. Get what you need ERs to Community Support. understand their resolutions.
and get it fast. Create, share and vote on product
enhancements
UPGRADE 12.1 & 12.2 Information Centers Pre-Install Patch Report Upgrade Advisor Comparison Reports
The Upgrade information centers A single point of reference for Easy to follow upgrade process flow,  Data Model
are one-stop location for all your upgrade-related patches (can only providing document on best  Seed Data
upgrade needs with tools and be applied prior to running main practices and recommendations on  File Comparison
latest documentation and notes. upgrade driver for 12.1/12.2) Upgrade lifecycle phases including Three reports show the changes
Evaluate, Plan, Configure & Test, between two
and Implement & Accept. E-Business releases.
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Copyright © 2016 Oracle and/or its affiliates. All rights
Certification*
Verify certification of any

combination of Oracle,
third-party products and
operating systems that
Oracle has tested and
confirmed work together

Lifetime Support Policy
 http://www.oracle.com/us/support/lifetime-support/index.html
 Lifetime Support Policy: Oracle Applications (PDF)
 Oracle E-Business Suite Error Correction Support Policy (V.5) (Doc ID 1195034.1) –(V.5, 1/29/2015)

E-Business Upgrade Advisors
 Upgrade Lifecycle Advisors are
specially crafted documents-
Phase Approach
 Provides step-by-step
instructions to perform an
upgrade
 Easy to follow upgrade process
 Access to the relevant
information and knowledge
dependent on current phase/step
in the Lifecycle process
 Potential to reduce the total
upgrade lead time

Patch Wizard – Doc 976188.1
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

Recommended Patch Collections for EBS 12.1.3 Released
RPC5
 One Consolidated patch across product families
 Recommended Patch Collection 5 (RPC5) includes:

o Applications Technology (ATG) o Procurement (PRC)
o Customer Relationship Management (CRM) o Projects (PJ)
o Financials (FIN) o Supply Chain Management (SCM)
o Human Resources Management (HRMS) o Value Chain Planning (VCP)
o Oracle Business Intelligence
Oracle E-Business Suite Release 12.1.3+ Recommended Patch Collection 5 (RPC5) (Doc ID 2152266.1)

Customization
Considerations

Customization Considerations
Customization Usage Review:
 Check and review customizations that business might not be using: Reports, programs
 Review and eliminate redundant custom indexes
 Review new Product Features or New Technology to Migrate to
Documents:
 Oracle E-Business Suite Developer’s Guide Release 12.2 Part No. E22961
 Upgrading your Customizations to Oracle E-Business Suite Release 12.1 Doc ID: 1435894.1
 Creating a Custom Application in Oracle E-Business Suite Release 12.2 Doc ID 1577707.1
 Deploying Customizations in Oracle E-Business Suite 12.2 Doc ID: 1577661.1
Guidance for Integrating Custom and Third-Party Products With Oracle E-Business Suite Release 12.2 Note:1916149.1
 Custom APEX Application interacting with E-Business Suite 12.1 via public APIs Proof of Concept
 APEX certification Whitepaper
Tools to Analyze Customization when Upgrading
 Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2 (Doc ID 1531121.1)
 Request your complimentary CEMLI Benchmarking & Analysis today!
 http://www.oracle.com/webapps/dialogue/ns/dlgwelcome.jsp?p_ext=Y&p_dlg_id=13735691&src=7618001&Act=92
 EBS Data Model Comparison Report – Doc Id: 1290886.1
 EBS ATG Seed Data Report – Doc Id: 1327399.1
 EBS File Comparison Report- Doc Id: 1446430.1
Other
 2016: Oracle Open World: CON6708-Migrating and Managing Customizations for Oracle E-Business Suite12.2
 2014: Oracle Open World: Online Patching Overview for Oracle E-Business Suite Release 12.2
 Upgrading E-Business Suite 11i Customizations to R12 (2011)
 http://oukc.oracle.com/static05/opn/login/?t=checkusercookies&%E2%81%9Er=-1&c=1044540202
 EBS Technology Blog – Support Implications for your EBS Customizations

12.2 Global Standards Compliance Checker
(GSCC) and Readiness Report
1. Check & Comply in
Advance of 12.2 Upgrade
2. Periodic Maintenance
Check
*Check for latest patches

12.2 Customization Documents
Oracle® E-Business Suite, Developer's Guide Release 12.2
Part No. E22961-13

12.2 Customization Documents

EBS Data Model Comparison Report
 Provides the database object definition
changes between two E-Business
releases
 Helps to preview the database object
definition changes before upgrading
 Shows impact analysis of the database
object changes that may affect
customizations or business flows

ATG Seed Data Model Comparison Report
 Provides a delta view between different
E-Business releases by documenting
the seed data changes
 Delivered by the product data loader
files (.ldt extension)
 Based on the E-Business ATG loader
control (.lct extension) files

EBS File Comparison Report

Oracle Consulting CEMLI Benchmarking Tool
Interactive tour of customer CEMLI environment
Flash Based Report
CEMLI Summary Interactive CEMLI Graph CEMLI Benchmarking
photo photo photo
High level dashboard summary detailing CEMLI data visualization via interactive CEMLI Benchmarking report by customer
the customer CEMLI profile. Flash based charts or data grids with drill peer group, CEMLI category, and object
down capabilities. type.
Overview section provides instructions for
using each the sections within the tool
(Interactive CEMLI Chart as well as CEMLI View customization counts by high level
Relative percentile ranking of a customer’s
Benchmarking Data.) CEMLI categories as well as specific
level of customization compared to other
application type.
customer peer groups .
© 2011 Oracle Corporation – Proprietary and Confidential

41 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 41
Data Set &
Cleaning Data

Data Set & Data Cleaning - Overview
 Production Purging and Archiving
 Purge old and/or transient data before upgrading
 OAM->Purging/Critical Activities - “Purge Portal”
 11.5 Purge avail
 R12 has some improved purge programs - over 260
 Add to R12 Maintenance plans/Change management plans
 Production Data review and cleaning
 Flush all the interfaces, such as Autoinvoice, Journal entry import, order import etc..
 Decide on the Upgrade Request Data Set for Upgrades from 11i to R12
 Minimize historical data to be upgraded as per business requirements – “Upgrade
By Request”
 Post-upgrade “hot-patch” of additional historical data outlined in 604893.1

EBS Archiving & Purging
 Reducing Your Oracle E-Business Suite Data Footprint using Archiving, Purging, and
Information Lifecycle Management (Doc ID 752322.1)
 52 Page PDF
 Data Lifecycle
 Product Table information
 Reference to each product Guide
 Example: Oracle® Assets User Guide Release
11i: Chapters 3,5,11 Part No.: A81359-08
 Appendix A:
 Page 42-EXAMPLE ARCHIVE & PURGE
PROGRAMS (ORACLE E-BUSINESS SUITE
REL 11.5.10)
 Appendix B:
 Page 45: EXAMPLES ARCHIVE PURGE
PROGRAMS (ORACLE E-BUSINESS SUITE
RELEASE 12)

EBS Purging
 Use OAM to configure, initiate and monitor purge programs
 Set the execution frequency and view program history
 Programs tagged with the “Purge” program type
System Administrator >Oracle Applications Manager >Purging/Critical Activities

Manage Data Volumes
Purge Old and/or Transient Data
• Archive/Purge Product Information
–Product User guides – GL/AP/AR/FA/OM
–Support Notes:
• (DOC ID 390353.1) – General Ledger Archive/Purge FAQ
• (DOC ID 144431.1) – Fixed Assets Archive/Purge FAQ
• (DOC ID 1073185.1) – Receivables Archive/Purge FAQ
• (DOC ID 136919.1) – General Ledger Archive/Purge Setup and Usage
• (DOC ID 752322.1) : Reducing Oracle E-Business Suite Data Footprint

– EBS Technology Blog: Link

Oracle Workflow Analyzer –Doc 1369938.1
 Proactive script that reviews the current Workflow Footprint

 Analyzes the configurations, and your environment
 Provides feedback, and recommendations on best practices and areas of concern
 Immediate analysis and output of Workflow environment.
 Easy To add tool for regular Workflow maintenance.
 Execute anytime to compare trending from past outputs
Oracle Concurrent Processing Analyzer
Doc 1411723.1
 Immediate Analysis and Output of
Concurrent Environment
 Identifies Concurrent System Setup and
configurations
 Identifies and recommends Concurrent Best
Practices
 Easy to add Tool for regular Concurrent
Maintenance
 Execute Analysis anytime to compare
trending from past outputs

432.1  E-Business Suite > Analyzers Index Doc ID 1545562.1*
 EBS  Financials  Manufacturing
 Workflow analyzer script  R12: Master GDF Diagnostic to  11i/12: Inventory Health Check
 Concurrent Processing – CP validate Data related to invoices,
 R12 Order Management Sales Order
Analyzer Payments, Accounting, Suppliers
and EB Tax  R12 Shipping Execution
 EBS Reports and Printing
 R12: Period Close Analyzer  V6.2 OTM Analyzer
 EBS Cloning Log Parser
 R12: EBTax Setup and Data  R12 PO Approval Analyzer
 Database Parameter Settings
Integrity Analyzer  R12 IP Item Analyzer
Analyzer Script for Optimal
Performance  R12: Payables Trial Balance Helper  SCM/VCP: 9 Available
 Human Capital Management
 R12: Oracle Payments (IBY) Funds  ASCP
Disbursement Analyzer
 RetroPay Analyzer  Demantra
 R12: Internet Expense Setup
 HCM Technical Analyzer Helper  Discrete LCM
 R11i / R12 OTL Analyzer  AutoInvoice Post Process  OPM LCM
 EBS HCM Person Analyzer Validation Report  CRM
 Payroll Analyzer  AutoAccounting Analyzer  IB Analyzer

Upgrade By Request (11i to 12.x)
 Option to omit the upgrade of historical data from the initial upgrade process (critical downtime
window)
 Historical data can be upgraded anytime when system is up
 Implementation is a two step process:
 Set range of historical data to be upgraded before R12 upgrade and run the pre-upgrade
concurrent program
 Run the post-upgrade concurrent program (as needed for additional historical data)
 Review Upgrade By Request Appendix in R12.1 or 12.2 Upgrade Manual for more details
 Customer Relationship Management
 Financials and Procurement (example in appendix of subledger accounting)
 Supply Chain Management
 Projects
 Oracle® E-Business Suite Upgrade Guide Release 11i to 12.1.1 or 12.2
 http://docs.oracle.com/cd/E26401_01/doc.122/e87011.pdf
 See: “FAQ for the SLA Upgrade: SLA Pre-Upgrade, Post-Upgrade, and Hot Patch” (604893.1)

Example: Subledger Accounting- (11i to 12.x)
Upgrade Modes
 Full upgrade: All historical accounting data is upgraded

 AX, Loans, Property Manager
 Partial upgrade: Some historical data is upgraded
 AP, AR, Assets, Costing, Projects
 You determine the range of periods
 SLA Upgrade Historical Subledger Transaction Program is available post-
upgrade
 No Upgrade: No historical accounting data is upgraded
 Cash Management, Federal/Public Sector, OPM

Important 12.2
notes

12.2 Information Center- 1581299.1

12.2 Planning Guide
Oracle E-Business Suite Release 12.2: Technical Planning Guide and Go-Live Readiness Checklist (doc ID 1585857.1)

12.2 Global Standards Compliance Checker
(GSCC) and Readiness Report
1. Check & Comply in
Advance of 12.2 Upgrade
2. Periodic Maintenance
Check
*Check for latest patches

12.2 Notes to call out
 TECH DOCS: 12.2 info center:
 1581299.2: Oracle E-Business Suite Release 12.2 Information Center (Doc ID 1581299.1)
 Oracle E-Business Suite Release 12.2 Technology Stack Documentation Roadmap (Doc ID 1934915.1)
 Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID
1594274.1)
 Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID
1617461.1)
 Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite (Doc ID
1147107.1)
 Sizing:
 Database and Application Tier Sizing Guidelines from our 12.2 Install Guide.
 Oracle Open World 2015 Presentation:
 Presentation Download CON6711-Barakat-Getting Optimal Performance from Oracle E-Business Suite
 Oracle XML Gateway Sizing and Performance Guidelines
 Configuration
 Managing Configuration of Oracle HTTP Server and Web Application Services in Oracle E-Business Suite Release
12.2 (Doc ID 1905593.1)

Pre Upgrade
&
Configuration
Setting
Considerations

Pre-Upgrade activities
 11.5.10
 11.5.10 Minimum Baseline patches
 Doc ID: 883202.1 & Patch Wizard Support Filter
 Required for 12.2 Not Required for 12.1
 12. 0
 Check Patch Wizard for recommended patches
 Minimum Baseline/ Error Correction Policy Patches
 12.1
 Error Correction Policy Patches- Doc ID 1195034.1
 12.2
 12.2 Global Standards Compliance Checker (GSCC) and Readiness Report - Doc id:
1531121.1
 12.2 Technical Planning Guide – Doc Id: Doc id: 1585857.1
 Error Correction Policy Patches- Doc ID 1195034.1

12.1/12.2 CUP & Pre-Install Patches- Doc 1448102.1
12.1 CUP 2*/12.2 CUP 8*
(always check for latest CUP)
Pre-install patches for R12.x

R12.x patch that delivers higher versions
for files called by the R12.x main
upgrade driver
Monthly updated of EBS Wide pre-
install patches
Patches Categorized
Upgrade Failure
Upgrade Performance
Data Fix
Consolidated in one location
ALL EBS pre-install
Merge with R12.x main upgrade
driver

12.2 Online Patching Call out
• Pre-Online Patching Enablement checks
• Verify that all the database patches required by 12.2 Doc 1594274.1 are applied. Refer to the top part of this
document to get specifics on how to validate this.
• Verify that the latest CUP, as per the R12.2 release notes, is applied. Refer to the top part of this document to get
specifics on how to validate this.
• Verify that AD 12.2 upgrade patch 10117518 was merged with the latest AD CUP and that adgrants.sql has been
run from the merged patch directory, currently CUP8 (24690520) as per instructions in AD 12.2 upgrade patch
(10117518) Readme (Linux version, please consult the correct version for your platform). This merge had to be
done in admode prior to applying the patch. Instructions for performing this step are in the R12.2 Upgrade Guide,
section "Performing the upgrade".
• Make sure that the package AD_ZD_PREP is valid. You can check AD_ZD* package status using - select owner,
object_name, object_type, status from dba_objects where object_name like 'AD_ZD%';
• sqlplus apps/apps @$AD_TOP/sql/ADZDSHOWAD - Before allowing customers to proceed with the enablement
process, we have to make sure that they reviewed the latest version of the Readiness and Standards Compliance
Reports ( Note:1531121.1) and have addressed all the violations reported by the same.

Pre-Upgrade activities-separate downtimes
 Identify and execute tasks that could be completed in a separate
downtime period, prior to the production upgrade
 Use applicable steps mentioned in the “Reducing Downtime" and “Upgrade
By Request” appendices in R12.1 or R12.2 upgrade guide.
 Convert to Oracle Applications Tablespace Model (OATM) – Doc Id

404954.1
 Compacts data, optimizes storage settings and I/O
 Must be done before upgrade to 12.2 or can never be done.
 Convert to Multiple Organization architecture (Doc Id 210193.1)
 Drop MRC schema (11.5.10 and above )
 Upgrade RDBMS version to latest certified for the current APPS level
(Check Certify for latest Certifications on My Oracle Support)
 Other planned HW or OS upgrades (new HW; 64 bit)
 Review and disable all debug, logging at site,
responsibility, user level
 See notes if debug is not disabled
 Gather stats with GATHER_AUTO option for all schemas

close to the start of downtime
 Use TUMS (“The Upgrade Manual Script”)

 11i upgrade to 12.X only
 To avoid running tasks not relevant to your system

Gather Dictionary and Fixed Stats
 Gather dictionary object statistics when there is a significant
change in dictionary, for example, lot of new objects created.
exec dbms_stats.gather_dictionary_stats;
• Gather fixed object statistics with reasonable load on the
system exec dbms_stats.gather_fixed_objects_stats
• Dictionary and Fixed stats should be gathered manually as they
are not gathered automatically in the Release 12 upgrade by
adsstats.sql or any other method.

Gather Dictionary and Fixed Stats
• Fixed Object Statistics should be gathered:
–After any associated platform or database upgrade that is part of the
overall Oracle E-Business Suite upgrade.
–After any SGA/PGA parameters have changed.
–After Release 12 upgrade, when there is representative activity on
the system.
• Dictionary Statistics should be gathered:
–After any associated platform or DB upgrade that is part of the overall
Oracle E-Business Suite upgrade.
–After the Release 12 upgrade.
–After move to OATM
Configuration consideration/checks
 For the duration of the upgrade, consider…
 Disabling custom: triggers, business events and VPD policies
 Disabling auditing if enabled
 If possible run in noarchivelog mode
 Disabling flashback DB
 Removing Transparent Data Encryption (TDE) from volume tables
 Assign post upgrade jobs to specialized CM queue (by
request_type, see Document 399362.1)
 Utilize Parallel Concurrent Processing (PCP) for post-upgrade
concurrent jobs to leverage the Cluster (RAC) - Doc:1359612.1*
 Import statistics – Example - Doc: 117203.1
 Export statistics gathered during test runs, and import during final run

* See note section of powerpoint
Configuration considerations/checks
 Database tier configuration

 Maximize SGA and PGA sizing
 An upgrade only involves 10's of concurrent sessions;
starting rules of thumb ...
 log buffer = 30 to 100 Mb
 shared pool = 1 to 4 Gb
 pga target = 3 to 20 Gb
 SGA/buffer cache = multi Gb, be generous without
causing excessive paging or swapping


Use Large/Huge pages. For example on Linux HugePages
– See MOS ID 744769.1
– MOS ID 361468.1, “HugePages on Oracle Linux 64-bit”
describes how to configure hugepages. When running the
recommended script provided with Note 401749.1, make sure
that all database instances are started.
– Only SGA allocation benefits from large/huge pages, PGA
allocation does not.

 Database tier configuration less than 32 cores
 Other upgrade specific init.ora changes
 If specified, remove db_file_multiblock_read_count
 Maximize multiblock I/O sizes
 Set optimizer_dynamic_sampling = 4 during upgrade only
 Set job_queue_processes = # of CPU cores
 Helps with compiling invalid objects faster
 Set parallel_max_servers = 2 X CPU cores
 Helps with large index creation, stats gathering and some large upg+
phase jobs
 Set recyclebin = off
 AD Parallel workers – start with 1x number of CPU cores. Possibly increase
to 1.5 x number of CPU cores.
 Need to test with production-like DB server and I/O subsystem
 Database tier configuration more than 32 cores
 Other upgrade specific init.ora changes
 If specified, remove db_file_multiblock_read_count
 Maximize multiblock I/O sizes
 Set optimizer_dynamic_sampling = 4 during upgrade only
 Set job_queue_processes = # of CPU cores
 Helps with compiling invalid objects.
 Set parallel_max_servers = 1 X CPU cores
 Helps with large index creation, stats gathering and some large upg+
phase jobs
 Set recyclebin = off
 AD Parallel workers – between 0.5 and 1.0 x number of CPU cores.
 Need to test with production-like DB server and I/O subsystem

 Shutdown other RAC instances
 Only run the Release 12 upgrade on one Oracle RAC node. The majority of the elapsed time of the
Release 12 upgrade is taken by jobs running DML (INSERT, UPDATE, DELETE). These jobs use multiple
workers/parallel severs, which all access the same objects and blocks at the same time. So the additional
communication between nodes on the cluster (and cluster waits) will significantly outweigh the gains from
using the additional CPUs to increase throughput.
 To answer the subsidiary question "Does RAC really help performance or just
provide redundancy?“
 RAC will only help performance if you have effective node affinity. i.e. you arrange your modules /
workload across different nodes, so that blocks (from DB objects) are usually only used by one node, this
limits the communication between nodes on the cluster (which you will see as "gc" waits). So we
encourage customers to configure EBS so that different modules are on different nodes ......... or different
types of processing are on different nodes (e.g. concurrent and on-line).
The R12 Upgrade will not have good node affinity. It has not been designed as multiple concurrent
workloads (doing different things on different sets of objects), but as one stream of work, multi-threading,
with the threads often accessing the same objects/blocks at the same time.

Performance Considerations
 Pre-create new large indexes created by upgrade *
 constrained to indexes on existing columns
 No exact list, Customer Dependent based on perf/data/products
 Example: Specific to an upgrade script having issues - R12 :
Performance Issue While Running apilnupg.sql (Upgrade to
12.1.1) (Doc ID 942694.1)
 General
 Review 244040.1 for latest EBS recommended performance fixes

• For long running jobs or SQLs, it is best to start by investigating if good

execution plans are being used. A poor execution plan (or even just one that
is moderately sub-optimal) can be the root cause of contention, especially if
that contention only occurs during a particular job.
• Create custom indexes for long running jobs where a new index could
significantly improve the execution plan and performance
• For long running jobs with high level of contention on particular index
segments , consider dropping the index before the job and recreating
afterwards. Ensure that indexes are recreated in parallel and with exactly
the same definition. And remember to ALTER INDEX to revert the degree of
parallel (NOPARALLEL).

• For long-running xdf or odf jobs creating materialized views (MV), consider
cleaning up or truncating of any large MV logs (this requires MV complete
refresh)
• For high level of waits associated with redo log, especially “log buffer space”
and “log file sync”, consider:
– Change the configuration of redo logs
– Move to faster filer
– Increase redo log file sizes, increase the number of files or increase the
log parallelism (hidden parameter _log_parallelism_max).

POST Upgrade Middle Tier Sizing Guidelines
• Managed instances JVM sizing should consider both memory and CPU
domains.
• On 64bit environment, we do not recommend allocating huge heap sizes,
but rather have more managed instances in the cluster to scale up to the
target concurrency levels.
• For Admin Server sizing, the default size of 512M is not enough for most
installations, we recommend setting the XMS to at least 1 GB and the XMX
to 2GB
• An initial guidance on sizing can be found in the “Oracle E-Business Suite
Installation Guide: Using Rapid Install”
• Managing Configuration of Oracle HTTP Server and Oacore, Oafm, Forms
and Forms-c4ws Applications in Oracle E-Business Suite Release 12.2 (Doc
ID 1905593.1)

Method of
Upgrade

Preinstall R12.1 / R12.2 upgrade file system.
 Downtime reduction procedures

 Install Upgrade File System ahead of scheduled production
downtime.
 Apply ALL tech stack patches to middle tiers
 Consider upgrading FMW Oracle Homes to 11.1.1.9 – required
for 12.2.5+. (start cd 51 you get 11.1.1.9)
 Merge and apply ALL preinstall patches and upgrade CUP
patch.
 Merge preinstall patch and CUP patch drivers with main upgrade
driver.

Shared APPL_TOP & Distributed AD for 12.1.3
 Use “Shared APPL_TOP” (384248.1) with “Distributed AD”
 Allows upgrade to utilize the hardware resources of middle tier
machines to increase overall number of ad patch workers.
 No need to apply the same post upgrade patches on multiple tiers
 Distributed AD adds to the degree of parallelism by distributing AD

workers across application tier nodes and improves timing for copy
and generate portion of the patch driver.
 Do not get tempted to use more workers than necessary. Avoid

high worker counts that might lead to contention issues.

Shared APPL_TOP & Distributed AD-12.1.3
Admin/CM ad patch
Server workers 1-10
Forms ad patch
Server 1-10
workers 11-20
Shared
APPL_TOP
Web ad patch
Server workers 1-10
21-30
Database
Server
ad
ad patch
patch
Web workers
Server
workers 31-40
1-10

The above reflects Oracle’s current development plans which are subject to change at any time
Parallelize - Pre Apps Upgrade Options:
OATM – combine with DB upgrade in separate downtime.
Perform PRE Upgrade AD patching prior to main upgrade
Install R12 upgrade file system prior to upgrade.
Perform tech stack patching on R12 upgrade file system prior to upgrade.
Apply pre-install 12.1.1/12.2 patches prior to main downtime
Be sure to increase init.ora parameters during upgrade
Disable archive logging prior to starting upgrade.
Verify appropriate db space is available prior to main upgrade.
Increase ad patch batch size to 10,000 for large systems.
Continuously run the RDBMS script “$ORACLE_HOME/rdbms/admin/utlprp.sql 1”
from the database techstack during the upgrade run.
 Do NOT use parallel recompile for this as it may interfere with ad patch when it
runs the recompile adobjcmp.sql..

Parallel Autoconfig 12.1.3 & 12.2 post upgrade
 Run autoconfig in parallel on a multi-node system

Settings during upgrade
 Batch size and #workers

 Batch size
 The default of 1K is suitable for most patches, you can test other values
from 1K up to 10K for upgrades and rup’s.
 # Workers
 Starting rule-of-thumb is between 1 and 1.5 x #COREs
 It is critical to do multiple rounds of testing, adjusting above settings to
maximize server utilization, but constrained by factors such as
 Memory utilization (no swapping/ excessive paging)
 CPU utilization (scale down if at 100%)
 I/O response times (scale down if averages > 20 ms)

Identification of required patches
 Prepare a complete list of pre and post patches and recommended code levels
 Keep the system current on AD/ATG/OAM code e.g. latest AD/TXK and ATG
RUPs on 11i/R12.0 and on R12.1 or 12.2 after upgrade
 Review “Known-issues” sections from key “living” documents such as Release
notes, Maintenance Pack Install Instructions and Release Update Packs.
 AD and TXK Latest patches 12.2
 Consolidated Upgrade Patches (CUP)
 EBS R12.2 CUP 8 (Patch 24690520)
 EBS R12.1 CUP 2 (Patch 16791553)
 Latest pre-install patches (1448102.1) apply ALL patches
 Performance, script issues, data issues – updated every other month
 Recommended post upgrade High Priority patches from Patch Wizard Filter
 All patches with status Not Applied & Missing

Patching with ad patch for 12.1
 Patch merging, sequencing and ad patch options
 Use non-interactive patching
 Merge patches (228779.1). Merge NLS patches per language.
 Perform uptime maintenance when possible
 hot patching of iHelp, NLS patches, upload patch history
 Apply HRGLOBAL as a hot patch (1330470.1)
 When using ad patch for patches other then for upgrades,
maintenance packs or rollups, you can use options such as
phtofile, nolink, nogenform, nogenrep, nocompile jsp,
noautoconfig, novalidate (1078973.1)
 Get a full APPL_TOP ad snapshot after upgrade*
Patching with adop for 12.2
 Patch NLS and iHelp options
 Perform uptime maintenance when possible
 Apply iHelp using adop with the option hotpatch=yes
 Apply HRGLOBAL in “downtime” mode only during upgrade.
 Apply NLS patches using full adop cycle after 12.2.7
 Once you get to 12.2.7 you can apply the 12.2.0 NLS patches and
12.2.7 NLS patches. They should be applied in a adop cycle. This
would significantly reduce the upgrade downtime.
 The translation sync patch can be applied in the same adop cycle.
Oracle E-Business Suite NLS Release Notes, Release 12.2 (Doc ID
1314621.1)
 Get a full APPL_TOP ad snapshot after upgrade*
Post Upgrade item: R12.1 Caching issue:
 Intermittent Oracle Reports REP-0069: REP-57054: Error (Doc ID 1237834.1)

 Reports Cache Directory in Oracle E-Business R12 is Growing Rapidly (Doc ID 859255.1)
 Patch 11669923 Post Patch Instructions Would Get Overridden By Autoconfig (Doc ID
1322704.1)

Re-Review
Every Run

Support Items worth re-addressing
 EBS CUP Patches– Readme has important steps – preinstall patch and then Merge the U-Driver with the master upgrade driver.
*see sample readme in notes
 Pre-install patches for R12.1 and 12.2 – Doc 1448102.1 – (apply all Pre-Install)
 R12.x Post Upgrade Concurrent Processing Job Step
 12.1 Do not Skip these. Make sure all jobs complete successfully otherwise stop and fix before proceeding to 12.1.3
 12.2 These are combined and all run after upgrade to 12.2.7 is complete. Make sure all jobs complete to continue.
NLS – Another option to save time
 Evaluate if you can do NLS after Production vs during Downtime – also possible during Preinstall upgrade file
system approach.
 Internationalization Update Notes for Release 12 (Doc ID 393320.1) - PDF Output
In Oracle E-Business Suite R12, Oracle Reports PDF output is only supported for US7ASCII, WE8ISO8859P1
and WE8MSWIN1252. Customers who wish to generate PDF output files in other character sets are
recommended to move to BI Publisher.
Transportable Tablespaces
 The note 'Using Transportable Tablespaces to Migrate Oracle E-Business Suite Release 11i Using Oracle
Database 11g Release 2 Enterprise Edition (Doc: 1366265.1)- certifying 11i/11gR2 Transportable tablespaces
with either 10gR2 (10.2.0.5) or 11gR1 (11.1.0.7) as the source database in addition to 11gR2.

After each Upgrade Run- Review for...
 Performance testing, monitoring and additional optimizations
 Analyze long running jobs via timing report adtimrpt.sql and table ad_task_timing analysis
 Mine ad_task_timing to identify low worker utilization due to phasing waits and review responsible culprits
 Use My Oracle Support to check for known issues and workarounds for the longest running jobs (Pre-install
should fix many)
 Review Database Performance Tuning Guides –
 Oracle® Database Performance Tuning Guide 10g Release 2 (10.2) B14211-03
http://docs.oracle.com/cd/B19306_01/server.102/b14211/autostat.htm
 Oracle® Database Performance Tuning Guide 11g Release 2 (11.2) E41573-03
http://docs.oracle.com/cd/E11882_01/server.112/e10821.pdf
 AD Parallel tables: The AD_PARALLEL_UPDATES, AD_PARALLEL_UPDATE_UNITS tables can
give information on the actual rows processed, the number of batches, progress over time, and
long running batches (that might indicate locks/sleeps or data distribution issues).

 Outside-the-box optimizations – Requires Testing/Resources*
 Long running index creation and Statistics gathering
 As these tasks run with little or no concurrent tasks,
consider using alter system commands to increase
parallel_max_servers and pga_aggregate_target
 *Need to test so as to not exhaust machine resources
 Large indexes: Pre-create, but do not alter column
definitions
 For stats (adsstats.sql ; phase: last+63) : Consider stats
import or on RAC using all nodes when gathering stat*(next
slide for details)
 Specific to an upgrade script having issues - R12 : Performance
Issue While Running apilnupg.sql (Upgrade to 12.1.1) (Doc ID
942694.1)
Best Practices for Minimizing Oracle E-Business Suite Release 12 Upgrade Downtime (Doc ID 1581549.1)
*For stats (adsstats.sql ; phase: last+63) : Consider stats import or on RAC using all nodes when gathering stat
If the adsstats.sql script is taking a significant amount of time to run, you could reduce the Release 12 upgrade time
by:
•Exporting statistics gathered during test runs (by adsstats.sql - at same point: phase: last+63).
•Importing these statistics instead of running adsstats.sql.
However, this does complicate the upgrade. So only do it if it is expected to save a significant amount of time, and
you are confident in adopting this approach.
Note that if parallel_max_servers is set to a value much less than 2 x number of cores, you should consider
increasing parallel_max_servers before resorting to export/import.
If importing statistics is also long running, it may have a performance issue that could be resolved by gathering fixed
object and dictionary statistics prior to importing. You would normally only gather fixed object and dictionary statistics
after the Release 12 upgrade is complete (i.e. after R12.1.3 RUP or after 12.2.7 RUP). So these are additional
activities and their elapsed time should be deducted from any gains made by importing statistics.

 Export statistics using:
 FND_STATS.backup_schema_stats(schema_name => ‘ALL’, statid => '<your statid>')
 Import statistics using:
 FND_STATS.restore_schema_stats(schema_name => ‘ALL’, statid => '<your statid>')
 Two reasons you should use FND_STATS.backup_schema_stats and restore_schema_stats:
 Only FND_STATS is supported with Oracle E-Business Suite.
 FND_STATS.backup_schema_stats and restore_schema_stats will only backup and restore
Oracle E-Business Suite schemas (around 85% of objects on an Release 12 database). In
contrast, DBMS_STATS.export_database_stats and import_database_stats will export/import
all schema statistics and also gather fixed object, dictionary and system statistics. So the
workload will be considerably less if you use FND_STATS.

 Outside-the-box optimizations – Requires Testing/Resources**
 Long running mv related xdf’s (“en” phases)
 Cleanup and truncate large MV logs (requires MV complete refresh)
 Look more closely at long running jobs that you suspect may not be required for your
system
 Resolving Long Running jobs

 Thousands of jobs and customer product/data/setup configurations
 Some of the heavy lifting work may not be required for a specific site
 Go To My Oracle Support- Search on the exact job name
 If fix avail it may be in the Preinstall note
 If fix is not available
 Check with Oracle Support to validate & Log Bug
 A fix may be available for your case or Dev will create one
 Your fix then could get added in the Preinstall note or next CUP for others

Testing
&
Troubleshooting

E-Business Suite Analyzers  Utilize Proactively to prevent,
or resolve issues
 Use in SR Troubleshooting
 Scripts on some top E-
~60
Business Suite problem
Product
areas
Analyzers
 Scripts are Query based no
change to data
 Standalone or Concurrent
Request Execution setup
 HTML Output
 Empower your functional users
 Utilize when Solving SR’s
 Bundle Menu Tool now Avail!

Take provisioning and maintenance of EBS Support Analyzers to the next level!
Bundle Benefits:
• Easy to install and obtain all available EBS Support Analyzers in Index [Doc ID 1545562.1]
• Convenient method for DBA/SYSADMIN to execute analyzers from a single menu
• Provides a Maintenance methodology for obtaining new and updated analyzers
• Quickly load and register Analyzers as Concurrent Programs
• Menu option shows Analyzers installed as concurrent programs and versions
• Ability to remove and uninstall from the menu

Oracle Confidential – 95
Main Menu: Analyzer Bundle Menu Tool- Doc id 1939637.1
Main Menu Options
1-5 – Select product to execute Analyzer
or set up as Concurrent Program
L – Select to Load All Analyzers as

Concurrent Programs
C – Check for Analyzer Bundle updates
S – Display List of Analyzers currently
installed as Concurrent Programs
U – Remove and Uninstall Analyzers
H – Help Menu
X – Exit the Menu Tool

96
R12 PO Approval Analyzer Diagnostic Script
Doc - 1525670.1
 Proactive checks with recommendations to prevent
known issues
 Critical patches that have not been applied
 Invalid objects along with error message and
solutions for common errors
 Validations of setup and database conditions,
e.g., Max extents and space issues
 Multiple document checks that detect problems and
find solutions for a range of documents
 Data corruption issues
 Workflow errors with generic messages i.e.
document manager errors
 Documents with workflows in error that cannot be
progressed via the application
 Single document check prints all the information
needed to troubleshoot the problem with the approval
process including
 Table dumps
 Workflow activity
 Data integrity issues
 The approval list

ASCP Performance Analyzer
Doc - 1554183.1
Script for Performance Monitoring
 Immediate Analysis and Output of ASCP Environment
 Identifies Entity Data Volume
 Identifies Database parameter and recommendations
 Identifies planning process programs run time trend
 Easy to add tool for regular maintenance
 Execute analysis anytime to compare trending from past outputs

R12 Period Close Helper – Doc 1489381.1
Diagnostic to Validate Data Before Period Close
 Consolidates list of items that will stop period close
 Review parameters and transactions to correct
 Helpful information to resolve targeted transactions
 Functional End Users can execute
 Execute as Standalone or as Concurrent Request

R12 Payables Trial Balance Helper
Doc - 1553507.1
Smoother Reconciliation Experience
 Structured self help feature
 Output has highlighted solutions
for fast turn around
Avoid Last Minute Hassle
 Run anytime and clear
transactions
 Instant Check on Recommended
Patches
 RPCs have fixes for 80% of the
corruptions identified to date
No need to contact the DBA
 Both functional and technical users
can use these diagnostics
Smoother Period Close: MGD + PCA + RPC
The opportunity for a smoother month-end is within your grasp. It comprises of 3 parts:
 Diagnose and Correct Data Integrity

Issues – Doc ID: 1360390.1
AP Period
Close Analyzer  Determine and Action Period Close
Master Generic Recommended Obstacles – Doc ID: 1489381.1
(PCA)
Datafix Patch Collection
Diagnostics  Prevent Reoccurrence with Code
(RPC) Fixes – Doc ID: 1397581.1
(MGD/GDF)
TIP:
 Functional End Users
Smoother Period Close
 C –Level & Project leads
 Critical to know
R12 Internet Expenses Setup Helper
Doc 1559272.1
 Integrity Check
 Validates single or multiple OU setups
 Reduces the time needed to troubleshoot
 Shows recent setups, profiles options,
key items for OIE health and usage in
easy report
 Instant Check on Recommended Patches
 Identifies needed RPCs that have
fixes for 80% of corruption issues
 No need to contact the DBA
 Both functional and technical users can
use these diagnostics
Testing EBS
• Testing Oracle E-Business Suite
• CON6713-Testing Oracle E-Business Suite Best Practices
Oracle Application Testing
Suite (Oats)-Flow Builder
•Oracle Applications Testing Suite

•YouTube: Oracle Flow Builder Training
•YouTube: Oracle Applications Testing Suite and Flow Builder
Demonstration
•Oracle Functional Testing Suite Advanced Pack for EBS 12.2.4

Now Available LINK BLOG
•Oracle Functional Testing Suite Advanced Pack Readme for E-
Business Suite, (Doc Id: 1947643.1)
• Oracle Functional Testing Suite Advanced Pack for Oracle E-
Business Suite Readme, Release 12.1.3 (Doc ID 1905989.1)
•Oracle Functional Testing Suite Readme for E-Business Suite,
Release 12.1.3 (Doc ID 1578030.1)
Oracle Application Testing Suite
Overview
Oracle Functional Testing Suite for • Functional and Regression Testing

• Web and Oracle Application Testing Accelerators
Oracle Applications
• Oracle Flow Builder and Starter Pack
Oracle Load Testing Suite • Load and Performance Style Testing

• Web and Oracle Application Testing Accelerators
for Oracle Applications • Smart Integration with EM Diagnostics
• Test Planning, Requirements and Test Cases

Oracle Test Manager • Defects Tracking
• Reporting
105
Oracle Functional Testing Suite for Oracle Applications
Oracle Flow Builder and EBS Pre-built Test Content

Your Your
• Use Flow Builder to Generate Test Scripts Flows Data
• Start with EBS Pre-Built Test Content
• Create and Maintain Your Test Scripts EBS Pre-Built
– Add Your Flows & Data Test Content
Oracle Functional Testing Suite

for Oracle Applications
– Extend with More Components Flow Builder Generate
Framework to combine
flows and data to generate
test scripts
Record
EBS Quality Assurance Team Manually Test
OpenScript Automation
Reduced Automation Time by 60%
Record & Playback Scripts
+ Advanced Scripting
106
Oracle Flow Builder: EBS Pre-Built Test
Content
Starter Pack
For Both 12.1.3 and 12.2
2000+
3600+Components
components and
and 200+
230+ Flows across EBS
flows across EBS
• Commonly used base functionality
• For creating high level certification flows
• Broad coverage to jump start the testing
Asset
Lifecycle Financials Human Capital Logistics Manufacturing
Order
Management
Financials Procurement Management
Projects HCM
Management
Product
Asset
Order Information
Lifecycle Master Data
Management Procurement Management Projects Service
Logistics Manufacturing Management Service Management
107
Oracle Flow Builder: EBS Pre-Built Test
Content
Advanced Pack
For 12.1.3 & 12.2.5
XX product families / products across EBS
• NEW: Oracle Functional Testing Suite Advanced
Pack for Oracle E-Business Suite
• Niche products which stand alone and deep
functionality Asset Channel
Lifecycle Revenue Discrete Incentive Lease /Finance
• For creating detailed and complex test flows Management Management Manufacturing Compensation Management
• Significant number of components above Starter

Pack (70% - 90% coverage)
Process Project Property

• Oracle Functional Testing Suite Starter and Manufacturing Procurement Management Manager Service
Advanced Pack for Oracle E-Business Suite

Readme, Release 12.2.5 (Doc ID 2094528.1)
108
12.2 Troubleshooting
TROUBLESHOOTING:
•EBS Technology Codelevel Checker (ETCC) – (Doc ID: 1594274.1) Downloaded via Patch 17537119
• 12.2 - analyzes the Oracle Database Oracle Home and all middle tier Oracle Homes and warns of missing required bug fixes for upgrade.
•Script to Diagnose adop and Other AD-TXK Issues in Oracle E-Business Suite Release 12.2 (Doc ID 1901242.1)
•Rapid Install for E-Business Suite Release 12.2 (Doc ID 1378579.1) see appendix A for Rapid Install log file locations
•12.2 E-Business Suite - How To Enable FND: Debug / AF Logging When Login Is Not Possible (Doc Id: 1563168.1)
•Using Oracle Fusion Middleware Diagnostic Framework With Oracle E-Business Suite Release 12.2 (Doc Id: 1428056.1)
WEBLOGIC:
•Oracle Applications E-Business Suite 12.2 Fusion Middleware Log Files: Locate,View, and Control (Doc ID 1366187.1)
•12.2 Ebusiness Suite - Collecting Fusion Middleware Log Files (Doc ID 1362900.1)
CONFIG:
•Oracle E-Business Suite Release 12.2 Configuration in a DMZ (Doc ID 1375670.1)
•DMZ and SSL Configuration Guide for Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.2 V4 and V5 (Doc ID 1575921.1)
•11i - 12.2 Oracle Application Framework Troubleshooting Guide- (Doc ID 1496055.1)
•Oracle E-Business Suite Java APIs for Forms Troubleshooting Guide, Release 12.2 (Doc ID 1469785.1)
•Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12.2 (Doc ID 1317697.1)
Sizing & Testing Documents
Sizing:
• Database and Application Tier Sizing Guidelines from our 12.2 Install Guide
• Oracle Open World 2015 Presentation:
 Presentation Download CON6711_Barakat-Getting Optimal Performance from Oracle E-Business Suite
Testing:
• Oracle Open World 2015 Presentation:
Presentation Download CON6713 - Testing Oracle E-Business Suite: Best Practices from Oracle Development
Tuning:
• Tune performance of the core upgrade driver… See
• Oracle E-Business Suite Upgrade Guide, Release 11i to 12.1.1
• Oracle E-Business Suite Upgrade Guide Release 11i to 12.2
• Oracle E-Business Suite Upgrade Guide Release 12.0 and 12.1 to 12.2
Performance & Benchmark
Performance
• Oracle E-Business Suite Performance Guide (Doc ID 1672174.1)
• Express Diagnosis of Oracle E-Business Suite Release 12 Upgrade Performance Issues (Doc ID 1583752.1)
• Recommended Performance Fixes (Doc Id 244040.1)
 CON6711 - Getting Optimal Performance from Oracle E-Business Suite
Oracle Benchmarks
http://www.oracle.com/us/solutions/performance-scalability/index.html
• Oracle Applications Benchmark
http://www.oracle.com/us/solutions/benchmark/apps-benchmark/index.html
• Oracle R12 E-Business Standard Benchmark Overview
http://www.oracle.com/us/solutions/benchmark/apps-benchmark/ebs-standard-benchmark-overview-192676.html
Support
Call - Outs
Globalizations
 E-Business Suite Globalization Center Doc ID: 973912.1
 Understanding Oracle E-Business Suite Localizations Doc ID: 1478018.1
 NLS Frequently Asked Questions Doc ID 399789.1
 Globalization Guide for Oracle Applications Release 12 Doc ID 393861.1
 Internationalization Update Notes for Release 12 Doc ID: 393320.1
 Oracle Applications Documentation Resources, Release 12 Doc ID: 394692.1
 Oracle Applications NLS Release Notes Doc ID: 405294.1
 Oracle Database Globalization Support Guide
 Oracle Application Server Globalization Support Guide
 Oracle Applications Release 12 Translation Scope and Availability Doc ID 405992.1
 Database NLS Frequently Asked Questions Doc ID 60134.1
 Oracle Release 12 Documentation Library
 Oracle E-Business Suite Release 12 Technology Stack Documentation Roadmap Doc ID 380482.1
 Open World 2014 - Oracle E-Business Suite Internationalization and Multilingual Features
 Training: Oracle E-Business Suite Internationalization and Multilingual Features (Presentation)

 http://oukc.oracle.com/static05/opn/login/?t=checkusercookies&r=-1&c=1125655606
 Internationalization Development, discussed internationalization and MLS considerations when running a
global single instance of Oracle E-Business Suite. Maher discussed unicode support, multilingual support,
calendars, and other important internationalization and multilingual support issue. (February 2012)
Reviewing Your Financials Setups – from 11.5
Even in the Upgrade Case, Plan on Reviewing Your Financials Setups
• Some setups done separately in 11i modules are

centralized in R12
• Validate that new centralized setups reflect consistent tax
and
UNIFIED BANKaccounting
ACCOUNT MODEL treatments that ENGINE
CENTRALIZED PAYMENTS you expectONE GLOBAL TAX ENGINE
Funds Capture and Disbursement
• Centrally managed rules
• Consistent tax services
Legal Entity Tax Determination Process
Operating Units Regime Applicable Tax Status, Taxable Tax
Payments Taxes Rate Basis Calculation
Engine
Reviewing Your Financials Setups-from 11.5
Lots of Docs to Help You
• Understand upgrade impacts on 11i setups
– Oracle Financials & Procurement Functional Upgrade Guide
– “R12 Upgrade Considerations by Product” (Doc 889733.1)
– Accounting Setup Manager Pre-Update Diagnosis Report (Doc
961742.1)
• Understand new R12 Financials capabilities
– Oracle Financials Concepts Guide
– Oracle Financials product-specific implementation guides
– Transfer of Information (TOI) online training (Docs 988725.1 and
807319.1)
Financial Considerations 12 upgrade from 11.5
 Financials
 Before upgrade –Prepare data in 11i Instance
 Note 1571256.1 PRE-Upgrade GDF Diagnostic to Validate Data Related to Invoices, Payments,
Accounting and Suppliers
 Address issues identified by the script
 Preinstall Patches:
 Oracle E-Business Suite Consolidated Upgrade Patch 2 (CUP2) for R12.1.1 Doc ID 798258.1
 Oracle E-Business Suite Consolidated Upgrade Patch 8 (CUP8) for 12.2.0 Doc Id: 1320300.1
 Oracle E-Business Suite Pre-install Patches Report [Video] Doc ID 1448102.1
 Post Upgrade: Note 1460241.1 POST-Upgrade GDF Diagnostic to Validate Data Related to Invoices,
Payments, Accounting and Suppliers” and address issues it identifies
 Post Upgrade:
 Recommended Patches for EBS – PatchWizard utility in EBS will identify these
 Note: 954704.1 Payables, Payments, SLA and EBTax ones (If using other financial products apply
their RPCs as well)
 Oracle 12.1.3+ E-Business Suite Recommended Patch Collection 5 [RPC5] (Doc ID 2152266.1)
HCM Considerations 12 Upgrade
 HCM
 Known HRMS Issues for 12.1.1 Maintenance Pack (Doc ID 849871.1)
 General documents;
 Shared HR' Environments What Types of Records Would You Expect to See in HR tables ? (Doc ID
1075831.1)
 New Features in R12 for Shared HR / HR Foundation (Doc ID 435001.1)
 API:
 HR Foundation (Shared HR) and APIs (Doc ID 152028.1)
 Oracle HRMS Product Family Publicly Callable Business Process APIs (A Reference Consolidation) (Doc ID
216838.1)
 List of Publicly Callable Business Process APIs:
 Oracle Human Resources Management Systems Configuring, Reporting, and System Administration Guide,
Release 11i, June 2006. Part No. A95418-03 Page 3-148
 Oracle Human Resources Management Systems Configuring, Reporting, and System Administration Guide,
Release 12, April 2007. Part No. B31614-05
 Which APIs Can Use for Shared HR on R12 (Doc ID 1167113.1)
 Troubleshooting Guide for How to Use an HRMS API (Doc ID 152254.1)
 Oracle HRMS Implementation Guide E13513-04 - http://docs.oracle.com/cd/B53825_06/current/acrobat/121hrmsig.pdf
Post Go-Live
NEW How to Find E-Business Suite & E-Business Suite Technology
Stack Patches (Doc ID 1633974.2)
TABBED
NAVIGATION
Patch Wizard – Doc 976188.1
 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
Period Close Advisor – Doc 335.1
 One-stop shop for period

close steps for all products
(in the order of closing)
 Complete the critical
financial reporting process
accurately
E-Business Suite Analyzers  Utilize Proactively to prevent,
or resolve issues
 Use in SR Troubleshooting
 Scripts on some top E-
~60
Business Suite problem
Product
areas
Analyzers
 Scripts are Query based no
change to data
 Standalone or Concurrent
Request Execution setup
 HTML Output
 Empower your functional users
 Utilize when Solving SR’s
 Bundle Menu Tool now Avail!

Oracle EBS
Platform
Migration
Planning &
Back to Table of Contents Downtime
Resources 12.1
 Certify
 For DB Migration Options Certified with
EBS releases
 Doc 1377213.1 Oracle E-Business Suite
Upgrade & Platform Migration
 Doc 790942.1 Oracle Applications
Documentation Resources, Release 12.1
 Doc 406982.1 Cloning R12 with Rapid
Clone
 Doc 438086.1 Platform Migration with R12
 EBS Technology Blog
(http://blogs.oracle.com/stevenChan)
Resources 12.2
 Certify
 For DB Migration Options Certified with
EBS releases
Upgrade & Platform Migration
Release 12.2 Information Center –
Documentation.
 Cloning Oracle E-Business Suite Release
12.2 with Rapid Clone (Doc ID 1383621.1)
 Doc 2048954.1 Platform Migration 12.2
 EBS Technology Blog
(http://blogs.oracle.com/stevenChan)
Plan, Prepare and Test
 As with most planned database maintenance activities, the probability of

a successful platform migration is very high when a well-defined
migration plan is validated in a suitable test environment before
migrating the production database. The majority of time spent on a
platform migration project should be spent in the planning, preparation,
and testing phases.
 Optimizing the platform migration process is all about making the right
choices at the planning stage and verifying these choices with a test
environment before production migration.
Plan for Down Time
 When combined with a platform migration, the business requirement of minimizing downtimes can
often be difficult to meet.
 Platform migrations may be considered separately for the application and database tiers, or for both
tiers together. In either case, it is critical to understand that the migrations are separate processes
that can be thought of logically as such. This is especially crucial in light of potentially reducing
downtimes by breaking them out into separate discrete events which may have different
considerations for users and administrators.
 Performing a Database migration to a new platform first, if being considered as part of an EBS
upgrade, is recommended as customers would typically be able to perform this in a separate earlier
downtime
 Regardless of whether this migration is done in a separate earlier downtime or as part of a single
downtime, performance gains would be expected during the upgrade of the Applications to R12
since it will be running on newer and faster hardware and latest database version.
Oracle EBS
Platform
Migration
Database
Back to Table of Contents Migration
Database Migrations
 One important consideration – the “endian-ness” of the platform, i.e. the
byte order storage.
Big Endian Platforms Little Endian Platforms
• Oracle Solaris on SPARC • Linux x86 and x86-64
• HP-UX Itanium and PA RISC • Oracle Solaris on x86-64
• IBM AIX on POWER Systems • HP Tru64 and OpenVMS Alpha
• IBM: Linux on System z • Linux Itanium
• IBM: Linux on Power Systems • MS Windows Server x86/x64/Itanium
An upgrade of EBS combined with a platform migration could take the form of:
(a) an Operating System upgrade on the same platform (for example, upgrading
from Oracle Linux 5 to Oracle Linux 6)
(b) a migration across platforms of the same endian format
(c) a migration across platforms of different endian formats.
Operating System upgrade on the same platform
Process
 When considering a newer operating system as the target (for example, a newer version of
Oracle Linux or Solaris), users can simply use the Rapid Clone technique of essentially
copying datafiles over to a new machine.
 Reference Note: Cloning Oracle Applications Release 12 with Rapid Clone' - Doc 406982.1
OR
 Reference Document: Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc
ID 1383621.1)
 Most of the time is spent in copying database files and middle tier tech stacks
Tips and Recommendations

 Parallel copy with compression can be used to optimize the time consuming step of copying
dbf files.
Migration to a new platform of the same endian format
Process
 When the target of a database migration is of the same endian format, we recommend the use of
the database migration process called Transportable Database (TDB) to migrate the database.
While export/import (datapump) might be used, TDB represents the quickest way to migrate the
database and is recommended.
 Reference Notes:
11i : 'Using Transportable Database to migrate Oracle E-Business Suite Release 11i Using Oracle
Database 10g Release 2 or 11g Enterprise Edition' Doc 729309.1
R12 : 'Using Transportable Database to migrate Oracle E-Business Suite R12 using Oracle
Database 10g Release 2 or 11g Enterprise Edition' Doc 734763.1
R12 : 'Using Transportable Database to migrate Oracle E-Business Suite Release 12.2 Using
Oracle Database 11g Release 2 Enterprise Edition' Doc 2011169.1
R12 : Using Transportable Tablespaces to Migrate Oracle EBS Release 12.2 Using Oracle
Database 12.1.0' Doc 2157661.1
 The source (export from) ORACLE_HOME directory must be Oracle Database

10g Release 2 (10.2.0), 11g Release 1 (11.1.0), 11g Release 2 (11.2.0), 12c
Release 12.1.0.2. The target Oracle home version (including patch set version)
must match the source.
 You may choose to convert the datafiles of the database being transported on
the destination platform (target system conversion) instead of the source
platform. Reasons for doing this include:
 Avoiding any performance overhead on the source host due to the
conversion process.
 Distributing a database from one source system to multiple recipients on
several different platforms.
 Only data files that contain undo data require conversion. However, the
default behavior of CONVERT DATABASE is to perform a conversion on all
data files. Eliminating unnecessary data file conversion, which is possible with
target system conversion, can significantly reduce platform migration time.
See Doc 732053.1 for details.
 Use all available computer resources to do the CONVERT DATAFILE

operations by running them in parallel. RMAN allows the PARALLEL option to
be specified with the CONVERT DATABASE command.
 Export/import has been certified for every version of EBS and the database -
the use of export/import for EBS also supports the export of data from earlier
DB versions while importing to later versions. This may save some time in
combining an upgrade of the Database with a migration.
 For larger databases (>1TB) however, the use of export/import can be an

extremely slow process
 We can modify the data pump parameter file to utilize parallel processing.
By properly having multiple dump file and specifying enabling the parallel
import and export

Here is a general guideline for what should be considered when using the PARALLEL parameter:
 Set the degree of parallelism to two times the number of CPUs, then tune from there.
 For Data Pump Export, the PARALLEL parameter value should be less than or equal to the
number of dump files.
 For Data Pump Import, the PARALLEL parameter value should not be much larger than the
number of files in the dump file set.
 A PARALLEL greater than one is only available in Enterprise Edition
 To specify multiple dump files with a specific sizing criteria you can use the following in the
parameter file
DUMPFILE=expdir:exp%U.dmp
FILESIZE=2G
Migration to a new platform of different endian formats
(Export/Import (Datapump))
Process
 Export/import using datapump has traditionally been used to perform Database migrations across
platforms - this represents a full logical export of the database to a dump file which is then moved to
the target machine before being imported
11i/10gR2 :'Export/Import Process for Oracle Applications Release 11i Database Instances Using
Oracle Database 10g Release 2' - Doc 362205.1
11i/11gR1 and 11i/11gR2 : 'Export/Import Process for Oracle E-Business Suite Release 11i
Database Instances Using Oracle Database 11g Release 1 or 2' - Doc 557738.1
R12/10gR2 : 'Export/Import Process for Oracle E-Business Suite Release 12 Database Instances
Using Oracle Database 10g Release 2' - Doc 454616.1
R12/11gR1 and R12/11gR2 : 'Export/Import Process for Oracle E-Business Suite Release 12
Database Instances Using Oracle Database 11g Release 1 or 11g Release 2' - Doc 741818.1
Migration to a new platform of different endian formats
(Transportable Tablespaces)
Process
 The alternative for migrating to a target platform of a different endian format is a more
recently certified technique of migration called Transportable Tablespaces (TTS)
11i/10gR2 : 'Using Transportable Tablespaces to migrate Oracle Applications Release

11i Using Oracle Database 10g Release 2 Enterprise Edition' - Doc 454574.1
11i/11gR2 : 'Using Transportable Tablespaces to migrate Oracle Applications Release

11i Using Oracle Database 11g Release 2 Enterprise Edition' - Doc 1366265.1
R12/11gR2 : 'Using Transportable Tablespaces to migrate Oracle Applications Release

12 Using Oracle Database 11g Release 2 Enterprise Edition' - Doc 1311487.1
Migration to a new platform of the different endian format

 The RMAN DB file conversion step will take the longest amount of time
out of the entire migration. So we need to focus on optimizing this step
by doing the following:
 Create multiple RMAN conversion scripts each covering a subset of

the database files (20 files per scripts as an example)
 Use all available computer resources to do the CONVERT DATAFILE

operations by running them in parallel. RMAN allows the PARALLEL
option to be specified with the CONVERT DATABASE command.
Oracle EBS
Platform
Migration
Application
Back to Table of Contents Tier
Application Tier Migrations
 11i to R12.1 or R12.2 Upgrades
 Prep the DB for upgrade, install a R12 upgrade file system, run upgrade driver.
 Discards existing 11i application tier
 Upgrade and migration happens in one step by running the R12 Rapid Install on the target
machine to put down R12 upgrade file system.
 R12 Upgrades using Release Update Packs (RUP)
 A RUP is used to upgrade an existing R12 system
 Applied on an existing R12 application tier and does not use Rapid Install, so an upgrade
platform migration and a RUP platform migration are two separate processes.
 Apply the RUP, then perform the app tier platform migration using Rapid Clone (or the Platform
Migration Utility if migrating across platforms) or vice versa.
 If you are not upgrading into a new platform, do RUP, Then migrate to new platform using
Application Tier Platform Migration with Oracle E-Business Suite Release 12 Doc 438086.1 for
12.1 or Application Tier Platform Migration with Oracle E-Business Suite Release 12.2 Doc
2048954.1
Appendix
Upgrade
Back to Table of Contents By Request
Upgrade By Request- for 11.5 to 12.x
Performance – Upgrade Guide: (UG Appendix and Doc 604893.1)
• Oracle® E-Business Suite Upgrade Guide Release 11i to 12.1.1 Part No. E16342-04
 Oracle® E-Business Suite Upgrade Guide Release 11i to 12.2 Part No. E48834-03
 Option to omit the upgrade of historical data from the initial upgrade process (critical downtime window)
 Historical data can be upgraded anytime when system is up
 Implementation is a two step process:
1. Set range of historical data to be upgraded before R12.1 upgrade and run the pre-upgrade concurrent
program
2. Run the post-upgrade concurrent program (as needed for additional historical data)
 Review Upgrade By Request Appendix in R12 Upgrade Manuals for more details
 Customer Relationship Management
 Financials and Procurement (example next slides subledger accounting)
 Supply Chain Management
 Projects
Example: Subledger Accounting
Upgrade Modes
 Full upgrade: All historical accounting data is upgraded

 AX, Loans, Property Manager
 Partial upgrade: Some historical data is upgraded
 AP, AR, Assets, Costing, Projects
 You determine the range of periods
 SLA Upgrade Historical Subledger Transaction Program is available post-
upgrade
 No Upgrade: No historical accounting data is upgraded
 Cash Management, Federal/Public Sector, OPM
Upgrade by Request
Use Subledger Accounting “Upgrade by Request” - (UG Appendix G and Doc 604893.1)
 Limit historical accounting data upgraded during critical downtime
 using SLA Pre-Upgrade Program
 You can specify range of periods to upgrade; default is current fiscal year or
minimum of 6 periods
 Some SLA functionality relies on availability of previous accounting data
Option to run SLA Post-Upgrade Program for more historical data
See “FAQ for the SLA Upgrade: SLA Pre-Upgrade, Post-Upgrade, and Hot Patch”,
Doc 604893.1
Upgrade By Request
1. Pre-Upgrade
– Determine how much accounting data you need online
– Submit for All Ledgers as of a Start Date
2. Downtime Upgrade
– Upgrades current fiscal year’s data
– Based on the upgrade date
• …in first half of fiscal year, upgrade will go back to prior fiscal year to upgrade
minimum of 6 periods
• …in second half of fiscal year, upgrade processes data in all periods of
current fiscal year
3. SLA Upgrade Historic Subledger Transactions Program
– Submit for each Ledger and Period
– Not a substitute for downtime upgrade
Upgrade by Request

EBS Upgrade Reducing Downtime Doc Id 1578187 1 V15

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EBS Upgrade Reducing Downtime Doc Id 1578187 1 V15

Uploaded by

Copyright:

Available Formats

1 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Safe Harbor Statement

The following is intended to outline our general product direction.

It is not a commitment to deliver any material, code, or

4 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Open World 2016 Development Presentations

5 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 The items in the document are considerations. The

 When to use this document

8 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

9 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

10 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

11 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

12 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

13 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

14 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

15 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

16 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Back to Table of Contents

17 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

18 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

19 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Why Upgrade Planning and Executing Upgrade

 EBS Youtube Channel  Proactive Support Tools (aka 432.1)

20 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

• Oracle Consulting (OCS) : Upgrade assessments; upgrades & implementation projects

21 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

22 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Release 12.1 Reducing downtime:

 Oracle E-Business Suite Release 12.2.7 Readme (Doc ID 2230783.1)

24 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

EBS Technology Blog

26 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Verify certification of any

28 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

29 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

30 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

31 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 One Consolidated patch across product families

 Recommended Patch Collection 5 (RPC5) includes:

32 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Back to Table of Contents

33 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

34 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

*Check for latest patches

35 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

36 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

37 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

38 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

39 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

40 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

photo photo photo

© 2011 Oracle Corporation – Proprietary and Confidential

Back to Table of Contents

42 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

43 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

44 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

45 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

• (DOC ID 752322.1) : Reducing Oracle E-Business Suite Data Footprint

46 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 Proactive script that reviews the current Workflow Footprint

48 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

 Payroll Analyzer  AutoAccounting Analyzer  IB Analyzer

49 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.