RPM Database Corruption on RHEL 9

📖 ~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

rpm and dnf fail with database errors, often after abrupt power loss or interrupted transactions.

Environment & Reproduction

Errors include rpmdb open failed or BDB/SQLite backend access issues while querying packages.

Root Cause Analysis

Unclean shutdown, disk I/O errors, or stale lock files inside /var/lib/rpm.

Quick Triage

Check filesystem health, free space, and run rpm -qa | head to confirm read failures.

Step-by-Step Diagnosis

Backup /var/lib/rpm and remove stale lock artifacts before rebuilding the database.

Solution – Primary Fix

Run sudo rpm –rebuilddb, then sudo dnf check to validate package metadata integrity.

Solution – Alternative Approaches

Pause automated patch jobs while repairing to avoid concurrent rpm transactions.

Verification & Acceptance Criteria

Restore labels on /var/lib/rpm with restorecon -Rv /var/lib/rpm if contexts are inconsistent.

Rollback Plan

Execute dnf update –assumeno and rpm -Va sampling to ensure normal behavior.

Prevention & Hardening

If rebuild fails, restore the backup copy of /var/lib/rpm and investigate storage corruption.

Related Errors & Cross-Refs

Use reliable power protection and avoid killing dnf/rpm processes mid-transaction.

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

rpm –rebuilddb; dnf check; journalctl -p err -b –no-pager