NYOUG 2018 Fall General Meeting: Understanding the New Release and Patching Model for Oracle Database
By now you have heard that Oracle has changed its database release model and numbering, and on top of that has a new patching paradigm. Yearly releases plus Updates and Revisions may require adjustments in test, development and roll-out strategies as well as patching. What does it mean to you when adopting a new release? What is the best patching strategy for your organization? Are support timelines affected by all this? And how will the transition from the old model to the new model work? This presentation will explain everything you need to know about the new database release model and numbering, give you recommendations for patching strategy, and answer all your questions about this crucial area of operations.
Roy Swonger has over three decades of experience in commercial software development. His 20+-year career at Oracle has included work on software process and quality improvement as well as a progression of management roles in technical documentation, software development tools, and core database technologies. Roy has managed the Database Upgrade & Utilities in the Server Technologies division for more than 15 years. In this capacity he is responsible for the development of database features such as the Data Pump, SQL*Loader, External Tables, and Transportable Tablespaces. In addition, Roy runs the global Upgrade Program for the database, coordinating worldwide efforts to make database upgrades faster, easier, and less risky for customers. Roy holds a Bachelor of Science in Computer Science from Rensselaer Polytechnic Institute, and a Master of Software Engineering from Carnegie Mellon University.
[pdf-embedder url=”http://nyoug.org/wp-content/uploads/2018/10/Release_Model_Patching_18c_NYOUG.pdf” title=”NYOUG 2018 Fall General Meeting: Release_Model_Patching_18c_NYOUG”]