EBS-technical_upgrade_best_practices 12.1 or 12.2

1

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

E-Business Suite Release
Upgrade Best Practices Technical Insight
Udayan Parvate
Senior Director, EBS Release Engineering
Samer Barakat
Senior Architect, Applications Performance
2


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.

3

3
Copyright © 2012, and/or its affiliates. All rights rights
Copyright © 2013, OracleOracle and/or its affiliates. All reserved.
reserved.

Program Agenda
 R12.1/ R12.2 Upgrade Overview

 R12.1 / R12.2 Supported Upgrade Paths
 R12.1/ R12.2 Upgrade Resources

 Upgrade Best Practices to Minimize Downtime
 References (Customer Upgrade Snapshots and more)

 Q&A

4


R12.1/ R12.2 Upgrade
Overview

5


R12.1 Rapid Install (RI)
R12.1 Maintenance Pack (MP)


R12.1 was generally available (GA) in May 2009
– Via Oracle Software Delivery Cloud (OSDC, formerly known as

Electronic Product Delivery (EPD)) and Oracle Stores

Can be used by new and upgrading customers (11.5.9
and above) to go directly to R12.1


– If you are on R11i, use R12.1 RI from the software delivery cloud.

Follow instructions from the “Upgrade Guide: 11i to 12.1” and “12.1.1
Release notes”
– If you are on R12.0.X, use R12.1 MP (7303030) from My Oracle

Support (MOS). Follow instructions from “R12.1 Maintenance Pack Install
Instructions (752619.1)”
6


EBS R12.1 Release Update Pack (RUP) 3
(12.1.3) Release
EBS 12.1.3 was released in Jul 2010 and delivers
bugfixes and targeted functionality enhancements
 Available from My Oracle Support (MOS) as a patch
 Can ONLY be applied after upgrade to R12.1
 Currently, EBS 12.1.3 is the latest suite wide RUP
available for R12.1
 EBS 12.1.3 Installation instructions : 1080973.1


7


R12.2 Rapid Install (RI)
 Available as RI Only from OSDC. No Maintenance Pack available

from MOS. Upgrade your 11i, R12.0.4 or R12.1.X instance by
following the upgrade guide meant for your current EBS release
– For 11i, you must be on 11i10CU2 and satisfy the minimum baseline

patch level (MBL) requirements for extended support ( 883202.1) for a
direct upgrade to R12.2
– Apply patch 13543062:R12.AD.C as an additional step to enable

edition based redefinition (EBR) after US upgrade driver is complete.
– All patches beyond this step MUST be applied using ADOP ( online

patching compatible version of adpatch )
– The EBS upgrade to R12.2 itself is NOT an Online Patch

8


EBS R12.2 Release Update Pack (RUP) 2
(12.2.2) Release
 EBS 12.2.2 (16207672 ) is the required RUP level for running R12.2

in a production instance
 Available on My Oracle Support (MOS) as a patch for existing
customers and on OSDC for new customers
 Can ONLY be applied after upgrade to R12.2.0 using ADOP
 EBS 12.2.2 Installation instructions : 1506669.1

9


R12.1 / R12.2 Technology Stack

•

Apps Mid tierForms/Reports

•

Apps Mid tierJava Oracle
Home/

•

VERSION
INCLUDED

VERSION
INCLUDED

VERSION
INCLUDED

11i10CU2

TECHNOLOGY
COMPONENT

12.0.4 RI

12.1 RI

6.0.8.25

10.1.2.2

1.0.2.2/1.4.2

10.1.3.0/1.5

9.2.0.6

10.2.0.3

VERSION INCLUDED
VERSION CERTIFIED
WITH

MINIMUM REQUIRED
VERSION

12.2.0 RI

10.1.2.3

-

10.1.2.3

10.1.2.3

10.1.3.4/1.6.0

10.1.3.5

10.1.3.4/1.6

FMW 11.1.1.6/ 1.6

10.2.0.5

11.2.0.3

Apps Mid tierJDK

