Db2 consulting · 24×7 Db2 support · Db2 managed services for IBM Db2 12.1 LUW and Db2 13 for z/OS

Db2 Consulting, 24×7 Db2 Support and Managed Services for LUW and z/OS

MinervaDB provides Db2 consulting, Db2 support and Db2 managed services for organisations that run core business on IBM Db2. We treat Db2 LUW and Db2 for z/OS as two distinct disciplines: on LUW we engineer STMM, BLU, HADR with Pacemaker and pureScale through the 11.5 to 12.1 upgrade wave; on z/OS we work beside your systems programmers on data sharing, access paths, utilities, zIIP economics and the Db2 13 function-level journey. Every recommendation is anchored in MON_GET evidence or SMF and catalog data, never in opinion.

15 minSeverity-1 response, 24×7×365
900+enterprises served
46cities with delivery presence
15+years of database engineering depth
200+years of combined leadership experience

What our Db2 consulting covers

Db2 consulting across architecture, engineering, operations and modernization

Our Db2 consulting engagements start with one question: LUW or z/OS? The code bases, tooling and teams differ, and advice that crosses between them without care is how estates get hurt. Each service below is delivered for the platform you actually run.

Architecture and engineering

Instance, database and subsystem design, table space and partitioning strategy, BLU and DPF layouts, data sharing group topology and capacity planning.

Health checks and tuning

Severity-rated audits, top-SQL and access-path work from MON_GET_PKG_CACHE_STMT or the dynamic statement cache, bufferpool, sort and lock tuning.

High availability and DR

HADR with integrated Pacemaker, pureScale and GDPC on LUW; data sharing, GDPS-aware recovery and image-copy strategy on z/OS; rehearsed recovery.

Upgrades and function levels

11.5 to 12.1 mod-pack upgrades, Db2 12 to Db2 13 for z/OS migrations, APPLCOMPAT ratchets and the V13R1M511 object-conversion campaign.

Security and compliance

Authority models, row and column access control, audit policies, encryption, RACF and trusted-context design, mapped to SOC 2, PCI DSS, HIPAA, GDPR and DPDP.

Managed services and observability

24×7 Db2 support and Db2 managed services: monitoring, incident response, maintenance, backup verification and monthly SLO reporting.

01 · Version landscape

Db2 11.5 support ends April 2027, and Db2 12 for z/OS has already ended

On LUW, Db2 12.1 is current at mod pack 12.1.5 (June 2026), while 11.5.9 is the final 11.5 fix pack with end of support on 30 April 2027; 11.5 Base Edition left support in September 2025. On z/OS, Db2 12 reached end of support on 31 December 2025, Db2 13 reached function level 509 in April 2026, and IBM has said the next version will not arrive before 2028. Db2 consulting planning starts by placing each system on this table.

Db2 consulting version landscape October 2026: Db2 12.1 LUW at 12.1.5, Db2 11.5 final fix pack and end of support April 2027, Db2 11.1 out of support, Db2 13 for z/OS at FL 509, Db2 12 for z/OS end of support, next z/OS version not before 2028

Figure 1. Db2 consulting planning: LUW and z/OS lifecycle status as of October 2026 and the action we recommend. Sources: IBM end-of-support dates, fix pack index and function-level documentation.

We run Db2 11.5. How urgent is the upgrade?

Plan it now. 11.5.9 is the final fix pack, so no new function arrives and defects are fixed only through support channels until 30 April 2027. Moving to 12.1 also means replacing TSA MP with Pacemaker if your HA still uses it, which turns the upgrade into an HA project as well.

We are still on Db2 12 for z/OS. What now?

Unless you hold an extended-support contract, you are running without fixes. We plan the Db2 13 migration (V12R1M510 prerequisite, fallback path, catalog readiness) together with the V13R1M511 object inventory, so you do not migrate once and then stall at a function level.

Is there a Db2 14 for z/OS?

IBM has announced a next version of Db2 for z/OS without a name and has said it does not expect to release it before 2028. Db2 13 is the platform to plan on, and its end of support has not been announced.

02 · Db2 LUW engineering

Db2 consulting for LUW: memory, logging and access paths from evidence

