R12 Upgrade Path

8/3/2019 R12 Upgrade Path

1/32

Thinking of Oracle ApplicationsRelease 12 Upgrade?

Things to do NOW in 11.5.x to be ready forupgrade to Release 12!!

Sushil Motwani,

Practice Director, DBA Services

Apps Associates LLC

November 10, 2008


2/32

Audience

This presentation is intended as a guide for thedatabase administrator and the applicationspecialists who are responsible for upgrading toRelease 12 of Oracle Applications. This mayinclude:

Release Management Managers

NEOAUG November 2008 2

Project ManagersOracle Applications Developers

Technical Application Specialists andOF COURSE

Oracle DBAs and Applications DBAs (Cananyone do without them? )


3/32

Agenda

Current 11i Certifications

Current Release 12 CertificationsSteps we can do NOW before Release 12

Certified Upgrade Path (Pre 12.0.4 and 12.0.4)

Database Upgrade Considerations


ecommen e ec no ogy ac pgra esoOATM

oNative Sun JRE

oMulti-Org

Patching to stay certified

On-Going and Future Steps before an actualupgrade


4/32

Release 11i Certified Components .

Database Tier9i 11g (9.2.0.8 11.1.0.6)

Non-OATM (separate tablespaces for each product installed)OATM (Oracle Applications Tablespace Management)

OATM available out-of-the-box with 11.5.10 Rapid Install.

OATM Migration Utility available for earlier 11i releases

Pre-requisite of 11i.AD.H minipack and a minimum database


. . . .

Release 10.7 or 11.0 customers, upgrading to Release 11ican also use the OATM Migration utility.

Database Specific Technologies like

RAC (Real Application Clusters) 9i 11g

TDE (Transparent Data Encryption) 10g

Database Vault 10g

Physical Standby Databases 9i 10gASO / ANO (Advanced Security/Networking Option) >10.2.0.3

Advanced Compression

Database Partitioning


5/32

Release 11i Certified Components

Applications TierOracle Application Server 1.0.2.2.2

Oracle Home 8.1.7.4

Apache Web Server (HTML/JSP/Jserv) 1.3.19

Developer /2000 Patchsets 15 19

Oracle Home 8.0.6.3

JDK 1.3 6


JDBC Drivers 9.2.0.8

Oracle Application Java Framework 5.10

Workflow 2.6.3

Desktop TierWindows 2000, XP, XP Service Pack 2 (SP2), XP Service Pack 3(SP3), Vista Service Pack 1 (SP1)

Oracle JInitiator 1.1.8.22 through 1.1.8.27; 1.3.1.21 through1.3.1.30 Not on Vista

Sun JRE 1.5.0_12 and higher, 1.6.0_03

Browsers: Internet Explorer 6, 7; Firefox 2,

Mac OS X 10.4 (Tiger) with Safari 2


6/32

Release 12 Certified Components .

Database Tier10g 11g (10.2.0.2 11.1.0.6)

OATM (Oracle Applications Tablespace Management)

Database Specific Technologies like

RAC (Real Application Clusters) 10g 11g

TDE (Transparent Data Encryption) 10g

Database Vault 10g


Physical Standby Databases 10g

ASO / ANO (Advanced Security/Networking Option) 10.2.0.4

Advanced Compression

Database Partitioning


7/32

Release 12 Certified Components

Applications TierOracle Application Server 10gAS 10.1.3.0.0 and 10.1.3.3

Forms / Reports 10g 10.1.2.0.2 and 10.1.2.2

Oracle Jdeveloper 10.1.3

JDK 5, 6

Oracle Application Java Framework 5.10

Workflow 2.6.3


Desktop TierWindows 2000, XP, XP Service Pack 2 (SP2), XP Service Pack 3(SP3)

Sun JRE 1.5.0_12 and higher, 1.6.0_03

Browsers: Internet Explorer 6, 7; Firefox 2

Windows Vista, Vista Service Pack 1(SP1)Sun JRE 1.5.0_12 and higher, 1.6.0_03