10gr2: 10.2.0.5
•

10

Database


11.1.0.7

11gr2: 11.2.0.3,
11.2.0.4, 12c

R12.1 / R12.2 Key Facts
11i10CU2
#of Product
Schemas

#file calls in DB
portion of the U
driver

PROD db size
File system size
#files shipped
in RI / RUP
#of Jobs
(Changed +
New) in DB
portion of the U
driver

R12.0.4 RI

R12.1 RI

12.1.3 RUP

195

201

209

(25 removed,11
added)

(25 removed,17
added)

No changes

104242

144940

156622

23408

31 GB

45 GB

50 GB

12.2.0 RI
173

28 GB

142074

357778

389521

NA
64 GB (Patch+Run)

52103

365055

41223

~108049
(Vs 11iMBL)

~113337
~95488

( Vs 11.5.10.2 )

~23474

~55575

17375

( Vs 11.5.10.2 )

~31843

( Vs 12.1.1)

(Vs 12.0.4)

( Vs 12.2.0)

NA
( Vs 12.0.4 )

32166
(Vs 12.1.3)

11

16066

90 GB

28 GB

268359

No changes

(54 removed,18
added)

NA
26 GB

12.2.2 RUP


R12.1 / R12.2 Supported
Upgrade Paths

12


R12.1 Upgrade Paths ( DB Prep Guide 761570.1)


Minimum EBS suite level for direct upgrade to R12.1
– 11i9, 11i9CU1, 11i9CU2 or above
– 11i10, 11i10CU1, 11i10CU2 or above

– R12.0 and above



Minimum EBS suite level required for database versions
– 10.2.0.4 requires 11i9CU2

– 10.2.0.5/11.1.0.7/11.2.0.3/11.2.0.4/12.0.4 require 11i10CU2/R12.0.4

 Certified upgrade path options can be categorized into
A.Upgrade database and EBS level in a single downtime
B.Upgrade database and EBS level in separate downtimes
C.Apply upgrade interoperability DB patches and then upgrade EBS
13


R12.1 Upgrade Paths Continued..

TARGET

11.0/11i.X => 12.1
SOURCE

12.1

< = 11.5.8

B ,C

11i10cu2

B ,C
C

11.0

B ,C

11i9cu2
11.5.9/cu1
11.5.10/cu1

A

A. Upgrade database and EBS level in a single downtime

B. Upgrade database and EBS level in separate downtimes
C. Apply upgrade interoperability DB patches and then upgrade EBS

14


11.2.0.3/11.2.0.4/
12c

A

12.1

10.2.0.5

C

12.1

11.1.0.7
12.1
10.2.0.4

R12.1 Upgrade Paths Continued..

TARGET

12.0.X => 12.1
12.1
SOURCE

10.2.0.4

B ,C
B ,C
A

< = 12.0.3
A

12.1
11.2.0.3

B ,C

> = 12.0.4

12.1

B ,C

11.1.0.7
B ,C


15


12.1
10.2.0.5

R12.2 Upgrade Paths (DB Prep Guide 1349240.1)
TARGET

SOURCE

< = 11.5.8
11.0

11i10CU2
MBL

12.2

11.5.9/cu1
11.5.10/cu1

11i9cu2

< 12.0.4

>=12.0.4 or
12.1.X



16

A, B ,C


11.2.0.3

A, B ,C

R12.1 / R12.2 Upgrade
Resources

17


EBS Data Model Comparison Report
Per product database object comparison between two releases for
the following object types (1290886.1)


–Regular tables, Partitioned tables, Index organized tables, Global

temporary tables, Queued tables
–Views, Materialized views, Materialized view logs
–Indexes, Sequences, Advanced queues, Packages, Triggers

 R12.1.3 and R12.2.2 comparison with prior EBS releases available
 Benefits
–Customers can focus on what has changed
–Easier to analyze impact on customizations, planned test coverage
–Differences viewable for all products in the same report via simple UI
18


19


R12.1.3 EBS ATG Seed Data Comparison Report
 Per product EBS ATG Seed data type comparison between two