Db2 LUW performance is decided by a few subsystems working together: STMM-managed memory, sort and lock memory, the transaction log and the optimizer. Db2 12.1 adds a VECTOR type, DiskANN vector indexing in 12.1.5 and an AI query optimizer that builds cardinality models during RUNSTATS, which can change access plans after an upgrade. Our Db2 consulting captures a plan baseline before any change and diffs it afterwards.

Db2 consulting LUW architecture: instance with bufferpools, package cache, sort memory and transaction logs, HADR log shipping to principal and auxiliary standbys, Pacemaker cluster manager and archive logs

Figure 2. Db2 LUW 12.1 inside the instance, with HADR and Pacemaker. The four memory and logging areas are where most tuning happens.

Db2 consulting evidence: top SQL by CPU and bufferpool hit ratios

-- Db2 consulting evidence, LUW: which statements own the CPU, the reads and the waits?
SELECT SUBSTR(stmt_text, 1, 80)                           AS statement,
       num_exec_with_metrics                               AS executions,
       total_cpu_time / 1000                               AS cpu_ms,      -- microseconds -> ms
       total_act_time                                      AS activity_ms,
       total_act_wait_time                                 AS wait_ms,
       lock_wait_time                                      AS lock_wait_ms,
       DECIMAL(rows_read, 31, 0) / NULLIF(rows_returned, 0) AS read_per_returned,
       sort_overflows                                      AS sorts_spilled
FROM TABLE(MON_GET_PKG_CACHE_STMT(NULL, NULL, NULL, -2)) AS t   -- -2 = all members
ORDER BY total_cpu_time DESC
FETCH FIRST 15 ROWS ONLY;

-- Bufferpool hit ratios per pool (system pools excluded).
SELECT bp_name,
       CASE WHEN pool_data_l_reads > 0
            THEN DECIMAL(100 * (1 - DOUBLE(pool_data_p_reads) / pool_data_l_reads), 5, 2) END  AS data_hit_pct,
       CASE WHEN pool_index_l_reads > 0
            THEN DECIMAL(100 * (1 - DOUBLE(pool_index_p_reads) / pool_index_l_reads), 5, 2) END AS index_hit_pct
FROM TABLE(MON_GET_BUFFERPOOL(NULL, -2)) AS b
WHERE bp_name NOT LIKE 'IBMSYSTEMBP%';

-- Prove the access path of one statement:
--   db2 "SET CURRENT EXPLAIN MODE EXPLAIN"  ->  run the statement  ->  db2exfmt -d PRODDB -1 -o plan.txt

Database configuration baseline for Db2 12.1, with reason and activation per change

# Db2 consulting baseline, Db2 12.1 LUW, database PRODDB (illustrative values)
# Each line: change ; why ; when it takes effect
db2 "UPDATE DB CFG FOR PRODDB USING SELF_TUNING_MEM ON DATABASE_MEMORY AUTOMATIC"   # STMM owns memory ; online
db2 "ALTER BUFFERPOOL IBMDEFAULTBP SIZE AUTOMATIC"                                # STMM may grow or shrink it ; online
db2 "UPDATE DB CFG FOR PRODDB USING SHEAPTHRES_SHR AUTOMATIC SORTHEAP AUTOMATIC"  # needs instance SHEAPTHRES = 0 ; online
db2 "UPDATE DB CFG FOR PRODDB USING LOCKLIST AUTOMATIC MAXLOCKS AUTOMATIC"        # avoid lock escalation ; online
db2 "UPDATE DB CFG FOR PRODDB USING LOGFILSIZ 65536 LOGPRIMARY 40 LOGSECOND 60"   # 256 MB log files ; LOGFILSIZ at next activation
db2 "UPDATE DB CFG FOR PRODDB USING AUTO_RUNSTATS ON AUTO_STMT_STATS ON"          # statistics stay current ; online

# Switching from circular to archive logging puts the database in BACKUP PENDING.
# Do it only in a window, and take a full backup immediately afterwards.
db2 "UPDATE DB CFG FOR PRODDB USING LOGARCHMETH1 DISK:/db2/archlogs"

# Verify: current value next to the value pending activation.
db2 "GET DB CFG FOR PRODDB SHOW DETAIL" | grep -E "SORTHEAP|LOCKLIST|LOGFILSIZ|LOGARCHMETH1"
What does read_per_returned tell you?

