Automatically verify and repair the RPM database.
RPM's developer, Jeff Johnson, says that such checks are inadequate and not needed and, by their use of RPM, can themselves lead to corruption of the RPM database. Every part of this viewpoint seems extreme to me.
Normally the RPM database is reliable, but, as it is normally never checked, if it starts to go bad there will be no warning until it completely falls over, usually when installing updates. At this writing, the new Fedora 6 appears to have some issues with corrupting the RPM database, making this sort of tool more immediately necessary.
I am not experienced with the internals of RPM. This tool follows the docs for RPM and also info gleaned from googling about (--verifydb is undocumented). I try to follow best practices for safely checking, repairing, replacing, and logging, but there may be problems. (RPM's developer, Jeff Johnson, says that the check I'm doing is inadequate and not needed and, by its use of RPM, can itself lead to corruption of the RPM database. Every part of this point of view seems extreme to me. See the thread at Redhat's rpm-list, "SUG: Automatic RPM database verification and repair".)
Download and install the RPM in the usual way. I don't expect that any configuration will be needed, so I haven't really allowed for any.