New Generation Consultants, Inc

Upgrading to Oracle EBS R12Architecture and Technology

Amarendra Nettem

Feb 27th, 2009

Introducing New Generation Consultantswww.newgenusa.com

� Oracle Certified Partner

– Founded 2001

– HQ in Des Plaines; branch in Chennai

– 6 Practice Areas

� Data and Process Integration

� Decision Support� Decision Support

� Enterprise Applications/OBAs

� Infrastructure Design, Deployment, Support

� Managed Services

� Education and Training

� Drawing at end of today’s presentation!

2

Upgrading to Oracle EBS R12

Architecture and Technology

3

Agenda

� Oracle R12 Technology Stack Overview

�Changes from Oracle EBS R11i to R12

�New Features

� Analysis and Planning

�Supported Application Migration Paths

�Custom components requiring changes�Custom components requiring changes

� Best Practices

� Questions and Answers

4

Oracle R12 Technology StackOracle R12 Technology Stack

5

Technology Stack - Release 11i

Application

JSP

ServletEngine(Jserv)

We

b L

iste

ne

r

Client

9i or 10g

Database

9iAS 1.0.2.2JInitiator

User Interface Application logic Database logic

JSP

Forms

Reports

BC4JW

eb

Lis

ten

er

UIX

99iiR2 &R2 &

10g (Optional)10g (Optional)

iAS 1.0.2.2.2iAS 1.0.2.2.2

Technology Stack – Release 12

Application

JSP

OC4J

We

b L

iste

ne

r

Client

9i or 10g

Database

9iAS 1.0.2.2

User Interface Application logic Database logic

JSP

Forms

Reports

BC4JW

eb

Lis

ten

er

UIX

Technology Stack - Changes from EBS 11i to 12

Component 11.5.10 R12 (12.0.3)

Database Server 9.2.0.5 10.2.0.3

Web Server iAS 1.0.2.2.2 AS 10g 10.1.3

Java Servlet

Container

Jserv OC4J

Container

Forms Server Developer 6i AS 10g 10.1.2

Java Development

Kit

JDK 1.4 - 1.4.2 JDK 5.0

Client Viewer Jinitiator Sun JRE

Technology Stack - Changes from EBS 11i to 12

Technology Stack - Changes from EBS 11i to 12

Technology Stack - Changes from EBS 11i to 12

Oracle R11i

Oracle R12

Instance Home Advantages

� Clear distinction between the shared file system and the

file system unique to an instance� Ability to share code (Apps, technology stack) among multiple nodes and

even instances (Dev,Test, Production)

� Enables split ownership of applications and technology stack file systems

� Improves code safety by making shared file system read-only while not

patchingpatching

� Configuration and log files are co-located� Easier collection of instance state

� Ability to use network or local storage for various file

system portions� Minimize disk usage and maximize performance

New Features in 12.1

� AutoConfig can be run in parallel on different nodes of Apps

� Technology Stack Inventory Validation Report

� Shared Application Tier File System Amongst Multiple EBS Instances

� Record History is now available for OA Framework based pages� Record History is now available for OA Framework based pages

� Concurrent requests and managers can now be directed to a specific

database instance or node

Analysis and PlanningAnalysis and Planning

14

Why Upgrade?

• Supportability

• Stability

• Improved performance

• New features

• New Modules

• New features &

functionality

• New requirements

IT Drivers Business Drivers

• New features

• Maintenance cost

• Out of box use

• Customizations

• New requirements

• Re-engineer

• Design Improvements

15

EBS Support

Release GA date Premier

Support Ends

Extended

Support Ends

Sustaining

Support

Ends

11.5.9 Jun 2003 Jun 2008 Not Offered Indefinite

11.5.10 Nov 2004 Nov 2010 Nov 2013 Indefinite

12 Jan 2007 Jan 2012 Jan 2015 Indefinite

R12 features

� Think Globally � Work Globally� Manage Globally� Reduced pop-ups & duplicate screens� Reduced steps to complete key tasks

� Improved look, feel and visual style� Improved look, feel and visual style� Increased personalization capabilities

� New functionality in the Financials area� The best in technology:10gR2 & 10gAS

Analysis and Planning – Application Migration Path

Upgrade Path

� Applications R11.5.6 and below requires to first upgrade to

R11.5.10.2/10gR2

� Applications R11.5.7 and up can be directly upgraded to R12

� Database in all releases must have been upgraded to 10gR2

(11.5.9.2/11.5.10.2) or should be done during upgrade to R12

(11.5.9.1/11.5.10.1 and below)

Technology Improvements

� AutoPatch replaces AutoUpgrade tool

�AD parallel infrastructure improvements for work distribution of Large Table

Update

� Inclusion of Gather Auto Stats job in R12 Upgrade driver itself to keep

statistics up-to-date after the upgrade

� sqlplus_parallel directive to eliminate the contention between jobs� sqlplus_parallel directive to eliminate the contention between jobs

executing parallel query

� Optimizer dynamic sampling (for objects with no statistics)

� Converted non-critical jobs as concurrent manager requests to reduce

overall downtime

� R12 unified upgrade driver provides an option to defer compilation of

PL/SQL packages during creation

Overview – Maintenance Wizard

� This tool will guide you through upgrade of Oracle Applications technology stack and

products from Release 11i versions to Release 12

� Currently, the Maintenance Wizard performs the following types of upgrades:

- Upgrades to 11i via the Upgrade Assistant for Release 11.5.10 product. This includes: 10.7 NCA to 11.5.10.2 11.0.3 to 11.5.10.2

- Upgrades within 11i via the Maintenance Pack Assistant for 11.5.10 product. This includes: 11.5.3 or higher to 11.5.10.2

