{"id":9335,"date":"2015-12-15T13:32:54","date_gmt":"2015-12-15T17:32:54","guid":{"rendered":"http:\/\/onlineappsdba.com\/?p=9335"},"modified":"2017-02-10T04:20:47","modified_gmt":"2017-02-10T08:20:47","slug":"upgrading-oracle-ebs-to-release-12-2-here-is-what-you-should-keep-in-mind","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2015\/12\/15\/upgrading-oracle-ebs-to-release-12-2-here-is-what-you-should-keep-in-mind\/","title":{"rendered":"Upgrading Oracle EBS to Release 12.2 ? Here is what you should keep in mind !"},"content":{"rendered":"

\"images<\/a><\/p>\n

We all know 11i versions of E-business suite are De-supported at all levels and R12.1 De-support dates are near. In this scenario there is a huge requirement of Upgrade to the latest versions (R12.2). Oracle, no doubt adopted latest technology and moves to give the best in industry and so on the Oracle Application side. Latest version on Oracle application is 12.2 (Specific 12.2.5) and it comes with latest technology stack.<\/p>\n

The blow points gives the high-level overview of upgrade to R12.2 from the lower versions. Let\u2019s start with Tech stack versions<\/p>\n\n\n\n\n\n\n\n
TECHNOLOGY COMPONENT<\/strong><\/td>\n11.5.10.2<\/strong><\/td>\nR12.0.4<\/strong><\/td>\nR12.1<\/strong><\/td>\nR12.2\/R12.2.5<\/strong><\/td>\n<\/tr>\n
Database<\/td>\n9.2.0.6<\/td>\n10.2.0.3<\/td>\n11.2.0.1<\/td>\n11.2.0.3\/11.2.0.4<\/td>\n<\/tr>\n
Forms\/Reports<\/td>\n6.0.8.25<\/td>\n10.1.2.2<\/td>\n10.1.2.3<\/td>\n10.1.2.3<\/td>\n<\/tr>\n
Application Server<\/td>\n1.0.2.2.2<\/td>\n10.1.3.0<\/td>\n10.1.3.4<\/td>\n11.1.1.6\/11.1.1.6.7<\/td>\n<\/tr>\n
Webtier<\/td>\n–<\/td>\n–<\/td>\n–<\/td>\n11.1.1.6\/11.1.1.9<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Any upgrade to R12.2 goes through below phases<\/p>\n

\"upgrade-path\"<\/a><\/p>\n

    \n
  1. \u00a0Plan for Upgrade<\/strong> – Better plan is surety of success most of the time. We need to plan and also document all the issues reported so that during the Final-Production upgrade downtime can be minimal. We need to plan and check all the intermediate version are supported if not operational. That is the key point during the planning. Follow the best practices for minimizing the upgrade downtime suggested by Oracle and also as per the client and DBA experiences.<\/li>\n
  2. Prepare<\/strong> for Upgrade<\/strong>–\u00a0<\/span> This phase starts after the planning phase and includes Database and Application preparation for upgrade activity. This is the main upgrade phase where we perform all the upgrade activities<\/li>\n
  3. Database Upgrade<\/strong>\u00a0<\/span>\u2013 Select the latest version for database. If 11g database, consider for 11.2.0.4 version or you can plan for 12c versions too. Also apply the latest Consolidate patches as per the database versions. On the application side we need to be on the Minimum base line patches as per the Oracle recommendations.<\/li>\n
  4. File System Lay down-\u00a0 <\/strong>As we know R12.2 comes with latest technology and file-system, so we need to lay down the R12.2 file-system using the latest startCD. Currently StartCD 50 is available.<\/li>\n
  5. Upgrade to 12.2.0- <\/strong>We need to first upgrade to 12.2.0 and need to apply AD and TXK patches on the 12.2 filesystem. As this is the intermediate stage we need to perform it as pre-install activity. At this stage Application will not be operational.<\/li>\n
  6. Enable Online Patching- <\/strong>As you know new feature of R12.2 is online patching so we need to enable our old instance for the same. This is bit time consuming activity and we need to follow the Online Patching Readiness document 1531121.1 from MOS.\u00a0 This phase fixes<\/li>\n<\/ol>\n