releases (1327399.1)
– Supports most of the EBS delivered seed data types. e.g. Menus,

Functions, Profiles and many more
 Benefits
– Meant for Advanced user with prior knowledge about EBS Seed data

delivery
– Easier for developers/consultants/testing team to analyze impact on

customizations, planned/desired test coverage
– Post Go-live, to answer end-user questions

20


21


EBS File Comparison Report (1446430.1)
 EBS file system comparison per product
–Supports most of the file types found in EBS file system
–ASCII files: new, removed and changed files compared to prior release
–Binary files: new, removed files compared to prior release


 Benefits
–In upgrade planning phase, customers can get information about new,

removed and changed files
–Assistance in analyzing impact on customizations, personalization and

planning functional flow tests
–Differences viewable for all products in the same report via a simple UI
22


23


January 2012

R12.1 “pre-install” Patches Report (1448102.1)
 What is a pre-install patch ?

Any patch that fixes upgrade itself (critical upgrade failures, upgrade
performance issues). Must be applied to the R12.1 RI file system using
“adpatch preinstall=y” option
–

– 16791553:12.1.0 is the latest consolidated upgrade patch 2 (CUP 2) and

includes recommended preinstall patches as of July 2013.
 EBS level Report (revised ~monthly) logistics and usage
– Merge patches listed with R12.1 CUP2 and apply. Then apply merged

upgrade driver. Helps avoid time/effort chasing individual SRs for known
upgrade fixes
 For R12.2, a CUP is planned to be released per EBS 12.2 RUP.

24


25


January 2012

Upgrade Best Practices
Performance and Downtime

26


Plan, Prepare, Test and Upgrade
 As with most planned production maintenance activities, a successful upgrade is

highly dependent on how well-defined the upgrade plan is.
 Pre-production testing and validation on an comparable system prior to the actual

upgrade is key to minimizing unforeseen contingencies.
 Optimizing the upgrade process is all about making the right choices at the planning

stage and verifying these choices with a test environment before production.
Planning Your Oracle E-Business Suite (EBS) Upgrade from Release 11i to Release 12
(MOS ID 1406960.1)
Best Practices for Minimizing Oracle E-Business Suite Release 12 Upgrade Downtime
(MOS ID 1581549.1)

27


Plan: Prepare Platform
Plan for Platform Migration as a Separate Down Time
 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 due to the
fact that the upgrade of the Applications to R12 will run on newer and faster
hardware.
Oracle E-Business Suite Upgrades and Platform Migration (MOS ID 1377213.1)

28


Plan: Prepare Database
Plan for Database Upgrade as a Separate Down time
 Upgrade RDBMS version to latest certified for the current APPS level ( 11.2.0.3 /

11.1.0.7 / 10.2.0.5


Tune Init.ora Parameters:
– Ensure mandatory init.ora parameters are set correctly.
– MOS ID 396009.1 & 216205.1 (R12 & 11i respectively)

 Apply Required Patches & Fixes/Workarounds for Known Issues
– Recommended Performance Patches - MOS ID 244040.1
– Required Patching – Interoperability Notes
 11gR1 Certified with 11i and R12 – MOS ID
 11gR2 Certified with 11i – MOS ID 881505

29


452783.1 & 735276.1

Plan: Manage Data Volumes
Purge Old and/or Transient Data
 Purge Portal
 Purge Portal introduced in 11i10
 Single purge/archive management

console
 Purge programs can be configured,

initiated and monitored
 Set the execution frequency as well

view history of purge programs.
 Accessing the Purge Portal
 System Administrator > Oracle

Applications Manager >Purging/Critical
Activities

30




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

31


 Archive/Purge Product Information

– Product User guides – GL/AP/AR/FA/OM
– Support Notes:
 (MOS ID 138264.1) – General Ledger Archive/Purge FAQ
 (MOD ID 144431.1) – Fixed Assets Archive/Purge FAQ
 (MOS ID 136919.1) – General Ledger Archive/Purge Setup and Usage
 (MOS ID 752322.1) : Reducing Oracle E-Business Suite Data Footprint

32


Prepare: Manage Patches/Tasks
Identify Required Patches/Tasks


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 from MOS.

–

Consolidated Upgrade Patches (CUP)



–



33

EBS R12.1 CUP2 (16791553:12.1.0)

Latest pre-install patches (MOS ID 1448102.1)

Review “Known-issues” sections from key “living” documents such as Release
notes, MP Install Instructions

Use TUMS (“The Upgrade Manual Script”) To avoid running tasks not relevant to your
system


Identify Required Patches/Tasks


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



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



34

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

Assign post upgrade jobs to specialized CM queue (by request_type)
MOS ID 399362.1


Upgrade By Request (MOS ID 604893.1)


Use this option to defer the upgrade of historical data from the initial upgrade
process (critical downtime window), to post upgrade



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)