- Upgrades to Release 12 via the Upgrade Assistant for Release 12 product. This includes: - Upgrades to Release 12 via the Upgrade Assistant for Release 12 product. This includes: 11.5.8 or higher to 12.0.4

- Release Update Pack upgrades via the R12 RUP patches. This includes: 12.0.0 or higher to 12.0.6

- RDBMS upgrades for Applications customers via the Applications Database UpgradeAssistant 10g and 11g products. This includes:

8i to 10.2.0.3 9i to 10.2.0.3 9.2.0.8 to 11.1 10.1 or 10.2 to 11.1

Overview – Upgrade by Request

� Option to additionally upgrade historical data that has not been upgraded during the initial upgrade process

� Historical data can be upgraded anytime when system is up or down

� Following products historical data can be upgraded at a later date

- Financials and Procurement

- Projects

- Supply Chain Management

- CRM

Analysis and Planning – Pre Upgrade Tasks

Apply 11i.AD.I

Run TUMS Utility

Identify & Prepare Upgrade

Plan for Customizations

Review Size of the

Table Spaces

Run AD Preparation

Scripts

Gather Schema

Statistics for CBO

Backup the

database

Plan for Customizations

Convert to Multiple

Organization Architecture

Convert Oracle Alert E-mail

processing to workflow

notification mailer

Conditionally complete

product specific Pre-

Upgrade Steps

Run Rapid Install for

Release 12

Migrate or

Upgrade the

database to 10G

Release 2Drop Event Alert Triggers

in Custom Schemas

Disable AOL Audit Trail

Apply R12 AD Mini Pack

Run the Upgrade Patch Driver

(u6394500.drv)

Run the NLS Patch Driver

Analysis and Planning – Upgrade Tasks

Shutdown App tier listener and

Conc. Mgrs

Migrate the database to 10gR2

Update init.ora parameters

Backup the database

Disable custom triggers,

constraints and indexes

Drop the MRC Schema

Run the NLS Patch Driver

Disable the Maintenance Mode

Enable the Maintenance Mode

Reset init.ora parameters

Backup Oracle Applications

Reset Oracle Schema Passwords

Configure and Restart both, DB

and Apps Server Processes

Reapply Customizations

Migrate Custom Forms, Reports etc

Migrate Existing Objects to OATM

Analysis and Planning – Post Upgrade Tasks

Verify Completion of Concurrent

Programs

Resize the database

Install Online Help

Test, Test and Test the Applications

Integrate custom objects &

schemas

Re-enable custom triggers,

constraints & indexes

Custom Components requiring change

�Mod_plsql� Apps R12 no longer uses (disables) mod_plsql. Web pages are

migrated to OAF

�Oracle Reports Server� Oracle Graphics is no longer present in Application Server. Reports

which rely on it will need to be modified and we recommend using XML

Publisher and OAFPublisher and OAF

�Oracle Graphics Integration with Oracle Server� Convert the Oracle graphics integrated with Oracle forms to OAF.

Oracle Forms is not a part of Fusion technology stack

�Oracle Applications Framework pages� Migrate OAF present in AK repository to MDS.

Best PracticesBest Practices

27

� Involve Right People

� Review appropriate documentation to gather information

on upgrade process and tools required

� Plan to run multiple test upgrades

� Plan to test key features

Best Practices - 1

� Purge or archive historical data

28

� Use hardware that closely matches with that of

Production during Test upgrade

� Use TUMS to eliminate tasks that are not relevant for

your system

� Use Shared file system for Multi-node

� Use Distributed AD for Multi-node

Best Practices - 2

� Use Distributed AD for Multi-node

� Estimate tablespace sizes for Test upgrade

29

� Modify the following parameters for the duration of the upgrade.

Performance of some upgrade scripts can be significantly improved by

doing this:

� db_file_multiblock_read_count (do not set -- remove)

� db_file_optimizer_read_count (do not set – remove)

� job_queue_processes

� parallel_max_servers

� pga_aggregate_target

� sga_target

Best Practices - 3

� sga_target

� log_buffer

� recyclebin

� db_block_checking

30

Perform the following tasks in advance to reduce extended downtime:

� Convert to Multi Org

� Convert to OATM

� Purge workflow related tables

� Upgrade database to 10.2.0.3

Best Practices - 4

31

� Perform the following key tasks to substantially reduce

the downtime during your upgrade:

�Functional tasks listed in Reducing downtime section

- (Appendix E) in R12 Upgrade manual

�“Upgrade by Request” section

- (Appendix G) in R12 Upgrade manual

Best Practices - 5

- (Appendix G) in R12 Upgrade manual

32

� Gather statistics before your upgrade using Gather schema statistics concurrent program

� Build Master APPL_TOP from Test upgrades

� Record timing for each step during Test upgrade

� Make sure you have good backup before both the R12 and database upgrades

� Add PL/SQL no compile option in R12 upgrade driver to

Best Practices - 6

� Add PL/SQL no compile option in R12 upgrade driver to save time during upgrade

� Choose proper batch size and number of workers for AutoPatch during upgrade

� Isolate post upgrade concurrent programs to a separate manager queue

33

� NewGen Client

�Upgraded from 11.5.9 to 12.0.4

�Database size : 1.4 TB

�Purged close to 400 GB of temp data

�1st test upgrade : 72 hrs

Recent Upgrade Experience

�1st test upgrade : 72 hrs

�2nd test upgrade: 40 hrs

�3rd test upgrade: 19 hrs

�4th test upgrade : ??

34

35

Thanks for Supporting NCOAUG

� For more information contact:

– Eugene Breger847-331-5554gbreger@newgenusa.com

EMPOWER Your Business

– 2400 E Devon Avenue

Suite 266

Des Plaines, IL 6001836