neoaug things to do now before upgrading to release 12 ... · 10g 11g (10.2.0.2 11.1.0.6) oatm...

Thinking of Oracle ApplicationsRelease 12 Upgrade?

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

Sushil Motwani,

Practice Director, DBA Services

Apps Associates LLC

November 10, 2008

Audience

This presentation is intended as a guide for the database administrator and the application specialists who are responsible for upgrading to Release 12 of Oracle Applications. This may include:

�Release Management Managers

NEOAUG November 2008 2

�Project Managers

�Oracle Applications Developers

�Technical Application Specialists andOF COURSE

�Oracle DBAs and Applications DBAs (Can anyone do without them? )

Agenda

�Current 11i Certifications

�Current Release 12 Certifications

�Steps we can do NOW before Release 12

�Certified Upgrade Path (Pre 12.0.4 and 12.0.4)

�Database Upgrade Considerations

Recommended Technology Stack Upgrades


�Recommended Technology Stack Upgrades

oOATM

oNative Sun JRE

oMulti-Org

�Patching to stay certified

�On-Going and Future Steps before an actual upgrade

Release 11i Certified Components ….

Database Tier�9i �� 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 version of 9.2.0.4.


version of 9.2.0.4.

�Release 10.7 or 11.0 customers, upgrading to Release 11i can 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 �� 10g

�ASO / ANO (Advanced Security/Networking Option) >10.2.0.3

�Advanced Compression

�Database Partitioning

Release 11i Certified Components

Applications Tier�Oracle 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


�JDBC Drivers 9.2.0.8

�Oracle Application Java Framework 5.10

�Workflow 2.6.3

Desktop Tier�Windows 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 through 1.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

Release 12 Certified Components ….

Database Tier�10g �� 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


�Physical Standby Databases 10g

�ASO / ANO (Advanced Security/Networking Option) 10.2.0.4

�Advanced Compression

�Database Partitioning

Release 12 Certified Components

Applications Tier�Oracle 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 Tier�Windows 2000, XP, XP Service Pack 2 (SP2), XP Service Pack 3 (SP3)


�Browsers: Internet Explorer 6, 7; Firefox 2

�Windows Vista, Vista Service Pack 1(SP1)


�Browsers: Internet Explorer 6, 7; Firefox 2

�Mac OS X 10.4 (Tiger) with Safari 2

External Certifications Release 11i ….

External to Oracle Applications Tech Stack�Oracle 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.2

�Single 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 Enterprise Edition 10.1.3.3.1, 10.1.3.3.2



�Oracle Business Intelligence Applications 7.9.4

�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 Directory integration)

�Oracle SOA Suite 10.1.3.3

�Oracle Application Server (SOA) Adapter for Oracle Applications 10.1.3.3

External Certifications Release 12 ….

External to Oracle Applications Tech Stack�Oracle Internet Directory 10.1.2.0.2, 10.1.2.2, 10.1.2.3, 10.1.4.0.1, 10.1.4.2

�Single 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 Applications 7.9.4


�Oracle Business Intelligence Applications 7.9.4

�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 Directory integration)

�Oracle SOA Suite 10.1.3.3

�Oracle Application Server (SOA) Adapter for Oracle Applications 10.1.3.3

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


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 technology stack. A Release Management Process could be initiated.

�Implement Shared and/or Staged APPL_TOP for multi-tier systems

�Calculate and purchase all the hardware that will be used eventually for the upgrade

�Convert 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.2 respectively

Certified Upgrade Path (Pre 12.0.4)


Certified Upgrade Path (12.0.4 onwards)


Database Upgrade Considerations

In Release 12 of Oracle Applications, the minimum certified 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 your


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

�Release 11.5.9 CU2 and 11.5.10 CU2 �� Upgrade to 10.2.0.3 or higher, if possible, BEFORE Applications Upgrade

�Release 11.5.8, 11.5.9 base, 11.5.9 CU1, 11.5.10 base, and 11.5.10 CU1 �� Database Upgrade is possible only during Applications Upgrade

Please refer to Metalink Note: 403339.1 for Database Upgrade Methodology

OATM – Oracle Application Tablespace

Management ….