Browsers: Internet Explorer 6, 7; Firefox 2

Mac OS X 10.4 (Tiger) with Safari 2


8/32

External Certifications Release 11i .

External to Oracle Applications Tech StackOracle Internet Directory 3.0.1, 10.1.2.0.2, 10.1.2.2, 10.1.2.3 ,

10.1.4.0.1, 10.1.4.2Single Sign-On 3.0.9, 10.1.2.0.2, 10.1.2.2, 10.1.2.3, 10.1.4.0.1,10.1.4.2

Portal 3.0.9, 10.1.2.0.2, 10.1.2.2, 10.1.2.3, 10.1.4.0.1, 10.1.4.1

Discoverer 4i, 10.1.2.0.2, 10.1.2.2, 10.1.2.3, and Cumulative Patchsets


. . . . , . . . .

Oracle Business Intelligence Applications 7.9.4Web Cache 10.1.2.0.2, 10.1.2.2, 10.1.2.3

Oracle Access Manager (via Oracle SSO Integration): 10.1.4.0.1,10.1.4.2

Oracle Identity Manager Connector Pack 9.0.4, 9.1.0

Enterprise Single Sign-On 10.1.4.0.1 (via Oracle SSO Integration)

Identity Federation 10.1.4.2 (via Oracle SSO Integration)Oracle Virtual Directory 10.1.4.2 (via Oracle Internet Directoryintegration)

Oracle SOA Suite 10.1.3.3

Oracle Application Server (SOA) Adapter for Oracle Applications10.1.3.3


9/32

External Certifications Release 12 .

External to Oracle Applications Tech StackOracle Internet Directory 10.1.2.0.2, 10.1.2.2, 10.1.2.3, 10.1.4.0.1,

10.1.4.2Single Sign-On 10.1.2.0.2, 10.1.2.2, 10.1.2.3, 10.1.4.0.1, 10.1.4.2

Portal 10.1.2.0.2, 10.1.2.2, 10.1.2.3, 10.1.4.1, 10.1.4.2

Discoverer 4i, 10.1.2.0.2, 10.1.2.2, 10.1.2.3, and Cumulative Patchsets

Oracle Business Intelligence Enterprise Edition 10.1.3.3.1, 10.1.3.3.2


rac e us ness n e gence pp ca ons . .

Web Center 10.1.3.3

Web Cache 10.1.2.0.2, 10.1.2.2, 10.1.2.3

Oracle Access Manager (via Oracle SSO Integration): 10.1.4.0.1,10.1.4.2

Oracle Identity Manager Connector Pack 9.0.4, 9.1.0

Enterprise Single Sign-On 10.1.4.0.1 (via Oracle SSO Integration)

Identity Federation 10.1.4.2 (via Oracle SSO Integration)

Oracle Virtual Directory 10.1.4.2 (via Oracle Internet Directoryintegration)

Oracle SOA Suite 10.1.3.3

Oracle Application Server (SOA) Adapter for Oracle Applications10.1.3.3


10/32

What can we do NOW ?

Prepare for an Eventual Upgrade to Release 12Steps that SHOULD be done before the upgrade

Upgrade the Database to at least 10g (if you can )

Apply at least 11i.AD.I patch

Convert to OATM

Replace Oracle Jinitiator with the Sun JRE

Convert to Multi-Org


Steps that CAN be done before the upgrade

Implement latest database features on your current version

Make sure that you are on certified components of the technologystack. A Release Management Process could be initiated.

Implement Shared and/or Staged APPL_TOP for multi-tiersystems

Calculate and purchase all the hardware that will be used

eventually for the upgradeConvert customized reports to use BI Publisher and many more..

Steps that CANNOT be done before the upgrade

Upgrade the technology stack iAS and Forms to 10.1.3 and 10.1.2respectively


11/32

Certified Upgrade Path (Pre 12.0.4)



12/32

Certified Upgrade Path (12.0.4 onwards)



