Still on Informix 12.10? You need to read this.
12.10 support is over. But while you weren't looking, Informix changed quite a bit: standalone containers for Kubernetes, a rebuilt engine under the hood, native S3 backup, and a certification that's switching versions.
In March, Anup Nair — Principal Technical Product Manager for Informix — published the Informix Standalone Container announcement on IBM TechXchange. Enterprise-grade images for Kubernetes and OpenShift, with full support, no Cloud Pak for Data required. The post has 13 views and zero comments. Almost nobody noticed.
And yet, it's probably the most significant change in how Informix is deployed since IBM acquired it. Combined with the end of 12.10 support, the new capabilities in Informix 15 and the v15 certification transition, the landscape has shifted. Here's the summary.
Standalone containers: what's changed
Until recently, running Informix in containers with enterprise support in production required Cloud Pak for Data (CP4D). The Docker Hub images — which have since moved to the IBM Container Registry (ICR) — were Developer Edition only: fine for dev and test, no IBM support for production.
The Informix Standalone Container removes that dependency:
- Production-grade images for Informix v14 and v15 on IBM Container Registry.
- Direct deployment on Kubernetes and OpenShift without CP4D.
- Full enterprise support under existing entitlement — not a separate product.
- Developer to Enterprise Edition upgrade by swapping the image and applying the installer.
- CASE bundles on GitHub: ibm-informix-standalone.
In practice, this means integrating Informix into CI/CD pipelines, spinning up instances for automated tests, deploying with Helm Charts across hybrid-cloud environments, and having dev environments identical to production. Daniel Weber, Informix Container Dev Lead, demonstrated the process at the April IIUG Tech Talk.
It's the kind of announcement that doesn't make headlines but changes how you operate a product day to day.
Informix 12.10 has lost support
On 30 April, IBM completed the transition of Informix 12.10 to Extended Support. Three direct consequences:
- No more security patches. Any vulnerability discovered from now on stays unresolved.
- No more bug fixes. The current fixpack is the last one.
- Technical support only at extra cost under Extended Support, until 2030.
The CSDK 4.10 (Client SDK) also transitions to Extended Support on the same date, which affects legacy ESQL/C, ODBC, and JDBC drivers.
12.10 was released in 2013. Thirteen years is a reasonable lifecycle. But many production environments are still running it because "it works" and there was never enough pressure to migrate. Now there is — and it coincides with a genuine modernisation path: containers, native encryption, S3 backup.
14.10 or 15: which one for migration
Informix 15 (November 2024) is the first major release in over five years, with deep internal engine changes: drastically expanded limits (a single partition can now hold 140 trillion pages), native dbspace encryption, improved Wire Listener (MongoDB 3.2–4.2), native S3/Azure/IBM COS backup via ON-Bar, official Helm Charts, and mandatory Java 11.
Informix 14.10xC13 (January 2026) is the latest release on the 14.10 branch: archecker improvements for SmartLOBs, Direct I/O for 2K/4K blocks, and accumulated fixes. Mature, battle-tested, conservative.
Our recommendation: if the environment is stable and you don't need the features in 15, the 12.10 → 14.10 path is the safest. It gives Informix 15 time to accumulate fixpacks. If it's a new project or you need native encryption, cloud backup, or Kubernetes-native deployment, go straight to 15.
Staying on 12.10 under Extended Support "until there's no other option". Extended Support has an end date and the longer you wait, the less flexibility you'll have. Rushing a migration is expensive. Planning one is a manageable project.
Why training your team matters as much as migrating
We see it project after project. A team upgrades Informix and keeps operating with the same procedures from eight years ago. The server is on the new version; the knowledge isn't.
14.10 introduced AUTO_TUNE, which makes many manual adjustments unnecessary. 15 changes the approach to encryption, backup, and deployment. And with standalone containers there's a brand new operational model that requires Kubernetes skills a traditional DBA may not have. The official documentation is in the Informix 15 containerised deployment guide, but documentation doesn't replace hands-on training.
At SIXE, we've been delivering official IBM training for over 15 years. We've updated the entire Informix curriculum to v15 with new labs and custom documentation.
Informix 15 & 14.10 System Administration (SIFMX819G) — 3 days / 24 hours. From server architecture to production troubleshooting, with a 12.10→14.10/15 migration module and container deployment. Delivered by practising DBAs on a live Informix 15 instance.
The full Informix catalogue includes system administration, database administration, and custom migration courses. In English, Spanishand French — online, on-site, open or in-company.
Tell us what Informix you're running and we'll tell you where to start.
Current version, whether you're considering containers, whether your team needs training before moving production. No sales pitch.
Blog!
Our mission
SIXE ensures that your infrastructures based on IBM®, Red Hat®, Canonical®, and SUSE® technologies remain stable, secure, and optimized for as long as you need them.
At SIXE, we are committed to sustainability. That’s why we help you design, implement, and maintain durable and efficient technological solutions.
