DB2 UDB Observability

📊 DB2 UDB Monitoring

GermainUX monitors the availability, performance, capacity, and operational health of IBM Db2 UDB databases.

⚙️ Monitoring component

📂 Data sources

GermainUX can monitor Db2 through:

The available monitoring depth depends on the permissions granted to the GermainUX database account and the data sources configured for the environment.

✨ Capabilities

Database availability

GermainUX can regularly test Db2 connectivity and detect:

• An unavailable database.

• Connection failures.

• Authentication problems.

• Connection timeouts.

• Unexpected response times.

• Recurring or intermittent availability problems.

Availability results can be analyzed over time and used for SLAs, Watches, reports, and approved actions.

Tablespace utilization

Using SYSIBMADM.TBSP_UTILIZATION, GermainUX can monitor available tablespace information such as:

• Tablespace utilization.

• Used and available capacity.

• Tablespaces approaching an approved threshold.

• Growth trends.

• Tablespaces requiring operational review.

This helps teams act before insufficient space affects database availability or application processing.

Transaction-log utilization

Using SYSIBMADM.LOG_UTILIZATION, GermainUX can monitor available transaction-log utilization and identify:

• High log consumption.

• Reduced available log capacity.

• Abnormal changes in utilization.

• Conditions approaching an operational threshold.

Locks and lock waits

Using SYSIBMADM.LOCKS_HELD and SYSIBMADM.LOCKWAITS, GermainUX can monitor:

• Held locks.

• Waiting applications.

• Lock-wait duration.

• Lock contention.

• Recurring blocking patterns.

• Applications or transactions associated with lock waits.

Deadlocks or lock timeouts can also be detected when the relevant information is available through configured Db2 views, queries, or logs.

Application performance

Using SYSIBMADM.APPL_PERFORMANCE and SYSIBMADM.APPLICATIONS, GermainUX can monitor available application and connection information, including:

• Connected applications.

• Active database activity.

• Application-performance measurements.

• Connection volume.

• Long-running or unusually active applications.

• Changes in application behavior.

The exact fields available depend on the Db2 version and administrative-view definitions.

Buffer-pool performance

Using SYSIBMADM.BP_HITRATIO, GermainUX can monitor available buffer-pool hit-ratio information and identify:

• Low hit ratios.

• Performance degradation over time.

• Differences between buffer pools.

• Conditions that may require database-administration review.

A low hit ratio is evidence for investigation; it does not by itself establish the root cause of poor application performance.

Long-running SQL

Using SYSIBMADM.LONG_RUNNING_SQL, GermainUX can detect and analyze SQL activity that exceeds the criteria exposed by Db2.

GermainUX can help identify:

• Long-running statements.

• Recurring slow SQL patterns.

• Applications associated with long-running SQL.

• Trends in statement duration.

• The users, systems, or business processes affected when correlation identifiers are available.

Execution plans, index usage, or additional SQL diagnostics require separate approved queries or Db2 interfaces that expose that information.

Connections

GermainUX can monitor available connection and application information to identify:

• Increasing connection volume.

• Unexpectedly persistent connections.

• Applications creating excessive connections.

• Connection failures.

• Connection usage approaching an operational threshold.

Identifying a connection leak requires evidence over time and appropriate application context; a high connection count alone does not prove a leak.

Backup and recovery status

GermainUX can monitor backup and recovery information when it is accessible through an approved:

• Db2 administrative view.

• SQL query.

• Operating-system command.

• Db2 log.

• Backup-management table or integration.

Possible monitoring includes backup status, last successful backup, failure events, duration, or age. These checks are not available automatically unless the necessary data source has been configured.

Db2 errors and logs

GermainUX can monitor accessible Db2 logs and event files to detect:

• Errors.

• Warnings.

• Availability events.

• Authentication or connection failures.

• Storage and transaction-log conditions.

• Backup failures.

• Recurring or newly observed messages.

Log monitoring requires the GermainUX Engine to have approved read access to the relevant files or a supported mechanism for retrieving them.

Server and operating-system health

Db2 system views do not provide every host-level metric. Deploy the applicable operating-system monitoring when CPU, memory, disk, process, and network visibility is required.

Depending on the Db2 server platform, GermainUX can monitor:

• CPU usage and queue length.

• Memory and swap utilization.

• Disk usage and I/O.

• Network availability and utilization.

• Db2 processes and services.

• Operating-system errors and logs.

Business benefits

DB2 UDB Monitoring helps organizations:

• Detect database outages and degradation before more users are affected.

• Prevent tablespace and transaction-log capacity problems.

• Identify lock contention and long-running SQL.

• Determine which applications or connections contribute to a problem.

• Correlate database degradation with application and business impact.

• Reduce the time required to diagnose intermittent Db2 issues.

• Prioritize problems according to their frequency and operational impact.

• Validate database, application, infrastructure, and configuration changes.

• Automate approved notifications, diagnostics, and corrective actions.

Analytics

