topic Re: Error from rpm command in Operating System - Linux

Error from rpm command

chai choon keet — Wed, 06 Jul 2005 22:21:24 GMT

Hi,
I'm installing an OVO Unix agent into the Linux Redhat Enterprise version 2.4

The installation failed with error msg:-

error: rpmdbNextIterator: skipping h# 614 blob size(16916): BAD, 8 + 16 * il
(57) + dl(9696)

error: rpmdbNextIterator: skipping h# 615 blob size(15988): BAD, 8 + 16 * il
(538976288) + dl(538976288)

error: rpmdb: damaged header #615 retrieved -- skipping.
error: rpmdb: damaged header #615 retrieved -- skipping.

please help. thanks

Re: Error from rpm command

Ivan Ferreira — Wed, 06 Jul 2005 23:57:41 GMT

Make sure the package you want to install is not corrupt. You may try to rebuild/recreate the rpm database with:

rpm {--initdb|--rebuilddb}

You may need to delete the db files from /var/lib/rpm

Re: Error from rpm command

Gopi Sekar — Thu, 07 Jul 2005 01:47:05 GMT

looks like the rpm package is corrupted, try to download it again and use it

Re: Error from rpm command

Ross Minkov — Wed, 13 Jul 2005 09:44:00 GMT

Here is a quick RPM db troubleshooting HOWTO.

First try this:

# rm -f /var/lib/rpm/__db*

If you still have problems with rpm after that try to rebuild the db:

# cd /var/lib; mkdir rpm-backup
# rsync -av ./rpm/. ./rpm-backup/.
# rpm -vv --rebuilddb

The first 2 lines above will backup your RPM db. Always make a backup before trying to have rpm repair the database.

If you still have problems with the RPM database you can use the db_dump and db_load utilities that come with RPM (from the SleepyCat DB database library). Use dp_dump to dump the Packages file then use db_load to reload the Packages file. The act of dumping and restoring may fix a corrupted file.

# cd /var/lib/rpm
# db_verify Packages
# mv Packages Packages-ORIG
# db_dump Packages-ORIG | db_load Packages
# rpm -vv --rebuilddb

HTH,
Ross

Re: Error from rpm command

Ross Minkov — Wed, 13 Jul 2005 09:46:34 GMT

One more thing I forgot to mention -- before running any of the commands I provided in my previous posting make sure that you don't have any rpm processes running. Use ps to check. For example:

ps auxw | grep -i rpm