The RPM database gets frequently corrupted, so it is impossible to instal or uninstall any package, or update the current ones.

[Jeff Johnson]

Tracker

[Publio-escipion-el-africano (publio-escipion-el-africano)]

Created an attachment (id=379720)
YaST2 Install's More Informationoutput

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.1.11) Gecko/20100714 SUSE/3.5.11-0.1.1 Firefox/3.5.11

The RPM database gets frequently corrupted, so it is impossible to instal or uninstall any package, or update the current ones.

It is the third time that I have this most unusual issue with openSuSE 11.2 since December 2009, and I never had it with SuSE before.

Fortunately, it seems to be solved through
rpm --rebuilddb
as root, but, however, I had to reinstall once all my system to get the package system to work earlier this year.
It is annoying and worrying at last. Thrice is too much!
I do not know how to reproduce it, and I was worrier by other issues, so I did not reported before. However, the recurrence compels me to do it.
This time the issue took place while updating bundle-lang-gnome-en and bundle-lang-gnome-es (bundle-lang-gnome-en-11.2-20.23.5.noarch.rpm and bundle-lang-gnome-es-11.2-20.23.5.noarch.rpm from the openSuSE 11.2's Update repository), but it could be any else package from any else repository, although currently I can not remember precisely which ones I had this before.

Reproducible: Sometimes

Steps to Reproduce:
1. (See above.)
2.
3.
Actual Results:
(See above and attachment.)

Expected Results:
Not a fourth.

The above attachment is what YaST2 Install showed about what happened.

[Mls-i (mls-i)]

Hmm, "frequently corrupt" sounds like you have some bad memory in your system. Can you please run "memcheck" or something like it to make sure it is not a hardware issue?

[Publio-escipion-el-africano (publio-escipion-el-africano)]

I am sorry for the delay, but I was in a hurry preparing a paper for a Congress, and, although I read your comment in time, as I did not know how much time, which I hadn't, doing it could take me, I decided to postpone the test after I had already finished and send the painful-text.
So...
The issue has taken place in two different computers: my Desktop computer and my laptop. 2/1, the more luckless was my laptop. Both were memory-tested through BIOS built-in test utility and memtest. Both are fine.

[Mls-i (mls-i)]

We updated the berkeley db version used by rpm in newer opensuse versions, the database stability seems to have improved.