1 copyright © 2011, oracle and/or its affiliates. all ... apps_upgrade_bes… · oracle...


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.

Safe Harbor Statement


3 Copyright © 2011, Oracle and/or its affiliates. All rights

reserved.

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.


Best Practices for Upgrading E-Business Suite to 12.1.3

Kandasamy Nainamalai ([email protected])

Senior Principal Support Engineer - Applications Technology Group


Program Agenda

• Why Upgrade to 12.1.3

• Value Proposition

• Tools / Resource

• R12.1.3 Upgrade Paths

• Best Practices

• 12.1 - Live Customers

• Customer Experiences

• Q&A


Why Upgrade to 12.1.3

• New functionality

• Changes in business requirements

• Release 12 provides upgrade path to Fusion

Applications

• Support

– Premier Support for 11.5.10 ended in November 2010

– Extended Support will end November, 2013


Value Proposition Financials Release 12


Value Proposition Global Financial Architecture


Value Proposition Manufacturing

• Oracle Contract Lifecycle Management for Public Sector (CLM) – to help public sector agencies proactively manage their procurement and acquisition activities

– Refer Doc ID 1194414.1 for more information

• Oracle Landed Cost Management (LCM) – To Calculate the landed cost that the buyer has incurred in purchasing goods and items

– Refer Doc ID 781061.1 for more information.

• Oracle Supplier Lifecycle Management (SLM) – A Tool to manage suppliers throughout the lifecycle of their relationship from initial supplier

discovery, through qualification and on boarding, to ongoing maintenance, and possible

obsolescence.

– Refer Doc ID 1182519.1 for more information


Value Proposition CRM

• Trade Management - Price Protection

• iStore

– One page checkout for B2C

– Product comparison

– Product detail pop-up (This avoids customization)

• Quoting - User defined QA Check


Value Proposition HCM

• Oracle HRMS (India)

– India Reconciliation of EFT Payments.

• Oracle Human Resources

– Multi-Tenancy for Business Process Outsourcing Vendors

• Oracle Self Service Human Resources (SSHR)

– Terminations – Reverse, Voluntary and Secondary Assignments


Value Proposition Technology

• Tech Stack Upgrade

– Performance

• 11g R2 Database

• 10gAS - OC4J Container - JVM

– Intergration

• Integrated SOA Gateway (SOA Provider)

• Service Invocation Framework (SOA Consumer)


Upgrade Tools & Resources Upgrade Lifecycle Advisors

• Different Advisor for each product

• Consistent layout

• Consistent phases

• Content differs for each product

• Multimedia offerings.

• No actual upgrade activities performed by advisor.

– Oracle Support Lifecycle Advisors (Doc ID 250.1)


Upgrade Tools & Resources Upgrade Lifecycle Advisors


Upgrade Tools & Resources EBS Data Model Comparison Report


Upgrade Tools & Resources EBS ATG Seed Data Comparison Report


Upgrade Tools & Resources Maintenance Wizard


Application

Upgrade

Database

Upgrade

No

Database

upgrade

Database

EBS

<= 11.5.8 customer must upgrade to 11.5.10.2

R12.1.3 Upgrade Paths


ATG - Best Practices

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/ATG RUPs on

11i/R12.0 and once on R12.1

High priority patches and Consolidated Patches.

Review “Known-issues” sections from Life cycle Advisor


Upgrade Best Practices

Patch merging and sequencing

Merge patches

Merge NLS patches per language. Apply NLS patches as “hot” patches

Perform uptime maintenance when possible e.g. hot patching of iHelp or

NLS patches, upload patch history

HRGLOBAL step before NLS ( Document 145837.1 & 414434.1 )

Stage patches locally accessible by mid-tier machines instead of on nfs

mounted or remote servers



Adpatch options and other reporting tools

Use applicable adpatch options to reduce downtime and track key upgrade

aspects using in-built tools

Use non-interactive patching

Use adpatch options such as nogenform, nogenrep, nocompile jsp,

noautoconfig, novalidate (1078973.1)

Use optimal values for batch size and #workers

Use OAM reports and Patch Wizard functionality to track patch timing, files

applied, functionality patched, impacted customized files etc. (976188.1)



Downtime reduction procedures

Use “Shared APPL_TOP” with “Distributed AD”

No need to apply the same patch on multiple tiers

Distributed AD adds to the degree of parallelism by distributing AD workers across

application tier nodes and improves D/G portion of the patch driver.

Use “Staged APPL_TOP”

Saves time to patch the file system (C/G portion) by using a patched up copy of

production instance file system

Use in 11i => R12.1 upgrade to avoid applying NLS C/G portion

Can use for R12.0.X => R12.1 upgrade and once on R12.1



For the duration of the upgrade, consider…

Disabling custom triggers and business events

Disabling auditing if enabled

If possible run in noarchivelog mode

Disabling flashback DB

Removing TDE from volume tables



Pre-upgrade activities

Identify and execute tasks that could be completed in a separate downtime

period, prior to the production upgrade

Use applicable steps mentioned in the "Downtime reduction" and “Upgrade By

Request” appendices E and G of the R12.1 upgrade guide

Upgrade RDBMS version to latest certified for the current APPS level ( 11.2.0.3 /

11.1.0.7 / 10.2.0.5 )

Convert to Oracle Applications Tablespace Model (OATM)

Compacts data, optimizes storage settings and I/O

Other planned HW or OS upgrades



Pre-upgrade activities ..

Use TUMS (“The Upgrade Manual Script”) to avoid running tasks that are not

