Software⏱️ 3 min read📅 2026-06-15

How to Fix: Linux rpm -Uvh (error: can't create transaction lock on /var/lib/rpm/__db.000)?

Fixing Linux rpm -Uvh error due to corrupted database.

Quick Answer: Run `rpm --rebuild` on the corrupted package and try installing again.

📋 Table of Contents

  1. 💡 Why You Are Getting This Error
  2. 🛠️ Step-by-Step Verified Fixes
  3. ✨ Wrapping Up

The error 'can't create transaction lock on /var/lib/rpm/__db.000' occurs when the rpm database becomes corrupted, which can happen due to incomplete or interrupted package installations. This issue affects users of Linux distributions that use RPM (Red Hat Package Manager) for package management.

This error is frustrating because it prevents the installation process from completing successfully, leaving the system in an unstable state. However, with the right troubleshooting steps, you can resolve this issue and continue with your package installation.

💡 Why You Are Getting This Error

  • The primary reason for this error is a corrupted rpm database. This can occur due to incomplete or interrupted package installations, where the rpm process was terminated abruptly without completing the transaction.
  • Another possible cause is an incorrect configuration of the rpm database, which can lead to issues with file locking and database integrity.

🛠️ Step-by-Step Verified Fixes

Reinstalling the RPM Database

  1. Step 1: Step 1: Stop any running package managers or daemons that may be interfering with the rpm process. You can do this by running `systemctl stop --now yum` or `systemctl stop --now rpm`. This will ensure that no other processes are trying to access the rpm database while you attempt to repair it.
  2. Step 2: Step 2: Remove any existing corrupted packages from the system using `rpm --erase `. Be cautious when using this command, as it may remove important system packages. It's recommended to only remove packages that you know are corrupt or unnecessary.
  3. Step 3: Step 3: Reinstall the rpm database by running `rpm --rebuild /var/lib/rpm/__db.000` and then `rpm --rebuild /var/lib/rpm/__db.001` (if applicable). This will recreate the rpm database from scratch, potentially resolving any corruption issues.

Alternative Fix Method: Using 'rpm --forcebad`

  1. Step 1: Step 1: Run `rpm --forcebad /var/lib/rpm/__db.000` to force the creation of a new transaction lock file. This command will attempt to repair any corrupted database files and create a new lock file if necessary.
  2. Step 2: Step 2: If the above command fails, you may need to use `rpm --rebuild /var/lib/rpm/__db.000` to recreate the rpm database from scratch.

✨ Wrapping Up

By following these troubleshooting steps, you should be able to resolve the 'can't create transaction lock on /var/lib/rpm/__db.000' error and continue with your package installation successfully. If the issue persists, it may be worth seeking further assistance from a Linux expert or the distribution's support team.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions

🛠️ Related Fixes

How to Fix: Pc crashes shortly after launching game (rainbow

Fix Pc crashes shortly after launching game (rainbow six siege). Compl

How to Fix: Installing an APK on a locked down phone

Installing an APK on a locked down phone: Try using a rooted device, e

How to Fix: New PC build- no signal and no clue

Fix New PC build- no signal and no clue. Complete troubleshooting guid