The interface is localized. Skill descriptions and documents are machine-translated by AI into your language; code, commands, paths and technical terms stay in the original, and the author's document governs.
Explore skills
Data & research · SKILL.md

db2-rhel

db2-rhel

Use when installing, configuring, or managing IBM DB2 LUW on RHEL 9 (and AlmaLinux/Rocky 9) — instance creation, database administration, buffer pool and tablespace management, backup/restore with HADR, performance tuning (db2advis, db2pd, MON functions), runstats/reorg, SELinux contexts, firewalld rules, and DB2 pureScale. Part of the db2-* skill family.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill documentation

GitHub

name: db2-rhel description: Use when installing, configuring, or managing IBM DB2 LUW on RHEL 9 (and AlmaLinux/Rocky 9) — instance creation, database administration, buffer pool and tablespace management, backup/restore with HADR, performance tuning (db2advis, db2pd, MON functions), runstats/reorg, SELinux contexts, firewalld rules, and DB2 pureScale. Part of the db2-* skill family. disambiguation: DB2 LUW specifically, on RHEL. Other engines on RHEL are rhel-databases; DB2 for z/OS is db2-mainframe; MQ messaging is ibm-mq.

IBM DB2 LUW — Administration on RHEL 9

Companion skill to rhel-server-admin and rhel-databases. For Python DB2 connectivity see python-enterprise-connectors.


Reference Files

Detailed code examples, patterns, and configuration are in the reference files below. Read the relevant file when working on that area.

FileCovers
install-admin.mdDB2 installation on RHEL, instance management, and database administration (tablespaces, buffer pools, schemas, tables)
performance-monitoring-rhel.mdperformance tuning (db2advis, db2pd, MON functions), monitoring, maintenance, RHEL-specific configuration, and DB2 pureScale
security-backup-recovery.mdDB2 security (authentication, authorization, roles, audit), backup strategies, and HADR recovery


Anti-Patterns

Anti-PatternWhy It FailsCorrect Approach
Running DB2 with default buffer pool sizesDefault 1000 pages is far too small for production; excessive disk I/O, poor query performanceSize buffer pools based on workload: OLTP needs 60-80% of data in memory; run db2pd -bufferpools to monitor hit ratio
Skipping RUNSTATS after bulk data loadsOptimizer uses stale cardinality estimates; queries that were fast become full table scansRun RUNSTATS WITH DISTRIBUTION on tables and indexes after every significant data change
Using HADR without automatic client rerouteFailover happens but applications cannot find the new primary; manual intervention requiredConfigure ALTERNATE SERVER in database directory and enable ACR in application connection strings
Not setting LOGFILSIZ and LOGPRIMARY appropriatelyDefault log sizes cause log-full conditions during batch loads; transactions roll back and retry endlesslySize transaction logs based on largest expected transaction; monitor with db2pd -logs; set LOGSECOND as overflow
Running backup without testing restoreBackup jobs succeed but restore fails due to missing log files, wrong paths, or version mismatchTest restore to a different instance quarterly; validate with RESTORE DB ... WITHOUT ROLLING FORWARD

Related Skills

WorkloadSkill
Core RHEL admin (dnf, SELinux, firewalld, LVM)rhel-server-admin
PostgreSQL, MySQL, Redis on RHELrhel-databases
Python DB2/Oracle/SQL Server connectorspython-enterprise-connectors
Web servers (Nginx, Apache, Caddy)rhel-web-servers
Docker / Podman containersrhel-docker-host
Monitoring (Prometheus, Grafana, PCP)rhel-monitoring
Saved skills