11i to R12 (12.1.

3) Real Experiences of a DBA
Kevin Dahl July, 2011

Presentor
•  •  •  •  •  •  •  •  • 

DBA 25+ Years worked in fortune 500 companies worked as consultant for 10+ years taught under graduate and graduate at university level as adjunct Oracle Apps DBA 20 Years System Architect Release 10.x to 12 RDBMS Version 7 to 11g middleware / Disco / SSO

2

Agenda
•  Presentation
–  –  –  –  –  –  –  –  Audience R12 Introduction Database Migration Required Word Size Change OATM Required High Availability Middle Tier Subledger Accounting Database, Application and Security patches

•  Wrap up

3

Application and Security patches 4 .•  Presentation –  –  –  –  –  –  –  –  Audience R12 Introduction Database Migration Required Word Size Change OATM Required High Availability Middle Tier Subledger Accounting Database.

Audience •  Audience –  This presentation is for Database Administrators 5 .

•  Presentation –  –  –  –  –  –  –  –  Audience R12 Introduction Database Migration Required Word Size Change OATM Required High Availability Middle Tier Subledger Accounting Database. Application and Security patches 6 .

and functionality enhancements into a consolidated.oracle.3 RUP R12 Introduction –  E-Business Suite Release Release Update Pack (12.•  R12. This release is a maintenance pack and can only be installed on top of an existing EBS 12.1 RUP3) (Patch 9239090) –  This release update pack (RUP) combines error corrections.com/stevenChan/entry/ebs_1213_available 7 . suite-wide patch set.1 environment –  http://blogs.1. statutory/regulatory updates.

