1 Copyright © 2013, Oracle and/or its affiliates. All ... · purchasing decisions. The...

DOAG Applications 2013 – Berlin

Workshop - EBS Upgrade

Best Practices & Downtime Reduction

Rüdiger Ziegler

Senior Principal Technical Support Engineer

Oracle Deutschland B.V. & Co. KG


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


Objectives

Generic Considerations

Pre-Upgrade

Downtime Reduction

Post-Upgrade

Question & Answers


Rüdiger Ziegler E-Business, Applications

Technology Group

Senior Principal Technical Support Engineer

Proactive Support Delivery

Hamburg, Germany

> 14 Years Oracle Support

> 3 Years Proactive Support


Martin Fritz E-Business, Applications

Technology Group

Principal Technical Support Engineer

Delivery Support – EBS ATG Component Tools

Hamburg, Germany

> 19 Years Oracle

> 13 Years Oracle Support


Objectives


Pre-Upgrade

Proactive Tools available

Downtime Reduction

Post-Upgrade

Question & Answers


Announced on Open World 2013 This Presentation is created on Release 12.1.3 – most areas would fit for 12.2 too Additional Information :

Doc ID 1581299.1 – Information Center 12.2 Doc ID 1585857.1 – 12.2 Technical Planning Guide Doc ID 1587195.1 – Getting started with EBS 12.2

E-Business Suite Release 12.2 is available now !

New Technology Stack in R12.2 !

https://support.oracle.com/rs?type=doc&id=1581299.1




Audience Poll

Show of hands: Sysadmin/Apps DBA/Architects/Prj Lead

Show of hands: Functional Super Users

Show of hands: C-Level, Decision Makers

Show of hands: Who is on 11i? 12.0? 12.1?

Show of hands: Non –EBS or First time EBS users?


Create A Reliable And Repeatable Process

Review and verify your products are certified

Utilize Upgrade Advisors with Best Practices

by Product, Business Process, Version and

Phase

Deploy Patch and Upgrade Plan Validations


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 ?

Customization Evaluation and plan ?

OATM converted: (Y/N) ?

Any OS / Platform Migrations planned ?

DB Size ?

Number of Instances upgrading ?

How many languages ?

Current Testing:

Estimated Downtime / Cutover window ?

How many runs completed to date ?

Last timing of upgrade run ?

TIMELINES:

GO LIVE:

Date(s) ?

UAT :

Dates ?

Acceptance Guidelines ?


Considerations / Best Practices

Know your Oracle Resources

Do several complete practice Upgrades (min 3 !!!).

Use similar hardware as Production Environment.

Use same data set that you expect for your

Production Upgrade.

Consider doing related systems changes during separate downtime(s)

Database Upgrade

Platform Migration for the DB- and/or the Middle-Tier

OATM conversion


Considerations / Best Practices - Continued

Identify your Customizations and check if they are still needed

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

Minimize duration of tasks performed before & after core upgrade driver

runs

Interim backups, final acceptance testing

Check for possible Downtime Reductions – later slides

Establish that the Upgrade will fit into your Downtime Window

Don’t forget to plan the Training for your End-Users !


EBS 11i - DB Upgrade Path

To Database 11g Release 2 (11.2.0) from :

Oracle9i Release 2 (9.2.0)

Oracle 10g Release 1 (10.1.0)


Oracle Database 11g Release 1 (11.1.0)

or earlier versions of Oracle DB 11g R 2

See Doc ID 1367654.1

To Database10g Release 2 (10.2.0) from :






To Database 12c Release 1 (12.1.0) from :









EBS 12.x - DB Upgrade Path

To Database 11g Release 2 (11.2.0) from :



earlier versions of Oracle Database 11g

Release 2 (11.2.0)


To Database10g Release 2 (10.2.0.5) from :

Earlier versions of Oracle 10g

Release 1 (10.1.0)

See Doc ID 812362.1

To Database 12c Release 1 (12.1.0) from :









Database Character Set

Preferred Character Set for R12 is UTF8

Multi Byte character sets better support National Languages

Latin, Chinese, Kyrillic, etc. characters in the same database

Better support for PDF output

See also :

Doc ID 788156.1 - AL32UTF8 / UTF8 (Unicode) Database Character Set

Implications

Doc ID 260192.1 - Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8

(Unicode) in 8i, 9i , 10g and 11g

Doc ID 778970.1 - How to Generate PDF Output With UTF8 in R12?





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