Utilize Parallel Concurrent Processing (PCP) for post-upgrade concurrent jobs to
leverage the Cluster (RAC).
–

–

35

For RAC and PCP refer to (MOS ID1359612.1)

On 12.1 you can define node affinity at the program level (MOS ID 1129203.1)


Patch merging, sequencing and adpatch options


Use non-interactive patching



Merge patches (MOS ID 228779.1). Merge NLS patches per language.



Perform uptime maintenance when possible
–
–



36

Use Hot patching of iHelp, NLS patches, upload patch history
Apply HRGLOBAL as a hot patch (MOS ID 1330470.1)

Use adpatch options such as nomaintainmrc, phtofile, nolink, nogenform,
nogenrep, nocompile jsp, noautoconfig, novalidate (MOS ID 1078973.1)


Prepare: Manage Customizations
Check Custom Code
For the duration of the upgrade, consider…


Check and review customizations that business might not be using.



Review new Product Features or New Technology to Migrate to.



Review and disable custom triggers and business events.



Review and disable custom VPD polices as needed.
Review and eliminate redundant custom indexes.



Upgrading your Customizations to Oracle E-Business Suite Release 12.1
MOS ID: 1435894.1

37


Prepare: Manage Customizations
[R12.2 ONLY] Identify and fix custom code to comply to online patching
standards.



Use Global Standards compliance checker script to scan your file system custom
code and fix reported issues



Detailed instructions : “EBS Technical Planning Guide” and MOS ID 1531121.1



38

Use “Online Patching readiness Reports” to identify issues in custom data base
objects that will be fixed automatically Vs needing manual intervention

Download Patch 6236081:R12.AD.X for your current EBS Release (11i, 12.0 or
12.1) and use the scripts and generate the reports.


Prepare: Pre-Upgrade Tasks
Remove Unnecessary Workloads / Overheads




Review and disable all debug or logging; do this at all levels (site, responsibility, user
level etc.)



Purge all old data that is no longer needed prior to the upgrade. MOS ID 752322.1



39

Remove TDE (Transparent Data Encryption) from high volume tables (for the
duration of the upgrade).

Flush all the interfaces, such as Auto Invoice, Journal Entry Import, Order Import etc.


Prepare: Pre-Upgrade Tasks
Remove Unnecessary Workloads / Overheads



Convert to OATM (Oracle Applications Tablespace Model). MOS ID 248857.1



Convert to the new Multiple Organizations (Multi-Org) architecture MOS ID 210193.1



If possible run in noarchivelog mode



Disable flashback DB (for the duration of the upgrade).



40

Drop MRC Schema if it still exists.

Disable auditing if enabled (for the duration of the upgrade)


Prepare: Database Tier
Gather Schema Statistics
 Gather CBO statistics for all Oracle E-Business Suite schemas with GATHER_AUTO
option using FND_STATS (or gather statistics concurrent program)

 If the adsstats.sql job is taking a long time during the R12.1.1 upgrade check the
following:
– Check that parallel execution is being used effectively (with parallel_max_servers
set to a suitable value, such as 2 x number of cores).
–

