Bug 454857

Summary:	db-4 in openldap needs new patches
Product:	Red Hat Enterprise Linux 5	Reporter:	Jan Safranek <jsafrane>
Component:	openldap	Assignee:	Jan Safranek <jsafrane>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	5.2	CC:	jplans
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-20 20:53:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Safranek 2008-07-10 08:55:06 UTC

Description of problem:
We shop openldap-servers with it's own version of Berkeley DB. Currently we ship
ver. db-4.4.20, with two official patches. Upstream released additional two
patches, improving the stability of the database.

We should apply these patches to prevent database corruption. See
http://www.oracle.com/technology/products/berkeley-db/db/update/4.4.20/patch.4.4.20.html
for description - we ship the first two, I'd like to add the later ones.

There is no reproducer. The database gets corrupted in very specific conditions
only - see the patch description.

Comment 1 RHEL Program Management 2008-07-10 09:00:27 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 6 errata-xmlrpc 2009-01-20 20:53:45 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0090.html