Upgrading Forms and Reports to R12 Linking differences between 11i and R12

On UNIX and Linux, E-Business Suite user-exit code is now

included in its own FND-owned shared object, which is

dynamically linked at runtime. e.g. : on Linux

$FND_TOP/bin/fndfmxit.so and $FND_TOP/bin/fndrwxit.so is

included. There is no longer any need to build separate Forms

and Reports runtime executables with the E-Business Suite

user-exit objects statically linked.

In Release 12, the executables $ORACLE_HOME/bin/frmweb

and $ORACLE_HOME/bin/rwrun are built by the standard

OracleAS 10g 10.1.2 patching process. The difference is that

Release 11i, used f60webmx, ar60run, ar60runb and ar60rund

executables with user-exit objects statically linked.

See Doc ID 437878.1 - Upgrading OracleAS 10g Forms and

Reports in Oracle E-Business Suite Release 12



Patchsets are now installed using the Oracle Universal

Installer on all Platforms.

One-off patches are now installed using the Oracle opatch

utility.

Opatch performs automatic conflict detection and various

rollback options.

Instructions about the usage are in the Patch READMEs.

Doc ID 224346.1 - OPatch - Where Can I Find the Latest

Version of OPatch? [Video]

Upgrading Forms and Reports to R12 Patching Forms & Reports (Developer)



Oracle E-Business Suite Release 12 does not use the

default jar files shipped with the Forms product. Instead,

it builds its own although it should be noted that the

individual class files are the same and the only difference

is in the packaging.

In Release 12 the E-Business Suite jar files are built

using $ORACLE_HOME/forms/java/frmall.jar and

$ORACLE_HOME/jlib/ewt3.jar as the source, rather than

the standalone class files.

Upgrading Forms and Reports to R12 Client Java Code


Personalizations Framework

For the most parts an Upgrade of an OA Framework

based page from Release 11i to 12.1.3 that page will

still exist in 12.1.3 - unless the specific Oracle EBS

Product has been heavily redesigned.

OA Framework Personalizations are likely to upgrade smoothly

("like to like") to 12.1.3

depends on the specific products you have.

Doc ID 1368023.1 - Oracle Applications Framework and Forms

Personalization Frequently Asked Questions (FAQ's)

Doc ID 397813.1 - Troubleshooting Framework Personalizations

Doc ID 1292611.1 - Upgrading Form Personalizations and OA

Framework Personalizations from Oracle E-Business Suite

Release 11i to 12.1





A screen or page may has been sufficiently modified in the

new version of the product such that the old objects that were

personalized no longer exist in the new version.

For the 11i to 12 Upgrade however, Forms are more likely to

have been rebuilt in OA Framework than to have been

modified using Oracle Forms.

An Oracle Forms based screen may be has been replaced

by an OA Framework-based page. This is very common

across the 11i to 12.1 upgrade, because many Products have

rebuilt a lot of their Oracle Forms-based functionality into OA

Framework while adding or redesigning other features.

For example, the User Interface for item instance

functionality in Oracle Install Base has been rewritten in OA

Framework.

Doc ID 395117.1 - Form Personalizations in Oracle E-

Business Suite (Release 12)

Doc ID 420518.1 - Limitations of Forms Personalization

Doc ID 455243.1 - Is a 'Form Personalization' Considered a

Customization?

Personalizations Forms





Oracle Resources to Help with Upgrade

EBS Upgrade page Value, Cost, Service

www.oracle.com/goto/upgrade-ebs-12-1

EBS YouTube Channel EBS Strategy by Cliff Godwin, EBS Endeca demos, more

www.youtube.com/oracleebsdemos

Customer Successes EBS Customer Success Search

www.oracle.com/search/customers/browse/_/N-1z13xx4

EBS Customer Success Booklet

www.oracle.com/goto/EBSCustomers

Available to Customers on oracle.com and My Oracle Support (MOS)

• Upgrade Best Practices White Paper Plan roadmap & scope, Upgrade vs. reimplement, Financials setup,

Customizations, Related system changes, Minimize downtime, Testing,

Training, more

MOS Doc 1406960.1

EBS 12.1 Info Center, 12.2 Info Center Release Content Documents (RCDs), Release Value Propositions

(RVPs), Online Training, Online Documentation, TRM, Proactive

Support Tools, more

MOS Doc:12.1 806593.1 , 12.2 1581299.1

Proactive Support Tools (aka 432.1) Prevent: Patch Wizard, Workflow Analyzer, Newsletters, Advisor webcasts

Resolve: Period Close Advisor, EBS Patch Community, Product Info Center

Upgrade: Upgrade Advisor (Doc 269.1), Maintenance Wizard, Patch Wizard,

Comparison Reports

MOS Doc 432.1

Why Upgrade Planning and Executing Upgrade

http://www.oracle.com/goto/upgrade-ebs-12-1







http://www.youtube.com/oracleebsdemos

http://www.oracle.com/search/customers/browse/_/N-1z13xx4




http://www.oracle.com/goto/EBSCustomers

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1406960.1






Oracle Services to Help with Upgrade Expert Resources Readily Available

Support

Resources

Consulting

Services

• 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)

