Bug 13660 - Upgrading from db3 to db 3.1 breaks RPM database
Upgrading from db3 to db 3.1 breaks RPM database
Status: CLOSED WONTFIX
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm (Show other bugs)
1.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-07-10 16:47 EDT by compwiz
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-07-10 16:47:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description compwiz 2000-07-10 16:47:38 EDT
Here's the situation:
Started with rpm 3.0.4, then upgraded to the CVS version of RPM 4.0, and
the database rebuild ended up OK while using db3 from the june rawhide
RPMs. However, after upgrading to the latest rawhide db3.1 RPM, and then
installing either the rawhide rpm-4.0-0.45, or latest CVS rpm-4.0, after
doing an rpm --rebuilddb, all databases in /var/lib/rpm basically get
erased, and when installing an RPM, i get:

db3 error(-30990) performing db->open: DB_OLDVERSION: Database requires a
version upgrade
db3 error(-30990) performing db->open: DB_OLDVERSION: Database requires a
version upgrade
dbiOpen: cannot open Triggername index
terraform                  
##################################################
  +++          6 terraform-0.7.1-1
db3 error(-30990) performing db->open: DB_OLDVERSION: Database requires a
version upgrade
db3 error(-30990) performing db->open: DB_OLDVERSION: Database requires a
version upgrade
Comment 1 Jeff Johnson 2000-07-10 18:59:32 EDT
Yup.  Convert the databases using db_dump and db_load something like (untested)

	cd /var/lib/rpm
	mkdir -p ../rpmnew
	for F in *
	do
	    db_dump $F | db_load -t hash ../rpmnew/$F
	done
Make sure you use the db_dump/db_load from the db3-3.1.14 package.

Note You need to log in before you can comment on or make changes to this bug.