Upgrading 11i E-business Suite to R12 E-business Suite
•Download as PPT, PDF•
6 likes•4,641 views
Planning for an upgrade Preparing for Upgrade Upgrading to R12 Post Upgrade Tasks
![Objective ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Upgrading 11i E-business Suite to R12 E-business Suite
Similar to Upgrading 11i E-business Suite to R12 E-business Suite (20)
More from iWare Logic Technologies Pvt. Ltd.
More from iWare Logic Technologies Pvt. Ltd. (20)
Upgrading 11i E-business Suite to R12 E-business Suite
- 1. Upgrading 11i EBS to R12 Webinar
- 6. Best Practice for Upgrade Phase 1: DB Upgrade Phase 2: Apps Upgrade Phases may happen in Separate critical downtimes Dual-Phase Upgrade Single-Phase Upgrade Apps and DB Upgrades must be completed during the same critical downtimes 11.5.1-11.5.6 Upgrade to 11.5.10.2 11.0 Upgrade to 11.5.10.2 11.5.7 11.5.8 9iR2 11.5.9cu2 11.5.10.2 9iR2,10gR1 R12 10gR2 11.5.9(cu1) 11.5.10(cu1) 9iR2,10gR1 Not certified on 10gR2 Certified on 10gR2 Upgrade Target (R12)
- 7. Oracle Application Upgrade Path Release level Upgrade path 11.0 Release 11.5.10.2 Release 12.1.1 11.5.1 – 11.5.8 Release 11.5.10 CU2 Release 12.1.1 11.5.9, or 11.5.10 (base, CU1,CU2) Release 12.1.1
- 16. Select the path to upgrade E-Business Suite Releases Available Paths 11.5.9 (base or CU1) with 9.2.0.x or 10.1.0.x database Path A 11.5.9 CU2 with 9.2.0.x or 10.1.0.x database Path A or Path B 11.5.9 CU2 with 10.2.0.2 database Path B 11.5.9 CU2 with 10.2.0.3 database Path B or Path D 11.5.9 CU2 with 10.2.0.4 database Path B or Path D 11.5.10 (base or CU1) with 9.2.0.x or 10.1.0.x database Path A 11.5.10.2 with 9.2.0.x or 10.1.0.x database Path A, Path B, or Path C 11.5.10.2 with 10.2.0.2 database Path B or Path C 11.5.10.2 with 10.2.0.3 database Path B, Path C, or Path D 11.5.10.2 with 10.2.0.4 database Path C or Path D 11.5.10.2 with 11.1.0.6 database Path C or Path E 11.5.10.2 with 11.1.0.7 database Path C or Path E 11.5.10.2 with 11.2.0.1 database Path E
- 17. Preparing for the Upgrade
- 24. Run Rapidwiz
- 25. Run rapidwiz: Select Upgrade Action Cont..
- 30. Step 6: Migrate or upgrade your database to at least Oracle 10g Release 2 Oracle Application 11.5.9 with CU 2 Oracle Application 11.5.10 With CU 2 Oracle Database 10gR2 Oracle Database 11g Certified with Certified with Certified with
- 34. Upgrade Process
- 42. Finishing Upgrade Cont.. /oracle/erptest/appl/inst/apps//iware_erptest/appl/admin/iware_
- 46. Post – Upgrade Tasks
- 51. Upgrade R12.x.x to R12.1.1 R12.0.1 – R12.0.6 R12.1.1 R12.1.X 11.5.7 – 11.5.10.2
- 53. Metalink References Details Doc Id Estimate tablespace sizes for test upgrade 399362.1 E-Business Suite Release 12 Upgrade Sizing and Best Practices 399362.1 Initialization parameters 396009.1 Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade 761570.1 Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0) 452783.1 Oracle E-Business Suite Readme, Release 12.1.2 949406.1 Oracle 10gR2 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 upgrade 403339.1 Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1.1 Upgrade 761570.1
Editor's Notes
- Release 11.5.10 CU2 > Release 12.1.1 Upgrading Oracle Applications, Release 11.5.10.2 > Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1 Release 11.5.10 CU2 > Release 12.1.1 Maintenance Pack Installation Notes, Release 11.5.10 CU2 (Doc ID: 289788.1) > Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1 . Release 12.1.1 Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1 .
- For Example: A test upgrade of the largest Oracle production system (oraprod) used the following CPUs: • Database tier machine - 24 CPUs (900 MHz SUNW, UltraSPARC-III+) • Application tier machine - 4 CPUs (3.05 GHz Intel Xeon) A test upgrade of the Vision database and application tier machine used 4 CPUs (3.05 GHz Intel Xeon). Note: See E-Business Suite Release 12 Upgrade Sizing and Best Practices (Doc ID: 399362.1) for the statistics on these production system upgrades. Memory To calculate the memory requirements for an upgrade, consider the following: • Number of concurrent users • Infrastructure requirements for multi-tiered architecture For Example A test upgrade of the largest Oracle production system (oraprod) used the following: • Database tier machine - 48 GB of memory
- To estimate the increase in required disk space for upgrading, consider the products, the number of languages being installed, and changes in the data model For Example In a test upgrade of the largest Oracle production system (oraprod), the database increased 10-20 percent. In a test upgrade, the Vision database increased 5 percent. For guidelines based on an upgrade of the Oracle production system (oraprod), see E-Business Suite Release 12 Upgrade Sizing and Best Practices (Doc ID: 399362.1).
- This release uses the Oracle Applications Tablespace Model (OATM), which is based on database object type rather than product affiliation. OATM uses 12 locally managed tablespaces for all products, including the temporary tablespace, system tablespace, and system-managed undo (SMU) tablespace. Each database object is mapped to a tablespace based on its input/output characteristics, including object size, life span, access methods, and locking granularity. Oracle has successfully tested systems with extent sizes of 128 K for small systems (100 GB database) and 4-10 MB for large, multi-terabyte database systems. We supply scripts in the upgrade process to create the tablespaces for all new products and configure the database for the new tablespace model. Then, the upgrade process creates the new objects. However, your existing objects are not automatically migrated. We strongly recommend that you migrate the existing objects after the upgrade is complete. Use the Tablespace Migration Utility (introduced in Release 11i) to perform this task
- Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1.1 Upgrade ID 761570.1 Oracle 10gR2 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade ID 403339.1
- The TUMS report lists tasks that you can omit from the upgrade because they do not apply to your system (for example, a task required for a product that you do not use or for applying a patch that you have previously applied). TUMS is delivered in a patch, which supplies the scripts you need to examine your system and create the report. We strongly recommend you create and review the TUMS report before you begin the upgrade
- Refer : Oracle Applications Developer's Guide
- Set the schema name to ALL to gather statistics for all Oracle Applications schemas (having an entry in the FND_PRODUCT_INSTALLATIONS table). In addition to gathering index and table-level statistics, the program gathers column-level histogram statistics for all columns listed in the FND_HISTOGRAM_COLS table. Step 3 :Use the Rapid Install wizard to lay down the file system and install the new technology stack for your Release 12.1.1 Oracle Applications system. The wizard collects configuration parameters and stores them in a configuration file (config.txt) in the Applications file system. When you run Rapid Install, it uses these values to lay down the file system structure and technology stack components for your configuration. As it runs, it creates a context file (<CONTEXT_NAME>.xml) that contains all the parameters that describe your system. This context file is created and managed by AutoConfig.
- F