Bug 472475

Summary:	Add -r argument to db2ldif documentation
Product:	Red Hat Directory Server	Reporter:	Rich Megginson <rmeggins>
Component:	Doc-administration-guide	Assignee:	Deon Ballard <dlackey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Content Services Development <ecs-dev-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	8.0	CC:	jgalipea, klamb, msauton, tao
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	8.1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-04-29 23:08:06 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:
Bug Depends On:
Bug Blocks:	249650

Description Rich Megginson 2008-11-21 01:14:30 UTC

Specifically
http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Managing_Replication-Initializing_Consumers.html
8.10.4.1. Exporting a Replica to LDIF

We need to mention here that the -r argument is required in order to create an LDIF file that can be used for replica initialization.  We also need to document -r here:
http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Populating_Directory_Databases-Exporting_Data.html#Exporting_Data-Exporting_to_LDIF_from_the_Command_Line
4.2.3. Exporting to LDIF from the Command-Line

With a note to say that -r is required to create a replica init LDIF file.

Also here:
Table 4.4. db2ldif Options

Comment 5 Jenny Severance 2009-03-17 18:49:01 UTC

verified 8.1 Admin guide
  8.10.4.1. Exporting a Replica to LDIF

verified 8.1 Admin guide
  4.2.3.1. Exporting a Database Using db2ldif or db2ldif.pl

verified 8.1 Configuration, Command, and File Reference
  7.3.5. db2ldif (Exports Database Contents to LDIF)

Comment 6 Chandrasekar Kannan 2009-04-29 23:08:06 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/RHEA-2009-0455.html