3: Release Content Documents (Note 561580.Oracle E-Business Suite Release 12.1) •  what is new? See documentation Oracle E-Business Suite Release 12.3 RUP released in August 2010… –  new tech stack components: •  README .1.1.1) 8 .R12 Introduction •  R12.3 Readme (Note 1080973.1.

•  Presentation –  –  –  –  –  –  –  –  Audience R12 Introduction Database Migration Required Word Size Change OATM Required High Availability Middle Tier Subledger Accounting Database. Application and Security patches 9 .

Database Migration Required •  Are you changing platforms? –  database version •  a current. stable release is preferable –  database upgrade/migration timing •  11i release will determine timing –  migrate before or after R12 upgrade? •  tasks in test plan will impact timing –  database migration options •  transportable database •  export / import •  transportable tablespace 10 .

0.2.1.3 •  why upgrade database version? –  potential improvements that will assist in the database migration –  version current for anticipated upgrade to R12.1.2 is most recent certified version with EBusiness R12.Database Migration Required… •  Are you changing platforms? –  database version •  11.3 11 .

10 CU1 upgrade during R12 upgrade window –  recall that 11i release < 11.5.5.9 CU1.5. 11. and 11.5.10.10 base.2 •  tasks in test plan will impact timing –  technical testing must occur –  cursory functional testing must occur 12 . 11.9 CU2 and 11.10 CU2 may upgrade before or during R12 upgrade window –  11.9 must upgrade to 11.5.5.5.9 base.Database Migration Required… •  Are you changing platforms? –  database upgrade/migration timing •  11i release will determine timing –  migrate before or after R12 upgrade? –  11.5.

oracle. which we discuss later 13 .1) »  note you will only migrate the database. All other 11i components remain on their current platform –  don’t for get word size considerations. Use this query to deterimine: select platform_name from v$db_transportable_platform.0 or 11g (Doc ID 729309.Database Migration Required… •  Are you changing platforms? –  database migration options •  transportable database –  according to Steven Chan you can expect a 50% time reduction when compared to traditional export/import ( http://blogs. –  you would follow this note for the pre R12 migration: Using Transportable Database to migrate Oracle E-Business Suite 11i Using Oracle Database 10.2.com/stevenChan/entry/ transportable_database_11gr1_ebs) –  database platforms must have same endian format.

2.1) –  this can accommodate an upgrade. export / import may be your most reliable remaining option –  metalink note for 11g database and 11i: Export/import notes on Applications 11i Database 11g (Doc ID 557738.1 states: “The target (import to) ORACLE_HOME directory must be Oracle Database 11g (11.x)” –  don’t for get word size considerations.0).Database Migration Required… •  Are you changing platforms? –  database migration options •  export / import –  for those database source and target platforms that do not have the same endian format. which we discuss later 14 . or Oracle Database 11g (11. The source (export from) ORACLE_HOME directory must be either Oracle Database 10g Release 2 (10.x). Metalink note 557738.

1) describes the procedure. The procedure was released in April of 2010 –  transportable tablespace is an alternative to export / import when endian formats of the source and target are not the same –  it is not a given that transportable tablespace method will always work. It is slightly more complex than export / import –  don’t for get word size considerations. We’ve encountered situations where the target database was corrupted with no apparent resolution and had to fall back to the export / import approach –  metalink note Document TitleCross Platform Transportable Tablespaces on 11i with 10gR2 (Doc ID 454574.Database Migration Required… •  Are you changing platforms? –  database migration options •  transportable tablespace –  this is a relatively new approach in the context of E-Business suite. which we discuss later 15 .

Application and Security patches 16 .•  Presentation –  –  –  –  –  –  –  –  Audience R12 Introduction Database Migration Required Word Size Change OATM Required High Availability Middle Tier Subledger Accounting Database.

you are removing OLAP and AW components and then adding them back after the movement from 32-bit to 64-bit 17 .Word Size Change •  32-bit to 64-bit? –  change to 64-bit if necessary •  The entire R12 code set can be run on a 64-bit operating system –  make the change prior to R12 upgrade if criteria discussed on prior slides is met –  the word size change can be added to database upgrade and/or platform migration tasks –  refer to metalink note 352306.1 •  in a nutshell.

•  Presentation –  –  –  –  –  –  –  –  Audience R12 Introduction Database Migration Required Word Size Change OATM Required High Availability Middle Tier Subledger Accounting Database. Application and Security patches 18 .

OATM Required •  Oracle Application Tablespace Model (OATM) –  Required for R12 –  Save time from R12 outage by doing ahead of time –  there will be functional and technical testing (not significant) –  refer to metalink note 404954. There are hits on metalink for most issues although it is possible and SR would have to be opened 19 .1 –  the first test iteration of the OATM conversion will reveal potential issues.

2 can handle the latest OATM patches and by default has a fuller menu system •  migrate CTXSYS is available •  script generated to drop empty tablespaces –  benefits include a reorg and use of consistently larger tablespaces 20 .10.5.OATM Required… •  Oracle Application Tablespace Model (OATM) –  note that there are minimum 11i version requirements that must be met before OATM can be implemented –  11.

Application and Security patches 21 .•  Presentation –  –  –  –  –  –  –  –  Audience R12 Introduction Database Migration Required Word Size Change OATM Required High Availability Middle Tier Subledger Accounting Database.

High Availability Middle Tier •  post R12 upgrade step –  2 or application tiers would be created to support high availability –  parallel concurrent processing is configured to accommodate this availability –  shared application file system is desired from a maintenance perspective: Sharing The Application Tier File System in Oracle EBusiness Suite Release 12 (MN 384248.1) –  shared application file system must reside on a high availability storage device 22 .

•  Presentation –  –  –  –  –  –  –  –  Audience R12 Introduction Database Migration Required Word Size Change OATM Required High Availability Middle Tier Subledger Accounting Database. Application and Security patches 23 .

Subledger Accounting (SLA) •  SLA revealed –  From R12 Upgrade Guide •  “During the upgrade. as well as the necessary periods of the previous fiscal. to ensure that there are at least six periods included in the upgrade (occurs when the upgrade is performed in the first half of the fiscal year)” •  note the default number of periods above. existing accounting data from the subledgers is upgraded into the new Oracle Subledger Accounting data model. You will probably want additional periods upgraded 24 . the upgrade updates the data for the current fiscal year. By default.

Subledger Accounting (SLA)… •  SLA revealed –  the definition of a larger range of periods to be upgraded is very important because some of the Oracle Subledger Accounting functionality relies on the existence of previous accounting data –  if you need to change the default number of periods of historic data to be upgraded you must apply patch 5233248 to your release 11i APPL_TOP and submit the SLA pre-upgrade program •  see the upgrade guide for details 25 .

Application and Security patches 26 .•  Presentation –  –  –  –  –  –  –  –  Audience R12 Introduction Database Migration Required Word Size Change OATM Required High Availability Middle Tier Subledger Accounting Database.

oracle.com/technetwork/topics/ security/alerts-086861.1) (database and middleware patches) 27 . Apps and Security Patches •  R12 post upgrade patching –  patch current for application products you use –  patch current with regard to the security patches for the database and E-Busines suite –  refer to this url for security patches: http://http:// www.htmlwww.com/technetwork/topics/security/ alerts-086861.Database.html –  refer to metalink note for the security patches: •  Patch Set Update and Critical Patch Update April 2011 Availability Document (Doc ID 1291877.oracle.

html 28 . Apps and Security Patches •  April 2011 http://www.Database.com/technetwork/topics/security/cpuapr2011-301950.oracle.

Application and Security patches 29 .•  Wrap Up –  –  –  –  –  –  –  –  Audience R12 Introduction Database Migration Required Word Size Change OATM Required High Availability Middle Tier Subledger Accounting Database.

Thanks! kdahl@solutionbeacon.com .

Sign up to vote on this title
UsefulNot useful