How many rows Db2 read for each row it returned. Values in the thousands point to a missing index, an unusable predicate or stale statistics, and they are where tuning pays back first.

Can the AI query optimizer change our plans?

Yes. In 12.1 it can replace filter-factor estimates for eligible predicates with learned models, retrained when statistics are collected. We inventory models in SYSCAT.AIOPT_TABLECARDMODELS and compare explain output before and after RUNSTATS on critical statements.

Do vector columns affect backups?

They do. IBM documents that logical backup and restore do not support the VECTOR type, so databases holding vectors need physical backup and restore in the recovery runbook, and we rehearse that restore.

03 · HADR, Pacemaker and upgrades

Db2 support for HADR failover that is tested, and upgrades that do not break HA

HADR ships transaction logs from the primary to up to three standbys, and the synchronization mode sets the RPO. Since Db2 12.1, the integrated Pacemaker cluster manager is the supported automation; TSA MP is not in the 12.1 install image, so an 11.5 estate that still depends on it loses automatic failover on upgrade unless the cluster is rebuilt first.

HADR health from db2pd and MON_GET_HADR, Pacemaker state and a graceful takeover

# Db2 support check: HADR state as the primary sees it (read-only, no recycle)
db2pd -db PRODDB -hadr | grep -E "HADR_ROLE|HADR_STATE|HADR_SYNCMODE|HADR_CONNECT_STATUS|HADR_LOG_GAP|STANDBY_ID"

-- The same evidence in SQL, one row per standby.
SELECT standby_id, hadr_role, hadr_state, hadr_syncmode, hadr_connect_status,
       hadr_log_gap,                                                  -- bytes the standby is behind
       TIMESTAMPDIFF(2, CHAR(primary_log_time - standby_replay_log_time)) AS replay_lag_s
FROM TABLE(MON_GET_HADR(NULL)) AS h;

# Pacemaker view on Db2 12.1: cluster resources and where they run.
db2cm -list
crm status

# Planned role switch, run on the principal standby ONLY after the checks above
# show HADR_STATE = PEER and HADR_CONNECT_STATUS = CONNECTED. Graceful, not BY FORCE.
db2 "TAKEOVER HADR ON DATABASE PRODDB"
HADR modeCommit waits forTypical use
SYNClog written on the standbysame data centre, zero data loss
NEARSYNClog received in standby memorymetro distance, near-zero loss
ASYNClog handed to the networklonger distance, small loss window
SUPERASYNCnothing; never blocks the primaryauxiliary standbys, remote DR

Upgrade 11.5.9 to 12.1.5 with readiness check, backup fallback and confirmation gate

# Db2 consulting runbook: Db2 11.5.9 -> 12.1.5 upgrade, single instance (LUW).
# HADR pairs follow IBM's HADR upgrade procedure; we rehearse it on a non-production pair.
set -euo pipefail
DB=PRODDB
NEW=/opt/ibm/db2/V12.1

# Gate 1: TSA MP is not shipped with 12.1. If it manages this instance, move to Pacemaker first.
if command -v lssam >/dev/null && lssam >/dev/null 2>&1; then
  echo "TSA MP detected: complete the Pacemaker cutover before upgrading"; exit 1
fi

# Verification before: the 12.1 code checks the database is ready to upgrade.
"$NEW/bin/db2ckupgrade" "$DB" -l "/tmp/db2ckupgrade_$DB.log"

# Fallback: offline backup, then verify the image is readable.
db2 "BACKUP DATABASE $DB TO /backup COMPRESS"
db2ckbkp /backup/"$DB".0.*.001

# Gate 2: explicit confirmation, because the instance stops for everyone.
read -r -p "Type UPGRADE-$DB to stop the instance and upgrade: " ok
[ "$ok" = "UPGRADE-$DB" ] || { echo "aborted"; exit 1; }
db2stop force
sudo "$NEW/instance/db2iupgrade" -u db2fenc1 db2inst1      # as root, instance upgrade
db2start
db2 "UPGRADE DATABASE $DB REBINDALL"

