RPM Database Corruption After Interrupted Transaction

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

dnf and rpm commands fail with database or BDB/SQLite consistency errors on RHEL 9.

Environment & Reproduction

Run `rpm –verifydb` and confirm available disk space in `/var` before repair steps.

Root Cause Analysis

Confirm core RPM tools with `rpm -q rpm dnf python3-dnf` to detect missing dependencies.

Quick Triage

Check whether unattended update units are active via `systemctl list-timers | grep dnf`.

Step-by-Step Diagnosis

Inspect `journalctl –since -4h` and `/var/log/dnf.log` around the failed transaction window.

Solution – Primary Fix

Backup `/var/lib/rpm` and package logs prior to any database rebuild operation.

Solution – Alternative Approaches

No inbound change is usually needed, but verify outbound repo connectivity after repair.

Verification & Acceptance Criteria

Validate default labels in `/var/lib/rpm` with `restorecon -Rv /var/lib/rpm` when contexts drift.

Rollback Plan

Rebuild with `sudo rpm –rebuilddb`, then run `sudo dnf distro-sync` to realign package state.

Prevention & Hardening

Confirm `rpm -qa | head` and `dnf check` complete without DB errors.

Related Errors & Cross-Refs

Avoid abrupt power loss during updates and use transactional maintenance windows.

Related tutorial: View the step-by-step tutorial for rhel-9.

View all rhel-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Provide rpmdb backups, filesystem health checks, and exact error traces from `journalctl`.