13/32

Database Upgrade Considerations

In Release 12 of Oracle Applications, the minimumcertified version is:

10.2.0.2 Release 12.0.0 and Release 12.0.1

10.2.0.3 and up Release 12.0.2 and up

11.1.0.6 Release 12.0.4 and up

To complete the upgrade to Release 12.0.4 or


higher, you MUST migrate or upgrade yourdatabase at least to Oracle 10g Release 2(10.2.0.3):

Release 11.5.9 CU2 and 11.5.10 CU2 Upgrade to10.2.0.3 or higher, if possible, BEFORE ApplicationsUpgrade

Release 11.5.8, 11.5.9 base, 11.5.9 CU1, 11.5.10 base, and11.5.10 CU1 Database Upgrade is possible only duringApplications Upgrade

Please refer to Metalink Note: 403339.1 for Database UpgradeMethodology


14/32

OATM Oracle Application Tablespace

Management .

Non OATM DisadvantagesPart of Oracle Applications from earlier releases prior to 11.5.10

Separate Tablespace for each product (1 for Data and 1 for Index)Earlier versions created the tablespaces in Dictionary Managed

Converting to Locally Managed does not convert existing data /tables to Locally Managed

Data could be several years old and extremely fragmented


OATM AdvantagesOATM available out-of-the-box with 11.5.10 Rapid Install.Now the default for all 11.5.10+ releases

OATM Migration Utility available for earlier 11i releases

Release 10.7 or 11.0 customers, upgrading to Release 11i canalso use the OATM Migration utility.

The new tablespaces can be created as Locally Managed usingAutomatic Extent Management / Uniform Extent Management andAutomatic Segment Space Management (ASSM)

All the existing data is moved into these tablespaces, eliminatingfragmentation for the existing data, as well as new data

Significant Reduction is number of Tablespaces


15/32


Management .

Implementation of OATMIn Oracle Applications, Metalink uses the Term Tablespace

Migration Utility (TMU)Originally available in a patch 3381489, now beensuperseded by 3942506

Under the OATM the following tablespaces are created as adefault.


APPS_TS_TX_DATA - This tablespace hold thetranslational tables of all Oracle Applications products.

APPS_TS_TX_IDX - All the indexes on the product tablesare kept under this tablespace.

APPS_TS_SEED - The seeded data that is setup andreference data tables and indexes form this tablespace.

APPS_TS_INTERFACE - All the interface tables are keptin this tablespace

APPS_TS_SUMMARY - All objects that record summaryinformation are grouped under this tablespace.


16/32


Management .

Implementation of OATM (Contd )APPS_TS_NOLOGGING - This tablespace contains the

materialized views that are used for summary purposesand other temporary object that do not require redo logentries.

APPS_TS_QUEUES - The advanced queue tables andrelated objects form a part of this tablespace.


APPS_TS_MEDIA - This tablespace holds multimediaobjects like graphics, sound recordings and spatial data.

APPS_TS_ARCHIVE - Tables that are obsolete in thecurrent release of Oracle Applications 11i are stored here.

APPS_TS_TOOLS Not created by default by OATMutility. Required, once on ATG Rollup 4 or higher.


17/32

Replacing Oracle Jinitiator with Sun JRE

(Native Plug-In)

Overview of Implementation of Sun JREAs per Oracle - Oracle recommends that Oracle E-Business

Suite 11i customers move to the latest and therefore mostsecure certified version of the Sun JRE Native Plug-in oneither Java family (JRE 5.0.x or JRE 6.0.x).

Majority of Oracle E-Business Suite currently use OracleJinitiator to access Forms Based Applications


,

Forms Based Applications with either Oracle Jinitiator, thenative Sun JRE or a mix of the two technologies

Disadvantages of Oracle JInitiatorSeveral version of Oracle Jinitiator have conflicts with JVM.

As newer JVMs get installed, the current version of OracleJinitiator may not be compatible