# Validation after: code level and instance service level.
db2level
db2 "SELECT inst_name, service_level FROM TABLE(SYSPROC.ENV_GET_INST_INFO())"

04 · Db2 for z/OS

Db2 consulting for z/OS: data sharing, access paths, zIIP and the Db2 13 path

On z/OS we work alongside your systems programmers: SMP/E, subsystem installation and z/OS itself stay with them unless contracted, while the database layer, SQL and application performance, utility strategy, HA/DR design and migration engineering are ours. The largest item on most roadmaps is no longer the Db2 13 migration itself but V13R1M511, the function level at which legacy objects can no longer be created or accessed.

Db2 consulting for z/OS: path from V12R1M510 to Db2 13 V13R1M100, V13R1M500, function levels to 509, V13R1M510 and the V13R1M511 gate with objects that must be converted

Figure 3. The Db2 13 function-level path, and what has to be converted before V13R1M511.

Top dynamic SQL from the statement cache, ranked by CPU

-- Db2 consulting evidence, z/OS: top dynamic SQL from the statement cache.
-- Prerequisites: statement statistics trace, e.g.
--   -START TRACE(MON) CLASS(30) IFCID(316,318)
-- and DSN_STATEMENT_CACHE_TABLE created under the current SQLID.
EXPLAIN STMTCACHE ALL;

SELECT STMT_ID,
       STAT_EXEC                        AS executions,
       DEC(STAT_CPU, 15, 3)             AS cpu_seconds,
       DEC(STAT_ELAP, 15, 3)            AS elapsed_seconds,
       STAT_GPAG                        AS getpages,
       STAT_SYNR                        AS sync_reads,
       STAT_ROWX                        AS rows_examined,
       STAT_ROWP                        AS rows_processed,
       SUBSTR(STMT_TEXT, 1, 80)         AS statement
FROM DSN_STATEMENT_CACHE_TABLE
ORDER BY STAT_CPU DESC
FETCH FIRST 15 ROWS ONLY;

V13R1M511 readiness: non-UTS table spaces, synonyms and per-object synchronous I/O

-- Db2 consulting readiness check for V13R1M511 (read-only catalog queries).
-- Confirm code values against the Db2 13 catalog reference for your
-- maintenance level before using the results to plan conversions.

-- 1. Table spaces that are not universal table spaces
--    ('G' = partition-by-growth, 'R' = partition-by-range; LOB 'O' and XML 'P' excluded).
SELECT DBNAME, NAME, TYPE, SEGSIZE, PARTITIONS
FROM SYSIBM.SYSTABLESPACE
WHERE TYPE NOT IN ('G', 'R', 'O', 'P')
ORDER BY DBNAME, NAME;

-- 2. Synonyms, which must become aliases or views before V13R1M511.
SELECT CREATOR, NAME, TBCREATOR, TBNAME
FROM SYSIBM.SYSSYNONYMS
ORDER BY CREATOR, NAME;

-- 3. Synchronous read I/O per table space partition from real-time statistics
--    (NSYNCREADIO, new at FL 509): object-level I/O attribution without a trace.
SELECT DBNAME, NAME, PARTITION, NSYNCREADIO, REORGINSERTS, REORGDELETES
FROM SYSIBM.SYSTABLESPACESTATS
ORDER BY NSYNCREADIO DESC
FETCH FIRST 20 ROWS ONLY;
How do you reduce mainframe software cost with Db2?

By cutting general-processor CPU on the work that drives your MLC peaks: access-path fixes, fewer getpages, buffer pool tuning, and moving eligible work to zIIP engines. The COPY utility gained zIIP offload in late 2024; we measure the effect in accounting and statistics traces before and after.

What do you review in a data sharing group?

Group buffer pool sizing and castout, global lock contention and false contention, P-lock activity, member workload balance and restart behaviour. FL 509 adds a lock hash algorithm that reduces false page P-lock contention on very large page sets once objects are reorganized.

Who handles a Db2 defect on z/OS?

IBM. We diagnose, build the evidence package with traces and dumps, open and drive the case with IBM support, and keep your service running with the safest workaround while the fix is delivered.

05 · Health checks and rates

Transparent Db2 consulting rates and fixed-price health checks