relevant for your system

Convert to multiple organization architecture (Document 210193.1)

Drop MRC schema ( 11.5.10 and above )

Assign post upgrade jobs to specialized CM queue (by request_type, see

Document 399362.1)

Flush all the interfaces, such as Autoinvoice, Journal entry import, order import

etc..

Review and disable all debug, logging at site, responsibility, user level

Gather stats with GATHER_AUTO option for all schemas close to the start of

downtime



Pre-upgrade activities ..

Pre-create new large indexes created by upgrade (constrained to indexes on

existing columns)

Minimize historical data to be upgraded as per business requirements – “Upgrade

By Request”

Purge old and/or transient data before upgrading



Key recommended fixes

Affecting Upgrade Performance

AD-Parallel improved scalability: 8917381 (Part of 9179588 AD CUP)

Forms/reports generation regression with 11g: 8557019

General

Review document 244040.1 for latest EBS recommended performance fixes



Database tier configuration

Maximize SGA and PGA sizing

An upgrade only involves 10's of concurrent sessions

log buffer = 30 to 100 Mb

shared pool = 1 to 4 Gb

pga target = 3 to 20 Gb

buffer cache = multi Gb,

Note :- Be generous without causing excessive paging or swapping

– Set job_queue_processes = # of CPUS

– Set parallel_max_servers = 2 X CPUs



Database tier configuration …

Batch size and #workers

Batch size

10K is suitable for most installs, you can test other values from 1K up to 100K if time

allows

# Workers

Rule-of-thumb is between 1 and 1.5 x #CPUs

Monitor Below during test upgrade.

Memory utilization (no swapping/ excessive paging)

CPU utilization (scale down if at 100%)

I/O response times (scale down if averages > 20 ms)



Runtime Performance Testing Tips...

Use Automated, scripted tools

EBS Test Started Kits (Winrunner/QTP)

Bundled QA based automated scripts for EBS testing - Patch 8408886

Oracle Applications Testing Suite (Accelerators for EBS)

Web and Forms based flows

Complement with user participation tests and batch load tests with frequent and critical

jobs

References

http://blogs.oracle.com/stevenChan/2009/10/oats_ebs_certified.html

http://blogs.oracle.com/stevenChan/2009/08/evolutionary_steps_automated_testing_ebs.html

Review EBS Benchmark Publications

http://www.oracle.com/us/solutions/benchmark/apps-benchmark/results-166922.html

http://blogs.oracle.com/stevenChan/2009/08/evolutionary_steps_automated_testing_ebs.html


E-Business Suite Release 12.1 Live Customers


Customer Upgrade Snapshots 11i to 12.1

• Cisco

– Release: 11i to R12

– DB size: 600GB

– #Workers and batch size: 32, 20000

– #CPUs on DB server: 16

– Downtime reduction measures

• Distributed APPL_TOP

– #hrs for the D driver: 5.5 hrs


Customer Upgrade Snapshots 11i to 12.1

• Dell

– Release: 11i10 to R12.1.2

– DB size: 15TB , 16 node RAC Cluster


– #CPUs on DB server: 8



• Pre-create large indexes

– #hrs for the D driver: 30 hrs (latest test results)


Customer Upgrade Snapshots 12.0 to 12.1

• AT&T

– Release: 12.0+ to R12.1.2

– DB size: 10 TB


– #CPUs on DB server: 32 Processors


• Staged APPL_TOP for US and ten languages


– #hrs for the D driver: 9 hrs


Summary

• R12.1.3 Upgrade is a major one ; introducing significant changes.

– changes in the Technology Stack, Financials Accounting Engine, and Tax Engine , etc.

• Give yourself plenty of time to:

– Understand changes between 11i and R12.1

– Plan your upgrade

– Train and prepare your end users

– Conduct testing of your business configuration in R12

• Use R12.1 Customer Support Lifecycle Advisors , Note 250.1

• Finally, Review the documents and best practices that we have shared in

this presentation

R12 Upgrade Best Practice Summary


Additional References

• Oracle Support Lifecycle Advisors (Doc ID 250.1)

• E-Business Suite Product Information Center Index (Doc ID 444.1)

• E-Business Suite (EBS) Technology Stack Upgrade from 11.5.10.2 to 12.1.3 [269.1]

• E-Business Suite Financials and Projects Upgrade from 11.5.10.2 to 12.1.3 and

12.1.2 [256.1]

• E-Business Suite Human Capital Management (HCM) Guided Upgrade Path from

11.5.10.2 to 12.1.3 and 12.1.2 [257.1]

• E-Business Suite Manufacturing from 11.5.10.2 to 12.1.3 and 12.1.2 [258.1]

• 411EBS - EBS INFO: E-Business Suite Conference Highlights & Information Center

(Doc ID 411327.1)


Additional References

– R12.1 documentation roadmap (790942.1)

– “Oracle E-Business Suite Release 12.1 Info center” (806593.1)

– Database preparation guidelines for R12.1 upgrade (761570.1)

– Patching FAQs (459156.1, 225165.1)

– Using staged or shared APPL_TOP and distributed AD (734025.1,384248.1,

236469.1)

– OAM “Patch Wizard” overview and FAQ (976188.1)

– AD Command Line Options for Release R12 (1078973.1)

– Recommended Performance Fixes (244040.1)

– R12 Upgrade Sizing & Best Practices (399362.1)


My email id

[email protected]


Q&A

1 copyright © 2011, oracle and/or its affiliates. all ... apps_upgrade_bes… · oracle...

Documents