RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Out of a sudden all rpm operations fail with this error message:
# rpm -q pacemaker
error: rpmdbNextIterator: skipping h#     546 Header SHA1 digest: BAD
[.. can repeat many times ...]

So far I was unable to find out what caused it. It happened two times to me so far (two different installations).

Version-Release number of selected component (if applicable):
# yum --version
3.2.29
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
  Installed: rpm-4.8.0-37.el6.x86_64 at 2013-09-19 12:08
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2013-09-12 10:55
  Committed: Panu Matilainen <pmatilai> at 2013-09-12

  Installed: subscription-manager-1.9.6-1.el6.x86_64 at 2013-09-19 12:10
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2013-09-12 20:11
  Committed: jesus m. rodriguez <jesusr> at 2013-09-12

  Installed: yum-3.2.29-40.el6.noarch at 2013-09-19 12:08
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2013-01-08 17:02
  Committed: James Antill <james.antill> at 2013-01-08


How reproducible:
not sure

Steps to Reproduce:
1. unknown
2.
3.

Actual results:
RPM commands start failing suddenly

Expected results:
no db corruption

Additional info:

Created attachment 806395 [details]
corrupted RPM database

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Attached rpmdb doesn't seem to be corrupeted. I extracted your tarball in rhel-6.5 system and successfully executed following command (where /root/rpm is path to extracted rpmdb):

# rpm --dbpath /root/rpm -q pacemaker
pacemaker-1.1.10-9.el6.x86_64

Also other commands worked as expected. Did you encounter this error right after installation? If yes then what kind of installation did you perform (default installation or some special steps)? If no then what steps did you perform in installed system before error occured?