On Sat, Dec 13, 2008 at 2:40 PM, Jeff Johnson <firstname.lastname@example.org> wrote:
> On Dec 13, 2008, at 2:50 AM, JD wrote:
>> How do I safely upgrade from rpm 4.4 to rpm 5
>> without destroying my current databse?
>> On one system, the rpm database has become unusable
>> after the upgrade.
>> To wit:
>> # rpm -qa
>> rpmdb: Program version 4.3 doesn't match environment version
>> error: db4 error(-30974) from dbenv->open: DB_VERSION_MISMATCH: Database
>> environment version mismatch
>> error: cannot open Packages index using db3 - (-30974)
>> error: cannot open Packages database in /var/lib/rpm
> There's a version stamp in /var/lib/rpm/__db* files that is
> checked when a Berekeley DB dbenv is 1st opened.
> Remove the version stamp by doing
> rm -f /var/lib/rpm/__db*
> will remedy. Entirely safe on a quiescent system (which is most
> usage cases for an rpmdb, rpm just doesn't run that often to worry).
>> How do I recover from this??
> BTW, rpm5 automates the removal action for the DB_VERSION_MISMATCH
> But that only solves the issue with rpm-4.4.x -> rpm5 upgrades, the
> downgrade requires rpm-4.4.x to handle DB_VERSION_MISMATCH automagically.
This was covered by this Jeff patch
Received on Mon Dec 15 18:30:42 2008