![Netscape NETSCAPE DIRECTORY SERVER 6.1 - ADMINISTRATOR Administrator'S Manual Download Page 73](http://html1.mh-extra.com/html/netscape/netscape-directory-server-6-1-administrator/netscape-directory-server-6-1-administrator_administrators-manual_1674675073.webp)
Maintaining Referential Integrity
Chapter
2
Creating Directory Entries
73
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:
•
Record referential integrity updates in the replication change log
•
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:
•
You should never enable it on a dedicated consumer server (a server that
contains only read-only replicas).
•
You should never enable it on a server that contains a combination of
read-write and read-only replicas.
•
You can enable it on a master server that contains only read-write replicas.
NOTE
The referential integrity plug-in should only be enabled on one
master 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 NETSCAPE DIRECTORY SERVER 6.1 - ADMINISTRATOR
Page 1: ...Administrator s Guide Netscape Directory Server Version6 1 August 2002...
Page 20: ...20 Netscape Directory Server Administrator s Guide August 2002...
Page 24: ...24 Netscape Directory Server Administrator s Guide August 2002...
Page 142: ...Using Referrals 142 Netscape Directory Server Administrator s Guide August 2002...
Page 440: ...Miscellaneous Tuning Tips 440 Netscape Directory Server Administrator s Guide August 2002...
Page 442: ...442 Netscape Directory Server Administrator s Guide August 2002...
Page 478: ...PTA Plug In Syntax Examples 478 Netscape Directory Server Administrator s Guide August 2002...
Page 498: ...498 Netscape Directory Server Administrator s Guide August 2002...
Page 538: ...Examples of LDAP URLs 538 Netscape Directory Server Administrator s Guide August 2002...