Back to all use cases

AssessmentFinancial Services / Payments

Keeping Db2 covered while the stay-or-move question gets a written answer

Regional Insurer

A typical engagement: AceMQ provides remote and on-call DBA cover for an insurer's IBM Db2 LUW estate and assesses which databases could move to PostgreSQL and which should stay.

Overview

An insurer's Db2 databases outlive the DBAs who built them. This scenario describes DBA cover for a Db2 for Linux, UNIX and Windows estate alongside an assessment of whether PostgreSQL could replace Db2 for some of it.

Challenge

The one DBA who knows the estate is close to retirement, restores have never been timed, Db2 11.5 base support ends on 30 April 2027, and leadership wants to know what a move to PostgreSQL would involve before the next IBM renewal.

Environment

Db2 LUW 11.5 on Linux in the customer's data centre, several production databases with HADR standbys, nightly backups, SQL PL stored procedures in the larger databases, and downstream consumers reading from the databases through batch extracts.

Approach

AceMQ and a partner Db2 DBA start with an estate review: backups and log archiving with a timed restore and rollforward, HADR state, fix pack level against IBM's published support dates, and the slowest recurring SQL. Cover goes live with runbooks and on-call. In parallel, an inventory of each database's Db2-specific features drives the feasibility assessment.

Solution

  1. Reviews backup and log archiving, times a restore and rollforward, and checks HADR synchronization mode and log gap on each standby
  2. Places each instance against IBM's published support dates and plans the 11.5 to 12.1 upgrade as a rehearsed, separate step
  3. Inventories SQL PL routines, XML columns, materialized query tables and other features with no one-to-one PostgreSQL equivalent, database by database
  4. Classifies objects by conversion effort and compares offline load with change capture, noting the replication licence question for Debezium's Db2 connector
  5. Writes a recommendation per database: move now, move in stages, or stay on Db2 with cover and an upgrade plan

Outcome

The engagement delivers Db2 DBA cover with a 15-minute emergency response, a written estate review, a rehearsed upgrade plan, and a per-database recommendation on PostgreSQL with the reasoning behind it. Application code changes are outside the scope and stay with the customer's developers.

Technologies

IBM Db2PostgreSQLDebezium

Ready for an IBM Db2 Health Check?

AceMQ's senior IBM Db2 engineers have handled this exact type of engagement before. Whether you need architectural guidance, hands-on remediation, or an ongoing managed partnership, we're ready to help.