• Proactive Support Tools (MOS Doc 432.1): Upgrade Advisor (MOS Doc 269.1)

• Support Communities: Upgrade, Customizations, Patching, more

• Advisor Webcasts (MOS Doc 1455369.1)

• Available to all customers with active support contract

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

Complementary CEMLI Analysis (North America)

• Broad expert partner ecosystem

Managed Private

Cloud

Services

• Oracle Managed Cloud Services: Your Oracle Applications managed any way you want; choice

of hosting @ Oracle, @customer, @ partner, or hybrid options

• Oracle EBS Upgrade Factory: Upgrade AND move from on-premises to managed cloud

• Many partner offerings

Advanced Support

Services • Oracle Advanced Customer Services (ACS): Tailored advanced services for your needs, including

technical expert onsite for few weeks for upgrade assessment at low cost






https://communities.oracle.com/portal/server.pt/community/upgrade/258

https://communities.oracle.com/portal/server.pt/community/e-business_customizations/322

https://communities.oracle.com/portal/server.pt/community/e-business_patching/358


http://www.oracle.com/us/products/consulting/index.html

http://www.oracle.com/webapps/dialogue/ns/dlgwelcome.jsp?p_ext=Y&p_dlg_id=13735691&src=7618001&Act=92

http://www.oracle.com/us/solutions/cloud/managed-cloud-services/apps-on-demand/overview/index.html

http://www.oracle.com/us/solutions/cloud/managed-cloud-services/sol-brief-ebs-final-1-1911305.pdf

http://www.oracle.com/us/support/advanced-customer-services/overview/index.html


Oracle Products to Help with Upgrade Automate Tasks, Reduce Effort

Training

Testing

• Oracle User Productivity Kit (UPK): Easy-to-use and comprehensive content development,

deployment, and maintenance platform for increasing project, program, and user productivity

• Oracle UPK Pre-Built Content for E-Business Suite and many more Oracle products

• Oracle Application Testing Suite (OATS)

• Oracle Functional Testing Suite for Oracle Applications, including EBS pre-built test content

• Oracle Load Testing Suite for Oracle Applications

• Oracle Test Manager: test process management, including test requirements management, test

management, test execution and defect tracking

Advanced

Controls

• Oracle Governance, Risk & Compliance (GRC)

• Risk and Financial Governance

• Performance and Operational Controls

• Access and Segregation of Duties (SOD) Controls

http://www.oracle.com/us/products/applications/user-productivity-kit/overview/index.html

http://www.oracle.com/us/products/applications/user-productivity-kit/pre-built-content/index.html



http://www.oracle.com/us/support/advanced-customer-services/overview/index.html

http://www.oracle.com/technetwork/oem/app-test/etest-101273.html?ssSourceSiteId=ocomen





http://www.oracle.com/us/solutions/corporate-governance/overview/index.html


Objectives


Pre-Upgrade


Downtime Reduction

Post-Upgrade

Question & Answers


E-Business Upgrade Advisor Doc ID 269.1 Upgrade Lifecycle Advisors are

specially crafted documents-

Phase Approach

Provides step-by-step

instructions to perform an

upgrade

Easy to follow upgrade process

for 11.5.10.2 to 12.1.3

Access to the relevant

information and knowledge

dependent on current phase/step

in the Lifecycle process

Potential to reduce the total

upgrade lead time



Frequent Inquiries to Support on Upgrade

Inquiry #1: Roadmap & Resources

Upgrade Overview tab

Inquiry #2: Customization Evaluation


Inquiry #3: Minimize Downtime


Inquiry #4: Patching & Patch Wizard