Managing multiple JVMs, and conflicts with Oracle Jinitiatormakes the desktop Maintenance a nightmare, as well asdealing with updating the Oracle Jinitiator version

Implementation of Sun JRE eliminates all of the above

Oracle Jinitiator gets decertified as of June 2009


18/32

Replacing Oracle Jinitiator with Sun JRE

(Native Plug-In)

Implementation/Installation of Sun JRE

Minimum Version Restrictions

Oracle Applications 11.5.9 or later

Developer / 2000 Patchset 18 or later(6.0.8.27.x) Recommended Patchset 19(6.0.8.28.x)


JRE 1.5.0_12 or later, JRE 1.6.0_03 or later

AutoConfig Enabled

Installation of the Oracle E-Business SuiteInteroperability Patch 6863618

Installation of the Native Sun JRE Plug-In on the

Web Server


19/32

Converting the Oracle Applications to

Multi-Org

Facts about Multi-OrgNon Multi-Org implementations are supported in 11i, as

long as 11i is supportedMulti-Org allows users to define one or more OperatingUnits, and to secure setups and transactions byoperating unit. Each responsibility is linked to oneoperating unit, and each operating unit is linked to one


enera e ger set o oo s

Release 12 needs Multi-Org enabled. With Release 12,Multi-Org Access Control, which enables an applicationsresponsibility to access multiple operating units if desired

Converting to Multi-Org does not require the use ofmultiple operating units or sets of books, but it doesenable you to use multiple operating units and sets ofbooks if desired.

New features introduced in Release 11i may requireconversion to Multi-Org in order to improve performanceacross the E-Business Suite


20/32

Converting the Oracle Applications to

Multi-Org

Implementation of Multi-OrgBefore Conversion to Multi-Org

Apply AD Patch 2412194, performance improvement patch

Define at least one Operating Unit, and set the profile option MO:Operating Unit at Site Level, to the Operating Units value

Conversion to Multi-OrgUsing ADADMIN , use the Convert to Multi-Org. Option available


ONLY if you do not have Multi-Org enabled

During the conversion processThe ORG_ID column gets populated with the Operating Unitvalue defined in the profile option

The MULTI_ORG_FLAG column in theFND_PRODUCT_GROUPS changes to Y

The Replicate Seed Data program runs, which for each

operating unit definedPost-Conversion to Multi-Org

Apply patch 2451368 to fix a bug associated with the Multi-OrgConversion


21/32

10g /9i Database Features Implementation

Depending on the version of Database, somefeatures that enhance the features provided by the

database:For 11.5.9 and 11.5.10.x, convert to use CBO instead of RBO, andregularly update the statistics of the data dictionary and APPSTables

In the parameter file, refer to Metalink Note: 216205.1 for specific


va ues, u use _ , ns ea o _ _ ,

DB_BUFFER_CACHE etc.Use PGA_AGGREGATE_SIZE instead of SORT_AREA_SIZE,HASH_AREA_SIZE

Convert the SYSTEM Tablespace to Locally Managed, and createall subsequent tablespaces as Locally Managed, with AutomaticExtent Allocation and Automatic Segment Space Management

Replace the Rollback Segments with the UNDO Tablespace

Replace the Temporary Tablespace to use TEMPFILES instead ofthe traditional TEMP Permanent Tablespace

Keep up-to-date on all the latest CPUs (Critical Patch Updates) onthe Database


22/32

Upgrading Oracle Applications to

Certified Tech Stack Components

Ensure that your environment is running oncertified technology components

To achieve the above, one has to patch regularly.

Here are some myths about patching (as per Steven Chan fromOracle):

We Can't Upgrade Because...


It requires too much downtime NOT True planned

downtimes are better than unplannedTesting is too expensive NOT True BIG Bang upgradesrequire much more testing in man hours

It's too complicated NOT True Being not certified causesmuch more complications with patching Ask the DBAs

We don't have enough staff Bigger upgrades require more