Sample specific long running tables at a lower percentage

 If the adsstats.sql script is still taking a significant amount of time, reduce the upgrade
time by:
– Exporting schema statistics gathered during test runs (by adsstats.sql )
– Importing these statistics instead of running adsstats.sql.

41


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 gather manually as they are not gathered
automatically in the Release 12 upgrade by adstats.sql or any other method.

42


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

43


Properly Size SGA/PGA Memory


Maximize SGA and PGA sizing:
– Review the Advisory sections in AWR (from test runs) to fine tune SGA & PGA.
– Some starting rules of thumb are:
» 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.

 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.
44


Upgrade and Initialization Parameters




For more than 32 cores, start with:
– parallel_max_servers = 1 x number of CPU cores.
– AD Parallel workers = between 0.5 and 1.0 x number of CPU cores.



Based on the performance diagnostics, these values can be changed based on the level of
contention and resource (CPU/IO) usage (in AWR).



45

For 32 cores or fewer initially set:
– parallel_max_servers = 2 x number of CPU cores.
– AD Parallel workers – start with 1 x number of CPU cores. Possibly increase to 1.5 x
number of CPU cores.
– job_queue_processes = number of CPU cores

Shutdown other RAC instances


Upgrade and Initialization Parameters




Set optimizer_dynamic_sampling level to the value of 4 during the Release 12 Upgrade,
revert to the default value of 2 (or remove) after the upgrade.



The values of the initialization parameters above (except db_file_multiblock_read_count)
may be different from the values used for normal operation. So be sure to revert after the
Release 12 upgrade has completed.



46

If specified, remove db_file_multiblock_read_count. This is the recommended value for
normal operation of Oracle E-Business Suite.

For other initialization parameters, refer to MOS ID 396009.1, “Database Initialization
Parameters for Oracle E-Business Suite Release 12”.


Prepare: Application Tier
Upgrade and autoconfig


47

Run autoconfig in parallel on a multi-node system (MOS ID 387859.1)


Shared APPL_TOP and Distributed AD


Use “Shared APPL_TOP” (MOS ID384248.1) with “Distributed AD” for (MOS ID
236469.1) upgrades and regular maintenance for multi-node instances
–
–

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.

–

Using Distributed AD and Shared APPL_TOP gives more visible benefits when the
workload is not database centric (inserts/updates).

–

48

No need to apply the same patch on multiple tiers

Do not get tempted to use more workers than necessary. Avoid high worker counts
that might lead to contention issues.


Shared APPL_TOP and Distributed AD
Admin/CM
Server

adpatch
workers 1-10

Forms
Server

adpatch
workers 1-10
11-20

Web
Server

adpatch
workers 21-30
1-10

Shared
APPL_TOP

Web
Server

49


adpatch
adpatch
workers 31-40
workers 1-10

Database
Server

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

–

–

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

1. Clone

3. Sync APPL_TOP

1. Clone

4. Sync Patch
History

3. Update DB

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

50

Production


2. Upgrade DB

Stage

Test: Pre-Production Testing
Testing and Final Run Planning


Testing should be done on a comparable system that has the same CPU, IO and memory
capacity as the target production system



It is critical to do multiple rounds of testing with different settings to maximize server utilization,
while considering the following
–

Memory utilization (no swapping/ excessive paging)

–

CPU utilization (scale down if at 100%)

–

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





51

When analyzing Release 12 Upgrade performance issues, the goal is prevent wasted test
iterations by maximizing the number of performance issues resolved.
Testing timings along with system resource utilization should be used to plan the final upgrade
with a 20% contingency factor.


Get the Timings




AD Utility and Worker Logs: The AD utility and worker logs can also be useful for diagnostics,
giving you more detail about what happened and when. The AD workers logs (adworknnn.log)
will give you the activities carried out by each worker and the timings.



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



52

AD Job Timing Reports: The job timing report (adtimrpt.sql) reports the top 100 time
consuming jobs.

