Originally posted by warheros
THAT is what i dont know how to do.
Ok, I've had to do that before. Let's see:
$ locate db|grep _|grep rpm
gets among others two possible locations:
I'm thinking /var/lib but not certain.
The command to rebuild the database I recall as "rpm --rebuilddb" and a quick look "man rpm" confirms this. Well, not too quick, it's a long man page. It also indicates at the end of the man page that database files are in /var/lib/rpm and a quick Google search yields at least one reference to deleting them, so I'm pretty sure it's the three _db files in /var/lib/rpm that you need to delete. It's a known bug in rpm, as I recollect. Particularly it can happen if rpm has to be killed with a kill -9 I seem to recall.
So, I would log in as root. I'd do something like:
mv _db.001 _db.001.bak
mv _db.002 _db.002.bak
mv _db.003 _db.003.bak
ps -ef|grep rpm
If any hung rpm processes exist then do a kill pid# where pid# is the first number following the process and verify that they are gone.
That last may take some time. Then verify that you have 3 new _db files and you can delete the _db...bak old corrupted _db files.
If that procedure does not fix things then I will suspect that in not having disk 3 you didn't install some critical file for rpm functionality OR you had a corrupted disk 1 or disk 2 (did you check the checksums on them when you downloaded?)
Hopefully, though the process above will fix things.
BTW I'm running RH 9 so the locations mentioned should be the same.