Non OATM Disadvantages�Part 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 Advantages


OATM Advantages�OATM 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 can also use the OATM Migration utility.

�The new tablespaces can be created as Locally Managed using Automatic Extent Management / Uniform Extent Management and Automatic Segment Space Management (ASSM)

�All the existing data is moved into these tablespaces, eliminating fragmentation for the existing data, as well as new data

�Significant Reduction is number of Tablespaces


Management ….

Implementation of OATM �In Oracle Applications, Metalink uses the Term “Tablespace Migration Utility (TMU)

�Originally available in a patch “3381489”, now been superseded by “3942506”

�Under the OATM the following tablespaces are created as a default.


default.

�APPS_TS_TX_DATA - This tablespace hold the translational tables of all Oracle Applications products.

�APPS_TS_TX_IDX - All the indexes on the product tables are kept under this tablespace.

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

�APPS_TS_INTERFACE - All the interface tables are kept in this tablespace

�APPS_TS_SUMMARY - All objects that record summary information are grouped under this tablespace.


Management ….

Implementation of OATM (Contd …)�APPS_TS_NOLOGGING - This tablespace contains the materialized views that are used for summary purposes and other temporary object that do not require redo log entries.

�APPS_TS_QUEUES - The advanced queue tables and related objects form a part of this tablespace.


�APPS_TS_MEDIA - This tablespace holds multimedia objects like graphics, sound recordings and spatial data.

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

�APPS_TS_TOOLS – Not created by default by OATM utility. Required, once on ATG Rollup 4 or higher.

Replacing Oracle Jinitiator with Sun JRE

(Native Plug-In)

Overview of Implementation of Sun JRE�As per “Oracle” - Oracle recommends that Oracle E-Business Suite 11i customers move to the latest and therefore most secure certified version of the Sun JRE Native Plug-in on either Java family (JRE 5.0.x or JRE 6.0.x).

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

With the Native Sun JRE, Oracle now supports access to


�With the Native Sun JRE, Oracle now supports access to Forms Based Applications with either Oracle Jinitiator, the native Sun JRE or a mix of the two technologies

Disadvantages of Oracle JInitiator�Several version of Oracle Jinitiator have conflicts with JVM.

�As newer JVMs get installed, the current version of Oracle Jinitiator may not be compatible

�Managing multiple JVMs, and conflicts with Oracle Jinitiator makes the desktop Maintenance a nightmare, as well as dealing with updating the Oracle Jinitiator version

�Implementation of Sun JRE eliminates all of the above

�Oracle Jinitiator gets decertified as of June 2009

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


�JRE 1.5.0_12 or later, JRE 1.6.0_03 or later

�AutoConfig Enabled

�Installation of the Oracle E-Business Suite Interoperability Patch “6863618”

�Installation of the Native Sun JRE Plug-In on the Web Server

Converting the Oracle Applications to

Multi-Org

Facts about Multi-Org�Non Multi-Org implementations are supported in 11i, as long as 11i is supported

�Multi-Org allows users to define one or more Operating Units, and to secure setups and transactions by operating unit. Each responsibility is linked to one operating unit, and each operating unit is linked to one General Ledger set of books


General Ledger set of books

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

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

�New features introduced in Release 11i may require conversion to Multi-Org in order to improve performance across the E-Business Suite

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 Unit’s value

Conversion to Multi-Org

�Using ADADMIN , use the Convert to Multi-Org. Option available ONLY if you do not have Multi-Org enabled


ONLY if you do not have Multi-Org enabled

�During the conversion process

�The ORG_ID column gets populated with the Operating Unit value defined in the profile option

�The MULTI_ORG_FLAG column in the FND_PRODUCT_GROUPS changes to “Y”

�The Replicate Seed Data program runs, which for each operating unit defined

Post-Conversion to Multi-Org

�Apply patch “2451368” to fix a bug associated with the Multi-Org Conversion

10g /9i Database Features Implementation

Depending on the version of Database, some features that enhance the features provided by the database:

�For 11.5.9 and 11.5.10.x, convert to use CBO instead of RBO, and regularly update the statistics of the data dictionary and APPS Tables