Configure Tab

Post 12.1.3 Recommended Patches


Upgrade Advisor - Printing Options

Print by Phase Feature

Will print for each phase

Print to PDF, File, Printer

Printable Page Feature

Exact Page


Upgrade Advisor - Using the Check Box

Stored Cookie

Check box

Black -> Red

Where you left off

Items to flag/Return


Audience Poll

Show of hands: Who has heard of Upgrade Advisor

Show of hands: Who has looked/used Upgrade Advisor


Upgrade Advisor – Phase Overview

Decision Making, Success Stories, Planning & Executing and Expert Services

Top Documents to start


More Resources…

Upgrade Advisor – Phase Overview


Assist with Production data clean up, Upgrade, R12 testing & , R12

Maintenance

Upgrade Advisor – Proactive Upgrade Tool


Collection of Key Documents based on a common topic

Upgrade Advisor – Upgrade Concepts


Upgrade Advisor - TEST


Oracle Applications Testing Suite Downloads

OATS 12.3.0.1

Doc ID 1578030.1



Road Map & New Technology Lifetime Support

Subscribe to Oracle E-Business Suite Technology Blog –Steven Chan

Review Oracle E-Business Suite recommendations & Certification announcements


Collaborate with a large network of industry peers, support professionals, and Oracle experts to exchange

information, ask questions & get answers.

• Exchange Knowledge

• Resolve Issues

• Gain Expertise

Visit My Oracle Support Communities

Visit the My Oracle Support Community now!!

1. Log into My Oracle Support.

2. Select the Community tab.

3. Select the Enter Here button.

4. Select the Community Name link under the

E-Business Suite section of the My

Communities Menu on the left side of the

window.

https://metalink.oracle.com/


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.

Convert to Oracle Applications Tablespace Model (OATM) – Doc ID 404954.1

Convert to Multiple Organization architecture - Doc ID 210193.1

Drop MRC schema (11.5.10 and above )

Upgrade RDBMS version to latest certified DB for your EBS Release

Other planned HW or OS Upgrades (new HW; OS/DB 64 Bit)

11.5.10 Minimum Baseline Patches - Doc ID 883202.1

Check Patch Wizard for recommended Patches – 11i, 12.0.x, 12.1.x

Error Correction Policy Patches

Pre-Upgrade activities – separate Downtimes





Use TUMS (“The Upgrade Manual Script”) to identify tasks not relevant to

your system

Review and disable all debug and/or logging at

Site level

Responsibility level

User level

Gather statistics with GATHER_AUTO option for all schemas close to the

start of the Downtime.

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 Transparent Data Encryption (TDE) from volume tables

Assign Post Upgrade jobs to specialized CM queue (by request_type, see Doc ID 399362.1)

Export statistics gathered during test runs, and import during final run

See Doc ID 117203.1

Pre-Upgrade Activities – Prepare Instance





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

Review “Known-issues” sections from key “living” documents

such as Release notes, MP Install Instructions

Consolidated Upgrade Patches (CUP)

EBS R12.1 CUP 2 (Patch 16791553)

Latest pre-install Patches (Doc ID 1448102.1) - apply

ALL Patches

Performance, script issues, data issues

Recommended post Upgrade Patches from PatchWizard

Not Applied & Missing



Patching Considerations

Patch merging, sequencing and adpatch options

Use non-interactive option of adpatch

Merge Patches (Doc ID 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 (Doc ID

1330470.1)

Use adpatch options such as nomaintainmrc,

phtofile, nolink, nogenform, nogenrep, nocompile

jsp, noautoconfig, novalidate (Doc ID 1078973.1)

Patch A Patch B

New merged

Patch






Patch Wizard Patch Wizard analyzes and

compares patches currently

applied in your instance with the

ones included in the

Recommended Patch List

Patch Wizard performs an impact

analysis, and allows for easy

download of patches you decide to

apply


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

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

By Request”

Post-upgrade “hot-patch” of additional historical data outlined in Doc ID 604893.1

Data Set & Data Cleaning - Overview



Reducing Your Oracle E-Business Suite Data Footprint using Archiving, Purging, and

Information Lifecycle Management (Doc ID 752322.1)

EBS Archiving & Purging

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)



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

EBS Purging


Objectives


Pre-Upgrade


Downtime Reduction

Post-Upgrade

Question & Answers


12.1 CUP 2 & Pre-Install Patches