GermainUX can analyze Db2 data through KPIs, measures, pivots, trends, drill-through views, correlations, and outlier detection.

Custom KPIs can be created from any approved query result that can be converted into a GermainUX event, metric, or transaction.

Outlier detection

GermainUX can detect abnormal Db2 behavior such as:

• Unusual tablespace growth.

• Spikes in transaction-log utilization.

• Increased lock waits.

• Abnormal connection volume.

• New long-running SQL patterns.

• Changes in buffer-pool performance.

• Increased error frequency.

• Performance that differs significantly from the established baseline.

Outlier detection identifies behavior requiring investigation; it does not automatically prove a specific root cause.

Notification and automation

GermainUX users can create Watches to receive notifications when existing Db2 insights meet conditions of interest.

Detected conditions can also trigger approved GermainUX actions, including:

• Email or other configured notifications.

• Reports.

• HTTP requests or webhooks.

• Diagnostic SQL queries.

• Scripts or local programs.

• Incident-management integrations.

• Approved corrective workflows.

Database-changing SQL, process restarts, or recovery commands should only be automated with explicit authorization, least-privilege credentials, validation, safeguards, and rollback procedures.

Minimum database permissions

Basic database-availability monitoring requires a regular Db2 account with CONNECT permission.

Deeper monitoring requires SELECT permission on the administrative views used by the configured monitors:

These permissions represent the documented minimum for the corresponding preconfigured monitoring. Additional custom queries require access to their referenced views or tables.

Grant only the permissions required by the selected monitoring use cases.

Prerequisites

Before deployment, confirm:

• A GermainUX Engine can reach the Db2 host and port.

• The compatible Db2 JDBC driver is available to the Engine.

• The target database and schema information is known.

• A dedicated least-privilege monitoring account is available.

• Required administrative-view permissions have been granted.

• TLS and certificate requirements are understood.

• Network and firewall rules permit the connection.

• The monitoring schedule and expected query load are approved.

• Any required log or operating-system access is available.

• Credentials can be stored securely in GermainUX.

Configuration

Add the Db2 data source

1. Open Germain Workspace.

2. Go to Data Sources > Database.

3. Select Add New Configuration.

4. Enter the Db2 host, port, database, and connection properties.

5. Select the applicable Db2 JDBC driver.

6. Configure TLS properties when required.

7. Test the connection.

8. Save the data source.

Add credentials

1. Go to Data Sources > Credentials.

2. Create or select a dedicated Db2 monitoring credential.

3. Enter the approved username and password.

4. Associate the credentials with the Db2 data source.

5. Test access using the intended monitoring permissions.

Run the Db2 wizard

1. Go to Wizards > DB2 UDB.

2. Select the monitoring node and GermainUX Engine.

3. Select the Db2 data source and credentials.

4. Select the required preconfigured monitoring capabilities.

5. Configure the execution schedule.

6. Review the generated components.

7. Finish the wizard.

8. Verify that the components appear in Germain State.

Available wizard screens and component names can vary by GermainUX version.

Add a Database Query Monitor

Use a Database Query Monitor when a required metric is not included in the preconfigured Db2 monitoring:

1. Go to Wizards > Database Query Monitor Deployment.

2. Select the Db2 data source and credentials.

3. Enter the approved SQL query.

4. Validate the query.

5. Select or create the KPI.

6. Map the query result to the required event, metric, or transaction.

7. Configure the execution schedule.

8. Select the monitoring node and Engine.

9. Finish the wizard.

10. Validate the collected data.

Custom monitoring queries should be read-only, efficient, bounded, and reviewed by the Db2 administrator before production deployment.

Configure an SLA

When an SLA is required:

1. Select the Db2 KPI.

2. Define the applicable static or statistical condition.

3. Select the evaluation window.

4. Configure the approved actions.

5. Validate the condition with controlled data before enabling production notification or automation.

Security

Use a dedicated monitoring account and follow these requirements:

• Grant CONNECT and only the required SELECT permissions.

• Do not use a Db2 administrator account unless specifically required and approved.

• Do not grant write permissions for read-only monitoring.

• Store credentials in GermainUX credential management.

• Use TLS where required.

• Restrict network access to the GermainUX Engine.

• Avoid collecting sensitive business rows through custom queries.

• Do not include passwords, tokens, or personal data in KPI details.

• Audit custom SQL and automated actions.

• Rotate credentials according to organizational policy.

Validation

After deployment:

1. Confirm that the GermainUX Engine can connect to Db2.

2. Verify each configured administrative view using the monitoring account.

3. Confirm that Db2 KPIs appear in GermainUX.

4. Compare selected values with an approved Db2 administrative tool.

5. Generate a controlled threshold condition when safe.

6. Verify the associated SLA or Watch.

7. Confirm that no monitoring query creates unacceptable database load.

8. Test credential rotation.

9. Validate any configured log or operating-system monitoring.

10. Review access and collected data with the Db2 security owner.

Deployment and configuration

ℹ️ Get Help

The Germain Team can help you set this up. Contact GermainUX Support.