�In the parameter file, refer to Metalink Note: 216205.1 for specific values, but use SGA_TARGET, instead of SHARED_POOL_SIZE,


values, but use SGA_TARGET, instead of SHARED_POOL_SIZE, DB_BUFFER_CACHE etc.

�Use PGA_AGGREGATE_SIZE instead of SORT_AREA_SIZE, HASH_AREA_SIZE

�Convert the SYSTEM Tablespace to Locally Managed, and create all subsequent tablespaces as Locally Managed, with Automatic Extent Allocation and Automatic Segment Space Management

�Replace the Rollback Segments with the UNDO Tablespace

�Replace the Temporary Tablespace to use TEMPFILES instead of the traditional TEMP Permanent Tablespace

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

Upgrading Oracle Applications to

Certified Tech Stack Components

Ensure that your environment is running on certified technology components

To achieve the above, one has to patch regularly.

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

“We Can't Upgrade Because...”


� It requires too much downtime – NOT True – planned downtimes are better than unplanned

�Testing is too expensive – NOT True – BIG Bang upgrades require much more testing in man hours

�It's too complicated – NOT True – Being not certified causes much more complications with patching – Ask the DBAs ☺☺☺☺

�We don't have enough staff – Bigger upgrades require more staff during testing

�It ain't broken; why fix it? – Primary Reason why companies do not upgrade ? What happens when something really breaks, and Oracle does NOT help !!!!!

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

Release Management Process/Regular

Patching Process

What is Release Management Process Model?

�Development �Patch/Test �Test/UAT �Production


�Development

• Custom Development

• Unit Testing of Customizations

• DBA installation of patches

�Patch/Test

• DBA installation of patches

• Developer testing of installation scripts for customizations

• System testing for release cycle

�Test/UAT

• DBA installation of customizations and patches

• Integration testing for release cycle

�Production

• Final installation of customizations and patches

• Final blessing of new release

Release Management Process/Regular

Patching Process

What does the DBAs do in a Release Management Process?

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

�Latest Security Alerts for DB Tier and Application Tier

�Latest AD.I patch

Latest Rapid Clone Patches


�Latest Rapid Clone Patches

�Latest Autoconfig Patches

�Latest 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

Downtime Reduction during Patching

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

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


merged

�AD Patch can be run in non-interactive mode, by creation of defaultsfile, and then creating batch programs which will runs series of patches one after 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 “compiledb” option.

Downtime Reduction during Patching

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

�Oracle now supports the Shared Application-Tier System. If you have multiple Application Servers using Load Balancing, then all the servers can share one single shared Application-Tier. Use Metalink Note: 233428.1 for 11i, and 384248.1 for Release 12. Patches


233428.1 for 11i, and 384248.1 for Release 12. Patches applied to shared application tiers are instantly available to all application tiers

�Shared application tier systems, distributed AD (Note: 236469.1) can be used to run adpatch and adctrl on multiple nodes, that share the application tier file system

�Staged Application Systems (I personally do not prefer it) Metalink Note: 242480.1, where patches are applied to a stage area, before the production upgrade, and then only the database portion is applied on the Production Instance thus reducing downtime

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 Extended Support

�11.5.10 – Premier Support – November 2010


�J2SE 1.4.x – October 2008

�J2SE 1.3.x – December 2006

Upcoming/Current Decertifications ….


Summary

� For each version of Oracle Applications there are several certification levels for each technology component

� Depending on your current version, the upgrade path will be different


the upgrade path will be different

� Ensure that we stay certified at all times

� Getting a Release Management Process to ensure a stable environment, and subsequent upgrades easier

Q&A


Q&A

Speaker Profile

Sushil Motwani is the Practice Director of DBA Services at Apps Associates LLC. He manages team of Database Administrators providing on-site and offshore (remote) services to our clients. Sushil has over 15 years experience primarily as an Oracle DBA including 10 years as an Oracle Applications Administrator/DBA.


as an Oracle Applications Administrator/DBA.

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 and NEOAUG conferences.

Thank You

Suggestions or Additional Questions

[email protected]


[email protected]

neoaug things to do now before upgrading to release 12 ... · 10g 11g (10.2.0.2 11.1.0.6) oatm...

Documents