12.1.1 CUP 2

Pre-install patches for R12.1

R12.1 patch that delivers higher

versions for files called by the R12.1

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.1.1 main upgrade

driver


Maintenance Wizard – Doc ID 215527.1 & Doc ID 434387.1

Guidance through the upgrade process

For Release 11i versions to Release 12

Minimizes upgrade tasks by dynamically

filtering the necessary steps based on IT

stack related criteria

Provides a set of step-by-step

instructions, including any critical

patches required

Reduces the possibility of errors or

accidental omission of vital tasks





Period Close Advisor – Doc ID 335.1

One-stop shop for period

close steps for all products

(in the order of closing)

Complete the critical

financial reporting process

accurately



Patching Advisor & Patch Wizard

Patching & Maintenance Advisor

Best Practices; Skill building

Proactive Strategy

Patch Wizard

11.5.10 Minimum Baseline

Patches

12.1.3 Recommended Patches

Proactive Strategy


Oracle Workflow Analyzer

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

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


Clone Log Parser Utility Save time validating Clone Logs

Consolidates over 12 cloning log

file types in a single HTML

Linked solutions for instant error-

fix recommendations

Provides basic configuration and

health checks of the environment


Identifies known data integrity issues during Migration/Upgrade/New Install

Isolates specific setup with the corrective action to resolve

My Oracle Support Notes and/or data-fix patches to resolve issues

Still have question – go to Oracle Payables Community or the EBTax Community

R12 EBTax Setup and Data Integrity Analyzer

https://communities.oracle.com/portal/server.pt/community/support/284

https://communities.oracle.com/portal/server.pt/community/e-business_tax/232


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 Period Close Helper Diagnostic to Validate Data Before Period Close


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

R12 Internet Expenses Setup Helper


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


Both functional and technical

users can use these diagnostics

R12 Payables Trial Balance Helper


Execute report immediately after the AutoInvoice Import program

Analyzes

AutoInvoice Interface tables

Analyzes validation errors encountered by AutoInvoice

program

3 values in report to alert you

Critical: identifies issues that would prevent successful

processing of Interface tables

Warning: identifies issues that could adversely affect the

performance of AutoInvoice program, though it may not

cause AutoInvoice program to fail

Informational: identifies issues that may not cause failure

but can be improved, and also provides data/settings that

you can address


3 Output styles

Output For All Orgs In Detail Format

Output For Single Org In Detail Format

Output For Single Org In Detail Format with Request ID

AutoInvoice Post-Process Validation Report Overview and Installation Instructions


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

ASCP Performance Analyzer (11.5.x & R12) Script for Performance Monitoring


Smoother Period Close: MGD + PCH + 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

Determine and Action Period Close

Obstacles – Doc ID: 1489381.1

Prevent Reoccurrence with Code

Fixes – Doc ID: 1397581.1

TIP:

Functional End Users

C –Level & Project leads

Critical to know

Master Generic

Datafix

Diagnostics

(MGD/GDF)

Period Close

Helper (PCH) Recommended

Patch

Collection

(RPC)

Smoother

Period Close


SQLTXPLAIN Tool

Perform SQL Tuning analysis

using the SQLTXPLAIN (SQLT)

tool

Diagnostic output generated by

the tool aids in troubleshooting

performance problems


ORA-600/7445 Tool

Advanced troubleshooting

capabilities for generic ORA-600

and ORA-7445 errors

Diagnosis can be done based on

error code, error message, or by

parsing the related stack trace


Objectives


Pre-Upgrade


Downtime Reduction

Post-Upgrade

Question & Answers


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

buffer cache = multi Gb, be generous

without causing excessive paging or

swapping

Adjust with help from AWR pool advisory

Configuration for the Upgrade Database - Tier

Other upgrade specific init.ora changes

If specified

remove db_file_multiblock_read_count

Maximize multiblock I/O sizes

Set job_queue_processes = # of CPUS

adobjcmp.sql (Phases : plb+90 and last+63)

Set parallel_max_servers = 2 X CPUs

Helps with large index creation, stats gathering and some

large upg+ phase jobs

Needs to be tested with a Production-like DB server and

I/O subsystem !


Shutdown RAC instances, so that 1 DB RAC Node remains

The majority of the elapsed time of the R12Release 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 add Performance or just provide Redundancy ?”

RAC will only increase 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).

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.

Configuration for the Upgrade RAC (Real Application Cluster) Database – Tier


