Session title: Db2 12 Continuous Delivery – New challenges for deployment
Session abstract: Fundamental changes in the Db2 z world often lead to concerns. Let’s face it – some changes force us to change! While a Db2 version migration usually took months, or even years, there will be no new Db2 version after 12, but continuous code drops.This will have a tremendous impact on migration strategies, because we have to find a reliable way to test these code deliveries in a fraction of time. If we make it, Business Divisions will become enthused at how quickly new technology becomes available for new applications. This presentation will describe the difference between Code, Catalog, Function and Application Levels, how you can control them and how you can fallback in case of anomalies. It also illustrates how we still can be pro-active in testing without burning weeks and months.
Learn how to choose from four different levels of testing and a new way of automation. CD-Screening allows you to pick and choose from KPI based test automation. The levels include simple anomaly alerting, access path verification, clone Pre-apply and even workload capture/replay to easily discover different behaviour resulting from a new code Level.
Presentation Outline: Joining this presentation, you’ll learn how to align Continuous Delivery to your Continuous Availability.
- Agile, Continuous Delivery, DevOps – just buzz words, or new methodologies
- Db2 Code, Catalog, Function and Application Levels – differences and dependencies.
- Activation/Deactivation of new code and how to fallback and when you can’t.
- Different flavors of (pro-active) CD-Screening and how it can be automated:
- Anomaly alerting based on Incompatibility Change Indicators (ICIs
- Dyn./Stat.Access Path Change Detection e.g.via Plan Management
- Clone based code change pre-apply exploiting Backup System
- Workload-KPI verification using SQL replay and KPI comparison
Speaker biography: Ulf Heinrich is the Director of Solutions Delivery at SEGUS Inc. He specializes in Db2 recovery issues and database maintenance, focusing on the growing requirement for cost reduction and 24×7 operations. As a consultant at large customer sites, he has implemented database maintenance procedures and recovery strategies, and also experienced the pitfalls of recovery scenarios under real‐world recovery pressure. His activities cover EMEA, as well as North America through SE’ U.S. subsidiary, SEGUS Inc. He is involved in the development of SE’ maintenance and recovery Solutions.