RPM DB_RUNRECOVERY errors will no longer be a worry with Bobcares by your side.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team recently helped a customer resolve rpm DB_RUNRECOVERY errors.

What are RPM DB_RUNRECOVERY errors?

Did you know that certain conditions that can lead to corruption of the RPM database? According to our Support Team, this is usually due to an interruption during installations or updates. In some cases, it may also be due to packaging errors.

Here is a look at some of the commonly seen RUNRECOVERY errors as a result of a corrupt RPM database:

error: db4 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db4 - (-30974)
error: cannot open Packages database in /opt/freeware/packages
error: rpmdb: Thread/process 32244334/1 failed: Thread died in Berkeley DB library
error: db4 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db4 - (-30974)
error: cannot open Packages database in /opt/freeware/packages

How to resolve RPM DB_RUNRECOVERY errors?

Our Support Techs suggest checking whether the rpm.rte is lower than 4.13.0.4 or not. If yes, it is time to update it to the latest version. In 4.13.0.4, the Toolbox release isolated the runtime files that are sometimes overwritten by non_IBM provided RPM packages.

However, if updating does not resolve the errors, try your hand at the following steps:

1. First, we will change the directory to the RPM database directory with this command:

   cd /opt/freeware

2. Then, we have to make a backup as seen below:

   tar -chvf `date +"%d%m%Y"`.rpm.packages.tar packages

3. Next, we will remove the _db* lockfiles that are in use by the RPM with this command:

   rm -f /opt/freeware/packages/__*

4. After that, we will rebuild the database with the following command:

   /usr/bin/rpm –rebuilddb

5. Finally, we will test the rpm command again as seen below:

   /usr/bin/rpm -qa

[Need help with a different query? We are available 24/7.]

Conclusion

In conclusion, the skilled Support Engineers at Bobcares demonstrated how to resolve rpm DB_RUNRECOVERY errors.