Batch size and #workers

Batch size

10K is suitable for most patches, you can test other

values from 1K up to 100K 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)

ADPATCH Settings during Upgrade


Affecting Upgrade Performance

AD-Parallel improved scalability: Bug 8917381 (fix is

included in Patch 9179588 AD CUP)

Forms/reports generation regression with 11g: Bug:

8557019

Forms/reports Compilation Against a 11g Database

Hangs or Takes a Very Long Time Doc ID 880660.1

Optimizer : Dynamic Sampling on indexes Bug

12942119 (11.2.0.2)

General

Review Doc ID 244040.1 for latest recommended

EBS Performance fixes

Upgrade Performance Considerations




Downtime Reduction Procedures

Use “Staged APPL_TOP” (Doc ID 734025.1) for regular maintenance and upgrade

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

Reducing Downtime – staged APPL_TOP

1. Clone DB- & APPS-Tier

2. Upgrade staged Instance to R12.x

3. Connect R12.x staged APPS-Tier to PROD DB

4. Upgrade PROD DB

5. Synch APPL_TOPs between Stage and PROD in parallel

6. Synch the Patch History between Stage and PROD



Shared APPL_TOP & Distributed AD

Downtime reduction procedures

Use “Shared APPL_TOP” (Doc ID 384248.1) with “Distributed AD” for (Doc ID 236469.1) upgrades and regular maintenance for multi-node instances

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 timing for D/G portion of the patch driver.

adpatch workers 1-10




Admin/

CM

Server

Web

Server

Web

Server

Forms

Server

Database

Server





Shared

APPL_TOP





Parallelizing possibility

Following parallel processes are possible :

Perform Technology Stack Patching on 12.1.1 install prior to Upgrade.

Apply pre-install 12.1.1 Patches prior to main downtime.

Disable archive logging prior to starting Upgrade.

Continuously run utlrp utility from the Database techstack during the Upgrade run.

Execute Autoconfig in parallel on a multi-node system (Doc ID 387859.1)



Upgrade By Request Performance – Upgrade Guide - Appendix G and Doc ID 604893.1

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.1 Upgrade

and run the pre-upgrade concurrent program

Run the post-upgrade concurrent program (as needed for additional historical data)

Review Appendix G in R12.1 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 Part No. E16342-04

http://docs.oracle.com/cd/B53825_08/current/acrobat/121upgrade.pdf





Objectives


Pre-Upgrade


Downtime Reduction

Post-Upgrade

Question & Answers


Post-Upgrade Recommendations

Actions after the Upgrade finished

Create a Full Backup of your Instance – DB- & APPS-Tier

Re-enable Triggers which are needed

Re-enable the archive log of the DB-Tier

Re-implement your Customizations, which are still needed

Check for recommended Patches

If any issue is reported, please also look for available

Diagnostics


Product Diagnostics Framework

Simplify troubleshooting by regularly scheduling and executing diagnostics tests

Diagnostic tests are used prior to ‘go live’, and/or prior to closing an accounting period

Issues are proactively identified and corrected before deadlines


Patch Wizard Patch Wizard analyzes and

compares patches currently

applied in your instance with the

ones included in the

Recommended Patch List

Patch Wizard performs an impact

analysis, and allows for easy

download of patches you decide to

apply


Identifies known data integrity issues during Migration/Upgrade/New Install

Isolates specific setup with the corrective action to resolve

My Oracle Support Notes and/or data-fix patches to resolve issues

Still have question – go to Oracle Payables Community or the EBTax Community

R12 EBTax Setup and Data Integrity Analyzer Doc ID 1529429.1

Prevent

https://communities.oracle.com/portal/server.pt/community/support/284

https://communities.oracle.com/portal/server.pt/community/e-business_tax/232




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


Both functional and technical users

can use these diagnostics

R12 Internet Expenses Setup Helper Doc ID 1559272.1

Prevent




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


Both functional and technical

users can use these diagnostics

R12 Payables Trial Balance Helper Doc ID 1553507.1

Prevent





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

ASCP Performance Analyzer Doc ID 1554183.1 Script for Performance Monitoring

Prevent





Objectives


Pre-Upgrade


Downtime Reduction

Post-Upgrade

Resources / Question & Answers


EBS TechStack landing page – Doc ID 1480550.1

Save time when looking for Information

around the EBS Technology Stack.

Links to available Information Centers

