Software
IBM Db2 Plug-in for
Oracle Enterprise Manager
Monitor IBM Db2 for Linux, UNIX, and Windows from Oracle Enterprise Manager: 17 console pages, alert thresholds that ship turned on, HADR takeover readiness, blocking chains down to the root blocker, and three compliance standards. A local or remote agent collects over JDBC as a least-privilege user that cannot read table data.
17
Native Console Pages
75+
Metric Groups
29
Compliance Rules
50+
Default Alert Thresholds
What the Plug-in Answers
Six features cover the questions Db2 DBAs are paged for: can the standby take over, who is blocking whom, did the backup run, and when will a table space fill.
HADR Takeover Readiness
Every 5 minutes, each standby gets a verdict on whether it could take over now, a 0–100 readiness score, and the reason in plain words, backed by log-gap, replay-gap, and replay-lag columns. Shipped alerts fire when a standby is not ready, when a gap passes 10 MB or 100 MB, and when replay lag passes 60 or 300 seconds. A standby can be monitored as its own target and reads Up, not Down. With HADR alternate servers set, a target follows the primary through a takeover and back.
Monitoring Readiness
One page checks what each feature needs: the connection, the license, the Db2 version and topology, monitoring access, every metric group's collection, the monitor switches, deadlock capture, HADR, and the diagnostic log. The agent runs the checks live when the page opens, and a gap that a statement can fix comes with that statement and a Copy button. The page runs no statement itself. The Overview shows an hourly count of the same checks.
Blocking Chains and Sessions
Locks shows who waits on whom as trees that start at the root blocker, marks applications waiting on each other in a cycle, and lists the past day's deadlocks once deadlock capture is set up. Sessions lists the 25 sessions using the most CPU in their current unit of work, including those idle in a transaction. Both can refresh every 30 seconds, 1 minute, or 5 minutes. With the agent on the Db2 host, a Kill button on a session or a root blocker forces it off after a confirmation.
Backup and Recovery
The last backup and the days since, plus Db2's recovery history of every backup, restore, load, reorg, and roll-forward, with failed operations and their SQLCODE. Running utilities and table-space rebalances are listed too. Back Up Database takes an online backup now, once at a later time, or daily on Oracle EM 24ai, compressed and with logs by default, after a confirmation. It works with a local or remote agent on a single-partition database. The backup-age alert warns after 1 day and goes critical after 3, and a failed operation raises a critical alert.
Days-to-Full Growth Forecast
For every table space, including auto-resize ones, a projected days to full, growth per day, and what limits growth: MAXSIZE, the file system, or fixed containers. Days to full is shown in amber under 30 days and in red under 7. A file-system headroom table covers each automatic-storage path. Alerts fire under 30 and 7 days to full, on a failed resize, and when a storage path's file system passes 85% or 95%.
SQL and Explain Plan
Rank the top 20 statements by CPU time or by executions over the past hour, day, week, or month. Statements are grouped by digest, so runs that differ only in literal values count as one statement. Statement Detail charts a statement's executions, CPU time, and activity time over the window, and Explain Plan shows the access plan of its cached section without running it. The statement text is stored without literal values, at most once a day and up to 2,000 characters, and you can turn that collection off.
Findings Become Oracle EM Alerts
More than 50 Warning and Critical thresholds ship turned on, as ordinary Oracle EM metric thresholds that you can tune per target and route through your existing notification rules. Starter, Standard, and Production-critical monitoring templates and an incident rule set ship alongside. On Oracle EM 24ai, six runbooks walk through the most common Db2 alerts: database down, table space running out of space, transaction log filling, backup overdue, HADR standby not ready, and applications blocked on locks.
17 Native Console Pages
Each page is part of the IBM Db2 Database target's menu in Oracle EM, grouped as Workload, Storage and Logs, and Protection, and reads the metric groups the plug-in already collects, with no separate reporting server.
Overview
24-hour availability, a Database card, a Monitoring and License card, and seven Key Indicators tiles. A Health Overview shows Oracle EM's current verdict and open alerts for each area, with a link to the page behind each one. Connection and lock charts, incidents, and related targets complete the page.
Performance
Where request time goes, buffer pool I/O per pool, catalog and package cache hit ratios with their lookup counts, a wait-time breakdown, and transaction log, direct I/O, and SQL activity rates. One time window moves every region, from real time to the past month.
Memory & Sorts
Sort heap use and sort overflows, package and catalog cache activity, instance memory against its limit, Db2's memory sets, and the self-tuning memory settings.
SQL
Top 20 statements by CPU time or executions over one time window, grouped by digest, with bar charts of activity time and executions. Opening a statement shows Statement Detail with its history and Explain Plan.
Sessions
The 25 sessions using the most CPU in their current unit of work, with their state, lock wait, locks held, and running SQL, read live at the auto-refresh rate you choose.
Locks
Blocking chains down to the root blocker, top waits by blocked and by blocking application, lock waits by table, live lock contention, recent deadlocks, and recent diagnostic-log matches.
Waits
Wait time by class, latch waits for the instance, buffer pool read and write time, WLM service classes and workloads, and the applications using the most CPU in the last interval.
Members
For a partitioned database: how many members are active, each member's status, connections, and log use, and data size per member to show skew between partitions.
Storage
Database space used, table space utilization and state, what limits each table space, the days-to-full forecast, and file-system headroom for each storage path.
Tables
Tables with stale statistics or a reorg recommendation, reclaimable space, overflow accesses, and a trend for any listed table over the window.
Indexes
Index activity and size for the most-scanned indexes, indexes no DML statement has scanned for 90 days, and invalid packages and objects.
Transaction Log
Log space used, secondary log files, log archiving status, the oldest open transactions with the one holding the log back, and the recovery configuration.
Backup
The last backup and its result, Db2's recovery history for backup, restore, load, reorg, and roll-forward with failures marked, a days-since-backup trend, running utilities, and Back Up Database.
High Availability
Takeover readiness for each HADR standby with its readiness score, state, sync mode, log gap, and replay lag, log-gap and replay-lag trends over a chosen window, and the target's incidents.
Monitoring Readiness
Live checks of the connection, license, collection, monitor switches, deadlock capture, HADR, and diagnostic-log setup, each with what is set now and the statement that fixes a gap.
License Info
The license the target's key carries: customer, type, status, expiration date, licensed instances, and days remaining.
More pages
Configuration
Database and instance configuration, registry variables, product and fix pack levels, audit posture, and system details on one searchable page, with changes since the previous collection highlighted.
Enterprise-Grade Capabilities
Everything listed here ships in the current release.
Curated Alerting and Runbooks
More than 50 Warning and Critical thresholds ship turned on across availability, locks, waits, memory, storage, the transaction log and archiving, HADR, backups, and table maintenance. They are standard Oracle EM thresholds, so tuning and notification work as they do for any target. On Oracle EM 24ai, six runbooks read the target's current values from the repository and show the fix, without running anything on the database.
Compliance Standards
Three standards with 29 rules evaluate on the daily configuration snapshot. Configuration Best Practices (17 rules) covers diagnostic logging, recovery and backup age, memory, network and platform security including TLS, authentication, and maintenance. Audit Posture (10) checks the audit policy and its categories, who holds administrative authority, what is granted to all users, and trusted contexts. Version Lifecycle (2) flags a release past IBM end of support or behind the latest modification pack, with the limits as editable rule parameters.
IBM Db2 Instance Targets
An optional IBM Db2 Instance target monitors what belongs to the instance once: instance memory and memory sets, agents, FCM buffers, latch waits, the diagnostic log, and its own daily configuration snapshot. Its Overview lists each database target that runs on the instance, and with the agent on the Db2 host the instance starts and stops from Oracle EM.
Automatic Discovery and Partitioned Databases
Each Linux and Windows agent host proposes its local Db2 databases as targets to promote, with nothing to configure. Partitioned (DPF) databases are read across every active member and reported as a whole, and an alert fires when a member is down.
Least-Privilege Monitoring
The monitoring user is least-privilege: it reads Db2's monitoring functions and catalog, and cannot read a row of table data. Admin jobs use their own credentials, separate from monitoring.
TLS, Kerberos, and Encrypted Credentials
TLS with a client truststore and hostname validation is a target property, and TLS faults are reported by cause. Kerberos authentication and DRDA encryption of the user ID and password are options too. The IBM JDBC driver ships bundled, so there is nothing to stage.
Availability That Names the Cause
A target reads Down only when Db2 cannot be reached. A wrong password, missing monitoring access, a TLS problem, or a quiesced database shows as a metric collection error that names the fix. A monitoring switch set to NONE raises an alert instead of graphing zeros.
Local and Remote Admin Jobs
Force Application, RUNSTATS on a table, and an online backup run as Oracle EM jobs over the target's own JDBC connection, so they work on a remotely monitored database. With the agent on the Db2 host, start and stop instance, quiesce, unquiesce, kill application, and archive active log run as local jobs.
Diagnostic Log Alerting
A curated set of db2diag.log patterns ships ready to alert, including critical-level entries, crash and trap signatures, full table space, lost HADR connection, and failed log archiving. Your own patterns survive plug-in upgrades. Requires the agent on the Db2 host.
Daily Configuration Snapshots
System, instance, database manager, registry, memory, recovery, and audit settings are captured every 24 hours as Oracle EM configuration data, with history and comparison across targets, and feed the compliance standards.
Compatibility
Certified on these Db2 versions, Oracle EM releases, and agent platforms.
IBM Db2 LUW
12.1 (certified Comprehensive) and 11.5 (certified Basic); single-partition and partitioned (DPF) databases
Oracle Enterprise Manager
13.5 and 24ai; runbooks require 24ai
Operating Systems
Linux x86-64 and Windows x86-64 agents, on the Db2 host or remote; local admin jobs, Kill buttons, and diagnostic-log alerting need an agent on the Db2 host
How It Works
Create the Monitoring User
Create a least-privilege monitoring user on each database. It needs no access to table data.
Deploy the Plug-in
Import the plug-in into Oracle EM, then deploy it to the Oracle Management Service and to each agent that will monitor Db2. The JDBC driver is bundled.
Add Targets
Promote the databases each agent host discovers, or add each one as an IBM Db2 Database target with its host, port, monitoring credentials, optional TLS settings, and your license key. Add IBM Db2 Instance targets if you want them.
Monitor and Act
Open Monitoring Readiness to confirm the setup, then the other pages as data arrives. Curated alerts start on their own. Associate the compliance standards, and set admin credentials for the jobs you want to run.
Get a Custom Quote
Ready to add Db2 monitoring to your Oracle Enterprise Manager? Build a quote in minutes and receive detailed pricing by email.
Bring Db2 into Oracle Enterprise Manager
Request a trial license key and monitor IBM Db2 databases and instances from the same console as the rest of your estate.