AD_TASK_TIMING: gives start and end times of jobs and workers, which can help identify all
long running jobs, and match long running SQL and performance issues (on AWR) with specific
jobs.


Get the Diagnostic Data


Start with Express Diagnosis of Oracle E-Business Suite Release 12 Upgrade
Performance Issues (MOS ID 1583752.1)
• SQL Tuning
•

Trace files

•

SQLT output (MOS ID: 215187.1)

•

Trace Analyzer (MOS ID: 224270.1)

•

AWR Report (MOS ID: 748642.1)

•

11g SQL Monitor Report

•

• Database Tuning
• AWR Report (MOS ID: 748642.1)
• ADDM report (MOS ID: 250655.1)
• Active Session History (ASH)

AWR SQL Report (awrsqrpt.sql)

• OS - OSWatcher (MOS ID: 301137.1)




53

Correlate AWR, system vitals and expensive SQLs. Start with the top events and top
SQLs sections in the AWR reports.
Use the advisory sections to size SGA, and PGA Properly


Common Optimizations




For long running SQLs - Display cursor report (with ALL +ALLSTATS ) can be used to
while SQL/job is running which massively speeds up the identification of sub-optimal
execution plans and their solution.



54

Use statistics_level=ALL during the testing/diagnosis phase. Make sure to reset to
TYPICAL afterwards. This will help capture runtime Execution plans with row counts &
row source stats.

The other alternative is SQL Trace - for which the trace can be enabled on the Job or
that particular SQL level.






Create custom indexes for long running jobs where a new index could significantly
improve the execution plan and performance



55

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.

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 (note that this requires MV complete
refresh)



For high level of waits associated with redo log, especially “log buffer space” and
“log file sync”, consider:
–

–

Move to faster filer

–

56

Change the configuration of redo logs
Increase redo log file sizes, increase the number of files or increase the log parallelism
(hidden parameter _log_parallelism_max).






However, bear in mind that the fix or workaround may not necessarily fix your
particular problem.



If you cannot confirm that you have exactly the same issue (from the diagnostics)
you may still apply the fix, but should continue to gather diagnostics and search for
a solution until the issue is fully resolved.



57

Once you have identified the long running jobs and SQL, you can check My Oracle
Support for known issues and potential solutions or workarounds.

If you have identified that a long running job has an inefficient execution plan, you
could use an SQL Profile to apply hints that will help the CBO choose a better
execution plan. You will need SQL tuning expertise to do this.


Customer Upgrade Snapshots

58


Customer Upgrade Snapshots Continued...
11i to 12.1.3
• Toyota Motor Europe
–
–
–
–
–

Release: 11.5.9+ on IBM AIX to R12.1.3 on Oracle Linux 5 Appl tier
DB size: 800 GB
#Workers: 32
#CPUs on DB server: 8 cores
Downtime reduction measures
• Online NLS patch application
– #hrs for the 12.1.1 D driver: 21 hrs
– #hrs for the 12.1.3 US upgrade: 4 hrs
– #hrs for the 4 languages NLS patching 11 hrs

59


Customer Upgrade Snapshots
11i to 12.1
 CPS (Chicago Public Schools)
– Release: 11.5.10.2 to 12.1

– DB size: 900GB
– #Workers and batch size: 32, 10000
– #CPUs on DB server: 2 node RAC, 8 CPUs per node

– Downtime reduction measures
 Distributed AD
 Upgrade RDBMS to 10.2.0.4 in a separate downtime
 # hrs for the D driver: 22 hrs

– Customer snapshot
http://www.oracle.com/customers/snapshots/chicago-public-schools-ebs-snapshot.pdf
60


11i to 12.0.6
 Cisco
– Release: 11i to R12.0.6
– DB size: 600GB
– #CPUs on DB server: 16
 Distributed AD
– #hrs for the D driver: 5.5 hrs

61


11i to 12.1.3
 Dell
– Release: 11i10 to R12.1.3
– DB size: 15TB , 16 node RAC Cluster
 Distributed AD
 Pre-create large indexes