shown in the picture.

Easy navigation through the different

areas of the EBS Technology Stack and

the related Components via Pop-Ups

when moving with the Mouse over a

specific area.

Resources





Latest Release Notes:

Oracle Applications Release Notes, Release R12.1.3 - Doc ID 1080973.1

Oracle Applications Release Notes, Release 12.1.1 - Doc ID 798258.1

Review Pre Install Patch - Doc ID 1448102.1

Oracle Applications Patching FAQ for Release 12 – Doc ID 459156.1

Oracle Applications Patching FAQ for Release 11i - Doc ID 457566.1

Steven Chan’s Oracle E-Business Suite Technology Blog

https://blogs.oracle.com/stevenChan

Planning Your EBS Upgrade from Release 11i to Release 12 - Doc ID 1406960.1

Best Practices for Minimizing EBS Release 12 Upgrade Downtime - Doc ID 1581549.1

Oracle E-Business Suite Reducing Downtime Upgrading to 12.1 - Doc ID 1578187.1

Doc ID 1581299.1 – Information Center 12.2

Doc ID 1585857.1 – 12.2 Technical Planning Guide

Doc ID 1587195.1 – Getting started with EBS 12.2

Doc ID 1531121.1 - Using the Online Patching Readiness Report in EBS Release 12.2

Resources













Latest Release Notes:

Oracle Applications Release Notes, Release R12.1.3 - Doc ID 1080973.1

Oracle Applications Release Notes, Release 12.1.1 - Doc ID 798258.1

Review Pre Install Patch - Doc ID 1448102.1

Oracle Applications Patching FAQ for Release 12 – Doc ID 459156.1

Oracle Applications Patching FAQ for Release 11i - Doc ID 457566.1

Steven Chan’s Oracle E-Business Suite Technology Blog


Planning Your EBS Upgrade from Release 11i to Release 12 - Doc ID 1406960.1

Using the Online Patching Readiness Report in EBS Release 12.2 - Doc ID 1531121.1

Best Practices for Minimizing EBS Release 12 Upgrade Downtime - Doc ID 1581549.1

Oracle E-Business Suite Reducing Downtime Upgrading to 12.1 - Doc ID 1578187.1

Resources

















Reduce data volume using archive and purge - Doc ID 752322.1

Use Subledger Accounting “Upgrade by Request” (UG Appendix G + Doc ID 604893.1)

Use a shared APPL_TOP - Doc ID 384248.1

Use a staged APPL_TOP - Doc ID 734025.1

Distributed AD - Doc ID 236469.1

Isolate post-upgrade concurrent programs in a special queue - Doc ID 399362.1

Patching Best Practices And Reducing Downtime – Doc ID 225165.1

Patching Shared Oracle E-Business Suite Products – Doc ID 1069099.1

Oracle E-Business Suite Release 12.1 Information Center - Doc ID 806593.1

Recommended Performance Fixes - Doc ID 244040.1

R12 Upgrade Sizing & Best Practices - Doc ID 399362.1

Database preparation guidelines for R12.1 Upgrade - Doc ID 761570.1

Patching FAQs - Doc ID 459156.1 & Doc ID 225165.1

OAM “Patch Wizard” overview and FAQ - Doc ID 976188.1 & Doc ID 976688.1

AD Command Line Options for Release R12 - Doc ID 1078973.1

Cloning Oracle Applications Release 12 with Rapid Clone - Doc ID 406982.1

Resources





















Learn More

About Oracle Support Best Practices

www.oracle.com/goto/proactivesupport

Get Proactive in My Oracle Support

https://support. oracle.com | Doc ID: 432.1

Get Proactive Blog

https://blogs.oracle.com/getproactive/

Ask the Get Proactive Team

[email protected]

Available References and Resources to Get Proactive

http://www.oracle.com/goto/proactivesupport

https://support.us.oracle.com/


https://blogs.oracle.com/getproactive/

mailto:[email protected]




Questions and Answers


Thank You !


Appendix A

Actions after each Test Upgrade


Performance testing, monitoring and additional optimizations

Analyze long running jobs via timing report, ad_task_timing analysis

Check ad_task_timing to identify low worker utilization due to phasing waits and review responsible

culprits

Review targeted AWR Instance and SQL reports –

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

The awrrpt.sql SQL script generates an HTML or text report that displays statistics for a range

of snapshot Ids.

The awrsqrpt.sql SQL script generates an HTML or text report that displays statistics of a

