12.2

12.2 An Introduction.

Oracle 12.2 has some major changes in terms file system and technology stack .usability improvements and new versions of technology stack components (Oracle Database 11g R2 and Oracle Fusion Middleware 11g R1 as the application server), but the most important and impressive new feature of course will be online patching. Online patching is supposed to change the game changer as Oracle says it.

Oracle plans for moving the application to next level of high availability, although not completely yet. With introduction to 2 file systems, online patching option, it has already started in that direction and with Weblogic in Tech Stack, it has scope for fail-over and clustering of application services.

Now with introduction of WebLogic in 12.2, Oracle is back to integration lines. Integration of fusion product with EBS now would be easier. We are going to see something in terms of ERP consolidation with this release, which means use of 12.2 EBS with fusion Middleware and Fusion Apps Products is going to have a good scope.

With introduction of “Edition Based Redefinition” in 11gr2, it is now possible to upgrade the database component of an application while it is in use, thereby minimizing or eliminating down time. Upgrade an application while it is in use, you copy the database objects that comprise the application and redefine the copied objects in isolation. Your changes do not affect users of the application—they continue to run the unchanged application. When you are sure that your changes are correct, you make the upgraded application available to all users.

Just to add more on online patching, although it can be reduced with various techniques (e.g. staged APPL_TOP), some downtime is still required to apply a number of changes. Online patching will not eliminate downtime completely, but will reduce it significantly by using “Edition Based Redefinition” (EBR) at the database level and using a secondary applications file system for online patching. In fact, all patching activity will be an online operation; downtime will be required only to switch from one version to another. Online Patching means that patches that change EBS database objects can be applied while the E-Business Suite production instance is fully operational.  Only a short downtime will be required to complete the patching process.  This wills make patching downtime's more predictable.