staff during testingIt ain't broken; why fix it? Primary Reason why companiesdo not upgrade ? What happens when something reallybreaks, and Oracle does NOT help !!!!!

SO, If you're in a hole, it's never too late to stop digging


23/32

Release Management Process/Regular

Patching Process

What is Release Management Process Model?


CustomDevelopment

Unit Testing ofCustomizations

DBA installationof patches

DBA installationof patches

Developer testingof installationscripts forcustomizations

System testing forrelease cycle

DBA installationof customizationsand patches

Integrationtesting for release

cycle

Final installationofcustomizationsand patches

Final blessing ofnew release


24/32

Release Management Process/Regular

Patching Process

What does the DBAs do in a Release ManagementProcess?

At the end of every Release Cycle, the DBAs look at the certifymatrix in Metalink to determine any upcoming de-certifications orupgrades. The following patches must always be looked at:

Latest Security Alerts for DB Tier and Application Tier

Latest AD.I patch


a es ap one a c es

Latest Autoconfig PatchesLatest ATG Patches

Latest OAM Patches

Latest Family Packs (Use patchsets.sh)

Certified components in 11i that will be used in Release 12/Fusion

Verify that all the technology stack components currently are

certified, and if any of them will be decertified. These include:Developer 2000 version

Oracle Jinitiator/Sun JRE

Oracle Discoverer

Oracle iAS Application Server/HTTP Server


25/32

Downtime Reduction during Patching

Use Latest Available Features for Patching,depending on the ATG Patch Level

Merge multiple patches into smaller number ofpatches using AD Merge. Pre-requisites cannot bemerged with a patch, for which it is a pre-requisite,but all the pre-requisites of multiple patches can be


AD Patch can be run in non-interactive mode, bycreation of defaultsfile, and then creating batchprograms which will runs series of patches oneafter the other without asking any questions.

Use options like nocompiledb, which will not

compile all objects every time it applies a patch.Only the last patch can have the compiledboption.


26/32

Downtime Reduction during Patching

Use Latest Available Features for Patching,depending on the ATG Patch Level

Oracle now supports the Shared Application-TierSystem. If you have multiple Application Servers usingLoad Balancing, then all the servers can share onesingle shared Application-Tier. Use Metalink Note:233428.1 for 11i and 384248.1 for Release 12. Patches


applied to shared application tiers are instantlyavailable to all application tiers

Shared application tier systems, distributed AD (Note:236469.1) can be used to run adpatch and adctrl onmultiple nodes, that share the application tier filesystem

Staged Application Systems (I personally do notprefer it) Metalink Note: 242480.1, where patches areapplied to a stage area, before the productionupgrade, and then only the database portion is appliedon the Production Instance thus reducing downtime


27/32

Upcoming/Current De-certifications .

Firefox 2.0 December 2008

Oracle Jinitiator 1.1.8 December 2008

Oracle Jinitiator 1.3.1 July 2009

11.5.9 Premier Support June 2008 Now in ExtendedSupport

11.5.10 Premier Support November 2010


J2SE 1.4.x October 2008

J2SE 1.3.x December 2006


28/32

Upcoming/Current Decertifications .



29/32

Summary

For each version of OracleApplications there are severalcertification levels for eachtechnology component

Depending on your current version,


the upgrade path will be different Ensure that we stay certified at all

times

Getting a Release Management

Process to ensure a stableenvironment, and subsequentupgrades easier


30/32

Q


A


31/32

Speaker Profile

Sushil Motwani is the Practice Director of DBAServices at Apps Associates LLC. He manages

team of Database Administrators providing on-site and offshore (remote) services to ourclients. Sushil has over 15 years experienceprimarily as an Oracle DBA including 10 years


as an rac e pp ca ons m n s ra or .

Before his current position, Sushil was a Lead/Sr.Oracle DBA/Applications Administrator for 6 years at Harvard University.

Sushil has presented papers at several OAUG andNEOAUG conferences.


32/32

Thank You

Suggestions or Additional Questions


. .

Documents

R12 Upgrade Path