particular SQL statement for a range of snapshot Ids. Run this report to inspect or debug the

performance of a SQL statement. http://www.oracle-base.com/articles/10g/automatic-workload-

repository-10g.php

After each Test-Upgrade check for...


Use My Oracle Support to check for known issues and workarounds for the longest

running jobs (Pre-install should fix many known 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 a sql-script having issues - R12 : Performance Issue While Running apilnupg.sql (Upgrade to 12.1.1) - Doc ID 942694.1

After each Test-Upgrade check for... continued





* 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). 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

Thousands of jobs and customer product/data/setup configurations

Some of the heavy lifting work may not be required for a specific site

Check with Oracle Support to validate

A fix may be available for your case

New 12.1.3 AD timing report by module



Appendix B

Testing


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


R12 Period Close Helper – Doc ID 1489381.1

Diagnostic to Validate Data Before Period Close

Prevent




Execute report immediately after the AutoInvoice Import program

Analyzes

AutoInvoice Interface tables

Analyzes validation errors encountered by AutoInvoice

program

3 values in report to alert you

Critical: identifies issues that would prevent successful

processing of Interface tables

Warning: identifies issues that could adversely affect the

performance of AutoInvoice program, though it may not cause

AutoInvoice program to fail

Informational: identifies issues that may not cause failure but can

be improved, and also provides data/settings that you can address


3 Output styles

Output For All Orgs In Detail Format

Output For Single Org In Detail Format

Output For Single Org In Detail Format with Request ID

AutoInvoice Post-Process Validation Report Doc ID 1523525.1 Overview and Installation Instructions

Prevent





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

R12 PO Approval Analyzer Diagnostic Script Doc ID 1525670.1

Prevent




Use Application Testing Suite Accelerators to

Automate Testing

Testing Support Functional/regression, Load/Performance

Test Management

Automatic script generation Reduce scripting time by ~50%

EM Grid Control Integration JVM Diagnostics for mid-tier

DB Diagnostics for DB-tier

DB Profiles for Oracle Database



Automate Testing

Accelerators & Test Starter Kits

Support for EBS 11i & R12 (socket & servlet mode)

Supports both FORMS and Web actions (back-office/self service)

EBS specific object identification rules

EBS specific correlations

Automatic test case creation

Oracle E-Business Suite Test Starter Kit (~75 pre-built scripts)

Use Case: Oracle@Oracle: http://www.oracle.com/technetwork/oem/app-quality-mgmt/oracle-at-oracle-oats-case-study-184436.pdf



Automate Testing

Web Actions

Forms Actions


Appendix C

Globalization Documents


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 Applications Release 12 Translation Scope and Availability - Doc ID 405992.1

Database NLS Frequently Asked Questions - Doc ID 60134.1

Oracle E-Business Suite Release 12 Technology Stack Documentation Roadmap - Doc ID 380482.1

Globalizations






















Appendix D

Platform Migration – DB- & APPS-Tier


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 4 to Oracle Linux 5

(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

Most of the time is spent in copying Database files and Middle-Tier files

Tips and Recommendations

Parallel copy with compression can be used to optimize the time consuming step of copying

dbf files.

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=406982.1


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








The source (export from) ORACLE_HOME directory must be Oracle Database 10g Release

2 (10.2.0), 11g Release 1 (11.1.0), or 11g Release 2 (11.2.0). 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

Reference Notes:

11i/10gR2 :'Export/Import Process for Oracle Applications Release 11i Database Instances

Using Oracle Database 10g Release 2' - Doc ID 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 ID 557738.1

R12/10gR2 : 'Export/Import Process for Oracle E-Business Suite Release 12 Database

Instances Using Oracle Database 10g Release 2' – Doc ID 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 ID 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)

Reference Notes:

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.


Application Tier Migrations

11i to R12 Upgrades

Prepare the DB for Upgrade, install a new R12 app tier, 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 a new R12 app tier on the file system

R12 Upgrades using Release Update Packs (RUP)

A RUP is used to upgrade an existing R12.1 system

Applied on an existing R12.1 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 to a new platform, do RUP, Then migrate to new platform using Doc ID 438086.1



1 Copyright © 2013, Oracle and/or its affiliates. All ... · purchasing decisions. The...

Documents

Transcript of 1 Copyright © 2013, Oracle and/or its affiliates. All ... · purchasing decisions. The...