As a virtual corporation we carry no office overhead, so what you pay goes to Db2 engineering talent. Every health check ends with a written report, findings rated Critical, High, Medium or Low, and a review call with the engineer who did the work. Prices exclude applicable GST or other taxes.

Db2 LUW health check and performance audit

US $15,500 per database, fixed price, remote, typically 3 to 5 business days. Configuration and STMM review, top-SQL and access-path audit from MON_GET_PKG_CACHE_STMT and db2exfmt, index, statistics and REORGCHK review, HADR and Pacemaker readiness, backup and restore validation, security posture and a capacity forecast.

Db2 for z/OS subsystem health check

Scoped per subsystem or data sharing group, priced on member count and SMF volume, remote or on-site, typically 5 to 10 business days. SMF 100/101/102 analysis, buffer, EDM, RID and sort pools, statement cache audit, data sharing review, utilities hygiene, zIIP and MLC opportunities, and a V13R1M511 readiness check.

Db2 security and compliance audit

US $15,000 per system. Authority and separation-of-duties review, row permissions, column masks and trusted contexts, audit coverage and SIEM integration, encryption and certificate lifecycle, compliance control mapping and a prioritised remediation plan.

Remote consulting · $300 per hour

Performance engineering, HADR, pureScale and data sharing design, access-path and index work, upgrade and function-level planning, backup and DR strategy, delivered remotely worldwide on short notice.

Remote DBA retainer · from $4,500 per quarter

Db2 managed services on retainer, minimum 4 hours per month: 24×7 monitoring and alerting, incident response and RCA, mod-pack and function-level management, backup verification, DR drills and monthly SLO reports. Emergency support is always included.

On-site consulting · $500 per hour

Architecture and modernization strategy sessions, engineering-leadership workshops, team enablement and hands-on implementation, available in 46 cities worldwide, plus travel.

06 · Modernization

Honest modernization: offload, coexist or stay on Db2

Vendors tend to sell more of their own platform. Our Db2 consulting runs measured assessments instead, and sometimes the answer is to stay on Db2. Where offload makes sense, change data capture moves read-heavy and analytical workloads to PostgreSQL or to ClickHouse operated by ChistaDATA, while Db2 stays the system of record.

Db2 consulting modernization: change data capture from Db2 for z/OS or LUW through ASN Capture and the Debezium Db2 connector into Kafka, then to PostgreSQL and ClickHouse, with licensing and 10-byte LRSN prerequisites

Figure 4. A Db2 change-data-capture pipeline for offload, with the prerequisites we check before committing to it.

Debezium Db2 connector registration, with prerequisites and secrets handled outside the request

# Db2 consulting modernization: register a Debezium Db2 connector with Kafka Connect.
# Prerequisites we verify first:
#   - ASN Capture running for the source tables (SQL replication; IBM states this
#     needs a separate IBM InfoSphere Data Replication licence)
#   - Db2 for z/OS: 10-byte RBA/LRSN, since 6-byte LSNs are not supported; z/OS support
#     is incubating in Debezium, so production use is a documented risk decision
# The password is resolved by Kafka's file config provider, never stored in this request.
curl -s -X POST http://connect.internal:8083/connectors \
  -H "Content-Type: application/json" \
  -d '{
    "name": "db2-orders-cdc",
    "config": {
      "connector.class": "io.debezium.connector.db2.Db2Connector",
      "database.hostname": "db2prod.internal",
      "database.port": "50000",
      "database.user": "cdc_reader",
      "database.password": "${file:/etc/kafka/secrets/db2.properties:password}",
      "database.dbname": "PRODDB",
      "topic.prefix": "db2prod",
      "table.include.list": "SALES.ORDERS,SALES.ORDER_LINES",
      "snapshot.mode": "initial",
      "schema.history.internal.kafka.bootstrap.servers": "kafka-1.internal:9092",
      "schema.history.internal.kafka.topic": "schema-history.db2prod"
    }
  }'

# Verify: connector and task state, then lag on the target side.
curl -s http://connect.internal:8083/connectors/db2-orders-cdc/status
Is Debezium a free way to stream changes out of Db2?

No. The Debezium Db2 connector relies on ASN Capture from SQL replication, and IBM states that using it for this purpose needs a separate IBM InfoSphere Data Replication licence. We put that cost in the business case from the first meeting.

