Maintaining Referential Integrity
Chapter 2
Creating Directory Entries
73
How Referential Integrity Works
When the Referential Integrity Plug-in (see “Referential Integrity Postoperation
Plug-in,” on page 505) is enabled, it performs integrity updates on specified
attributes immediately after a delete or rename operation. By default, the
Referential Integrity Plug-in is disabled.
Whenever you delete or rename a user or group entry in the directory, the
operation is logged to the referential integrity log file
(
serverRoot
/slapd-
serverID
/logs/referint
). After a specified time, known as the
update interval
, the server performs a search on all attributes for which referential
integrity is enabled and matches the entries resulting from that search with the
DNs of deleted or modified entries present in the log file. If the log file shows that
the entry was deleted, the corresponding attribute is deleted. If the log file shows
that the entry was changed, the corresponding attribute value is modified
accordingly.
By default, when the Referential Integrity Plug-in is enabled, it performs integrity
updates on the
member
,
uniquemember
,
owner
, and
seeAlso
attributes immediately
after a delete or rename operation. You can, however, configure the behavior of the
Referential Integrity Plug-in to suit your own needs. You can do any of the
following:
• Record referential integrity updates in the replication changelog.
• Modify the update interval.
• Select the attributes to which you apply referential integrity.
• Disable referential integrity.
Using Referential Integrity with Replication
There are certain limitations associated with the use of the Referential Integrity
Plug-in in a replication environment:
NOTE
The Referential Integrity Plug-in should only be enabled on one
supplier replica in a multi-master replication environment to avoid
conflict resolution loops. When enabling the plug-in on servers
issuing chaining requests, be sure to analyze your performance
resource and time needs, as well as your integrity needs. Integrity
checks can be time-consuming and draining on memory/CPU.
Summary of Contents for DIRECTORY SERVER 7.1
Page 1: ...Administrator s Guide Red Hat Directory Server Version7 1 May 2005 Updated February 2009 ...
Page 20: ...20 Red Hat Directory Server Administrator s Guide May 2005 Glossary 619 Index 635 ...
Page 22: ...22 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 26: ...26 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 78: ...Maintaining Referential Integrity 78 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 200: ...Assigning Class of Service 200 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 488: ...488 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 528: ...PTA Plug in Syntax Examples 528 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 572: ...572 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 612: ...Examples of LDAP URLs 612 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 634: ...634 Red Hat Directory Server Administrator s Guide May 2005 ...