Bug 13660 - Upgrading from db3 to db 3.1 breaks RPM database
Summary: Upgrading from db3 to db 3.1 breaks RPM database
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-07-10 20:47 UTC by compwiz
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-07-10 20:47:39 UTC
Embargoed:


Attachments (Terms of Use)

Description compwiz 2000-07-10 20:47:38 UTC
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 22:59:32 UTC
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.