– #hrs for the D driver: ~30 hrs

62


11i to 12.1
 GE
– Large EBS HRMS Implementation (~300K employees,10 Lang)
– Release:11.5.10.2 to R12.1.3, DB size: 838 G
– Hardware:

App Tier- 2 SUN T5240’s(64x64),
DB Tier - SUN M8000 (12 Dual Cores)

– #Workers and batch size per App Server: 48, 10000
 Distributed AD, Staged APPL_TOP

– #hrs for D driver:~10 hrs US, ~13 hrs NLS (11.5.10.2 -> R12.1.1)
– #hrs for DB Portion:~2.5 hrs US, ~1 hr NLS (R12.1.1 -> R12.1.3)

63


12.0 to 12.1
 Zebra Technologies Corporation
– Release: 12.0.6 to 12.1

– DB Size: 106GB
 Staged APPL_TOP
– #hrs for the U driver: 12 hrs
– Customer snapshot
http://www.oracle.com/customers/snapshots/zebra-technologies-corporation-ebs-snapshot.pdf

64


12.0 to 12.1
 Oracle GSI
– Release: 12.0.3+ to R12.1
– DB size: 17TB

– #CPUs on DB server: 88 processors
 Staged APPL_TOP for US and ten languages
 Ran data fixes for problems found in test upgrades prior to production

upgrade to minimize stoppages
 Distributed AD (4 servers,15 workers each)

 #hrs for the D driver: 14 hrs

65


12.1 to 12.1.3
 Oracle GSI
– Release: 12.1+ to R12.1.3
– DB size: 17TB

– #CPUs on DB server: 150 processors
 Ran data fixes for problems found in test upgrades prior to production

upgrade to minimize stoppages
 Distributed AD (4 servers, 50 workers each)

 #hrs for the D driver: 4 hrs

66


12.0 to 12.1.2
 AT&T
– Release: 12.0+ to R12.1.2
– DB size: 10 TB
– #CPUs on DB server: 32 Processors
 Distributed AD

– #hrs for the D driver: 9 hrs

67


References

68


References (R12.1 Specific)



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



Database preparation guidelines for R12.1 upgrade (761570.1)



Recommended Performance Fixes (244040.1)



R12 Upgrade Sizing & Best Practices (399362.1)


69

R12.1 documentation roadmap (790942.1)

R12.1 EBS pre-install patches Report (1448102.1)


References (R12.2 Specific)








70

Oracle E-Business Suite Release 12.2 Info center (1581299.1)
Oracle E-Business Suite Release Notes, Release 12.2
(1320300.1)
Oracle E-Business Suite Technical Planning Guide, Release 12.2
(1585857.1)
Preparation Guidelines for an E-Business Suite Release 12.2
Upgrade (1349240.1)
Using the Online Patching Readiness Report in Oracle EBusiness Suite Release 12.2 (1531121.1)
Oracle E-Business Suite Technology Stack Release Notes for
Release 12.2 (1376618.1)
Oracle E-Business Suite (12.2) Documentation Library


Additional Resources

71


Additional Resources


EBS Upgrade related Reports
–
–

EBS ATG Seed Data Comparison Report (1327399.1)

–


EBS Data Model Comparison Report (1290886.1)
EBS File Comparison Report (1446430.1)

White paper
–

–


Planning Your Oracle E-Business Suite Upgrade from Release 11i to
Release 12 (1406960.1)

Oracle E-Business Suite Upgrades and Platform Migration
(1377213.1)

Have Upgrade questions ? Please post on OTN R12 upgrade forum

http://forums.oracle.com/forums/forum.jspa?forumID=395&start=0

72


Q&A
73


74


75


EBS-technical_upgrade_best_practices 12.1 or 12.2

Recommended

More Related Content

What's hot (20)

Viewers also liked (18)

Similar to EBS-technical_upgrade_best_practices 12.1 or 12.2 (20)

More from Berry Clemens (20)

Recently uploaded (20)

EBS-technical_upgrade_best_practices 12.1 or 12.2