Over the past few weeks, I have been sharing my thoughts and experiences in the series, Don’t Get Left Behind on Db2 11.5, on LinkedIn about the approaching End of Support (EOS) deadline for IBM Db2 11.5 on 30 April 2027.
With less than six months remaining, I thought it would be useful to bring these thoughts together. Not as another technical upgrade guide (IBM has plenty of those!), but as some practical lessons I have learnt from working on Db2 upgrades over the years. And if there is one thing these experiences have taught me, it’s that the most difficult upgrades are often the ones you are forced to do rather than the ones you choose to do!
Is EOS an IT Problem or a Business Risk?
“Unsupported” means no new security fixes under standard support. Not fewer, none! Unless you’re paying for Extended Support, which is not, or at least should not be, a plan. It’s a surcharge for standing still.
I have come across more than a few (!) customers who needed a fix during a Production incident but could not get one because they had allowed support to lapse, avoiding an upgrade to a supported release containing the fix. And sometimes it takes something other than IT to force the issue.
Earlier this year, I was called in by a large insurance company to help upgrade an out of support Db2 data warehouse hosted on AWS EC2 instances. Interestingly, this customer was “happily” paying for Extended Support. However, a governance requirement triggered an upgrade of their entire Db2 estate. What followed was a frantic planning and implementation exercise against strict deadlines, at considerably greater cost than a properly planned upgrade would likely have incurred.
It seems to me that EOS is too often treated as an IT problem when it really is a business risk. For organisations in insurance, finance, government and other regulated sectors, running out of support software can also become a costly governance and compliance issue.
Are You Really Ready?
You have decided to upgrade from Db2 11.5 to 12.1 before April 2027. Great! But have you actually done a readiness assessment? One thing I have learnt from numerous Db2 upgrades is that the Db2 upgrade itself is often not the difficult bit. It’s everything surrounding it. Operating systems. Drivers and clients. Applications. Third-party products. HA/DR. Deprecated functionality. Infrastructure. And occasionally, something nobody remembered was dependent on the database until you proposed changing it! 😅
Of course, db2ckupgrade is an essential part of preparing for an upgrade. But passing it does not mean you are ready. It helps establish whether your database can be upgraded. It does not tell you whether your entire service is ready.
For me, the key questions are:
- What are we running, and where?
- Are the target platforms, applications and drivers compatible?
- What functionality has changed or been deprecated?
- What are the implications for HADR, clustering and DR?
- What needs testing, and by whom?
- And perhaps most importantly, what don’t we know?
That last question has caught out more than a few upgrade projects! My advice? Assess first, understand the dependencies, resolve the issues, and then plan the upgrade.
It’s Not Just a DBA Upgrade!
I have come across upgrades where the DBAs were well prepared, only to discover that an application was using an unsupported driver, or that an infrastructure component was incompatible with the target release. Having worked with Db2 for many years, you might think upgrading Db2 is primarily a DBA exercise. Well, that is far from reality! A successful upgrade needs more than just the DBAs.
Developers need to understand application compatibility, SQL behaviour, drivers and any new functionality.
DBAs need to understand changes to administration, security, performance, backup/recovery and deprecated features.
Systems and Infrastructure Teams need to consider operating system compatibility, clustering, monitoring, automation and the underlying infrastructure.
From my experience, the smoother upgrades are invariably the ones where all three teams are involved early, not when the DBA team completes the upgrade and then asks everyone else to test!
What’s Your Upgrade Plan (and Plan B)?
Having been involved in numerous Db2 upgrades on standalone and HADR environments, I have learnt that a single upgrade approach does not usually work for every environment. What works for Development and Test isn’t necessarily appropriate for Production. In fact, at the recent IDUG EMEA conference in Porto, I shared our experience of upgrading Db2 11.1 to 11.5, where we deliberately adopted two different approaches.
Development and Test: In-place upgrades – simpler, quicker and with manageable downtime.
Production: A parallel upgrade approach using HADR, allowing us to maintain a rollback environment on the original Db2 version and reduce migration risk.
The upgrade approach should be driven by business requirements, particularly downtime tolerance and the ability to recover if things go wrong. Which brings me to the question: Do you have a Plan B?
Rollback is not necessarily the reverse of an upgrade! Having a viable, tested rollback process can make all the difference. For me, the objective is to make the Production upgrade as predictable as possible. That means understanding the approach, rehearsing the procedures, measuring the outage and testing the rollback.
Are You Running Out of Options?
I have seen organisations put off upgrades because everything is working fine, other priorities take precedence, or they simply lack the resources. Until something forces their hand. An audit finding. A security vulnerability. A critical support issue. Or an EOS deadline! Suddenly, what could have been a well-planned exercise becomes a frantic race against time. And invariably, a more expensive and riskier one.
With Db2 11.5 reaching EOS on 30 April 2027, the longer you leave your upgrade, the fewer options you may have. You still need time for readiness assessments, remediation, planning, application testing, rehearsals and Production migration. And depending on the size and complexity of your Db2 estate, that could take considerably longer than you expect. Don’t let the EOS deadline dictate your upgrade strategy.
How Can Triton Help?
You do not necessarily need to start with a major migration project. A few days of expert assessment and planning could save weeks of problems later. We can help you get started with a short, focused engagement:
Db2 11.5 EOS Readiness Assessment
Understand your estate, identify compatibility issues, dependencies and risks, and establish what needs remediation.
Db2 12.1 Upgrade Planning Workshop
Agree the upgrade approach, sequencing, timelines, downtime requirements and rollback strategy.
Db2 Upgrade Assistance
Hands-on support through testing, rehearsal and Production migration.
Iqbal Goralwalla
Principal Consultant, Triton Consulting
Don’t get left behind on Db2 11.5. To find out more information and discuss how we can help you with a short, focussed planning session, do please get in contact.