Why does RBA/LRSN format matter for modernization?

Debezium does not support Db2 for z/OS levels that use 6-byte LSNs, and V13R1M511 blocks 6-byte RBA/LRSN page sets anyway. Converting to 10-byte format once serves both goals, so we plan the two workstreams as one programme.

When do you recommend staying on Db2?

When the workload is stable, well tuned, inside licence entitlements and tightly coupled to mainframe batch or CICS, and a migration would add risk without a measurable return. We document that verdict as carefully as a migration plan.

Can you migrate Db2 to PostgreSQL outright?

Yes, after an assessment of schema, SQL PL, packages and application coupling. See our PostgreSQL consulting practice and our broader data modernization services.

07 · Security and compliance

Db2 controls that hold up in an audit

Db2 has some of the most complete access-control features of any database: row and column access control, trusted contexts, fine-grained authorities and policy-based auditing. Our Db2 consulting turns them into a design auditors can follow, with evidence. Db2 12.1 adds a table-space-level authority so storage administrators no longer need DBADM, CSV audit output for SIEM ingestion, and FIPS 140-3 modules with quantum-safe TLS 1.3 key exchange in 12.1.5.

Column mask, row permission, audit policy and an authority review on LUW

-- Db2 consulting security baseline, LUW 12.1. Run with SECADM authority.
-- 1. Column mask: only the PAYROLL role sees full tax identifiers.
CREATE MASK hr.emp_taxid_mask ON hr.employee
  FOR COLUMN tax_id RETURN
    CASE WHEN VERIFY_ROLE_FOR_USER(SESSION_USER, 'PAYROLL') = 1
         THEN tax_id
         ELSE 'XXX-XX-' || SUBSTR(tax_id, 8, 4)
    END
  ENABLE;
ALTER TABLE hr.employee ACTIVATE COLUMN ACCESS CONTROL;

-- 2. Row permission: branch staff see only their own branch.
CREATE PERMISSION hr.emp_branch_rows ON hr.employee
  FOR ROWS WHERE branch_id IN (SELECT branch_id FROM hr.staff_map WHERE user_id = SESSION_USER)
  ENFORCED FOR ALL ACCESS
  ENABLE;
ALTER TABLE hr.employee ACTIVATE ROW ACCESS CONTROL;

-- 3. Audit policy for security, administration and object-maintenance events.
CREATE AUDIT POLICY prod_audit
  CATEGORIES SECMAINT STATUS BOTH, SYSADMIN STATUS BOTH,
             OBJMAINT STATUS BOTH, VALIDATE STATUS FAILURE
  ERROR TYPE AUDIT;
AUDIT DATABASE USING POLICY prod_audit;

-- 4. Review: who holds database-wide authorities.
SELECT grantee, granteetype, dbadmauth, secadmauth, dataaccessauth, accessctrlauth
FROM SYSCAT.DBAUTH
WHERE 'Y' IN (dbadmauth, secadmauth, dataaccessauth, accessctrlauth);
How do you secure Db2 for z/OS?

Through RACF profiles for Db2 resources, roles and trusted contexts for application servers, DDF and profile-table controls for distributed access, and audit policies. FL 509 adds subnet wildcards to resource limit facility tables, which simplifies governing distributed work by network range.

Do you configure native encryption?

Yes, Db2 native encryption with a keystore or hardware security module on LUW, and dataset encryption with z/OS key management on the mainframe, with key rotation procedures and restore tests so encrypted backups stay usable.

Which compliance regimes do you cover?

SOC 2, PCI DSS, SOX, HIPAA, GDPR and India's DPDP Act. We map each control to configuration evidence, access reviews and audit samples. See also our database security services.

08 · Cloud and containers

Db2 support on Amazon RDS, IBM Software Hub and self-managed cloud

Managed Db2 removes host administration, not engineering, and each platform narrows what a DBA can see and do. Our Db2 support covers those differences explicitly and documents an exit path for every managed deployment.

