Bug 231652 – migration: support conversion of bdb 4.2 files to bdb 4.3 and later

Bug 231652 - migration: support conversion of bdb 4.2 files to bdb 4.3 and later

Summary:	migration: support conversion of bdb 4.2 files to bdb 4.3 and later

Status:	CLOSED DUPLICATE of bug 232050

Aliases:	None

Product:	389
Classification:	Community
Component:	Database - General (Show other bugs)
Sub Component:
Version:	1.0.4
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Noriko Hosoi
QA Contact:	Orla Hegarty
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	152373 240316
	Show dependency tree / graph

Reported:	2007-03-09 15:15 EST by Rich Megginson
Modified:	2007-05-16 09:56 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-03-20 16:30:20 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Rich Megginson 2007-03-09 15:15:18 EST

In order to support migration from ds 7.1 and 1.0.x to 1.1 (and 7.2), we need to
be able to support upgrading the bdb files created with 4.2 to 4.3 and later. 
Fedora only supports bdb 4.3 now, and will support 4.5 and 4.6 in the near
future.    During migration, we should be able to copy the database
files/directories to their new location (e.g. from
/opt/fedora-ds/slapd-instance/db to /var/lib/fedora-ds/slapd-instance/db) and
when the new server instance starts up, it should upgrade the new db files.

Comment 1 Noriko Hosoi 2007-03-20 16:30:20 EDT

I used the original bug 232050 "Change format of DBVERSION and guardian files"
for this issue.  (See the Comment #4 and #6)

*** This bug has been marked as a duplicate of 232050 ***

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