PlatformWhat differs from self-managed Db2What we engineer
Amazon RDS for Db211.5 and 12.1 (12.1.4, trailing self-managed by about one mod pack); no shell, no SYSADM or SECADM; non-fenced routines unsupported; Community Edition limited to 4 vCPU and 8 GiBpre-migration checks, parameter groups, BYOL or Marketplace licensing review, SQL-level monitoring, backup and restore drills
IBM Software Hub (formerly Cloud Pak for Data)Db2uInstance is the new custom resource; Db2uCluster is deprecated with migration by backup and restorerebuild planning, Velero-based backup validation, operator upgrades
Self-managed on AWS, Azure, Google Cloudfull control; pureScale on AWS and Azure, HADR across zones and regionsHADR and Pacemaker design, storage and network sizing, cost reviews
Db2 for z/OS with IDAAaccelerator offload of analytical queries, version 8 migration and coexistenceworkload fit, QUERY_ACCEL_OPTIONS, accelerator versus ClickHouse offload comparison

09 · 24×7 Db2 support and managed services

How Db2 managed services run, and the response times we commit to

Principal engineers hold your runbooks, monitoring access and topology map before the first incident. Response targets are commitments for an engineer to be actively working the problem. We complement IBM support rather than replace it: product defects go to IBM with our evidence package, while we keep your service running.

S1 · 15 minutes

Production down or data at risk: database or subsystem unavailable, failed takeover, log full, corruption.

S2 · 12 hours

Severe degradation with a workaround: lock storms, HADR in remote catch-up, failing backups or image copies.

S3 · 24 hours

Non-critical defects, configuration questions and planned changes needing review.

S4 · 48 hours

Advice, capacity planning, upgrade and function-level roadmaps.

Onboarding

Access, topology, MON_GET or SMF baselines, HADR and data sharing review, backup and image-copy verification, and a ranked risk register.

Monthly reviews

Top-SQL trends, growth, REORG and RUNSTATS currency, HA readiness, security drift and the mod-pack or function-level calendar.

Knowledge transfer

Runbooks, RCAs and alert definitions stay with your team, so Db2 support builds capability instead of dependency.

FAQ

Db2 consulting questions we hear first

Short answers for CIOs, platform leads and Db2 managers choosing a Db2 consulting and support partner.

How much does Db2 consulting cost?

Remote Db2 consulting is $300 per hour and on-site consulting is $500 per hour plus travel. Remote DBA retainers start at $4,500 per quarter for a minimum of four hours per month, with emergency support included. The Db2 LUW health check and performance audit is US $15,500 per database; Db2 for z/OS subsystem health checks are scoped per subsystem or data sharing group.

How fast is your Db2 support response?

Severity 1 incidents get a named engineer working the problem within 15 minutes, 24×7×365. Severity 2 is 12 hours, Severity 3 is 24 hours and Severity 4 is 48 hours.

Do you support both Db2 LUW and Db2 for z/OS?

Yes, as separate disciplines with engineers who specialise in each, from Db2 11.5 and 12.1 on Linux, UNIX and Windows to Db2 13 for z/OS and data sharing groups.

Do you replace IBM support?

No. Db2 managed services from MinervaDB complement IBM support: we run day-to-day engineering and incident response, and we escalate product defects to IBM with the diagnostics they need.

Can you help with Db2 licensing?

We flag licensing implications, such as Db2 Connect JDBC licence files changing with version 12 drivers, edition limits and zIIP eligibility, and leave determinations to your IBM representative and counsel.

Are you tied to IBM or any vendor?

No. MinervaDB is vendor-neutral and sells no licences, so we will tell you when staying on Db2 is right and when PostgreSQL, ClickHouse or another engine fits better.

Guidance on this page is general and pinned to the Db2 versions, mod packs and function levels named. Test every configuration change, upgrade, takeover and restore step in a non-production environment first, verify backups by restoring them, and maintain a robust disaster-recovery posture. Related services: Remote DBA services · Oracle consulting · PostgreSQL consulting · 24×7 emergency DBA coverage · Db2 for z/OS index efficiency · IBM Db2 end-of-support dates · Db2 LUW fix pack index

Need Db2 consulting before the next deadline?

Talk to a Db2 principal engineer about your 11.5 upgrade, your Db2 13 function-level plan or a health check. contact@minervadb.com · +1 (844) 588-7287.