System information
Known Issues and Limitations
Page 22 of 3 2Directory Server 5. 22004Q 2 •Release Notes
For replication to function after the set of attributes to be replicated by fractional replication has been
modified, the consumer needs to be re-initialized twice (#4977320)
If you modify the set of attributes to be replicated by fractional replication, then replication will not
work unless you re-initialize the consumer twice.
Workaround
Either re-initialize the consumer twice or make the necessary changes to the replication agreement
in two stages, that is first remove the existing fractional replication filter and save the replication
agreement. Then set the new fractional replication filter and save the replication agreement. This
two-step procedure prevents you from having to initialize the consumer twice (which is a
preferable workaround if you are working with large databases).
Adding an entry with objectClass=nstombstone may cause replication to fail (#5021269)
Workaround
Avoid adding entries with
objectClass=nstombstone
Using the scheduled replication functionality may result in erratic replication behavior (#4999132)
Workaround
Avoid using scheduled replication and configure replication to always be in sync.
In a multi-master replication configuration (with at least 3 master replicas) where the masters are being
updated simultaneously with heavy traffic loads, you may experience latency peaks (#5006198)
Benign error message written to the error log during replication sessions (#5029597)
During replication sessions the following benign error message may be written frequently to the
error log thus increasing the error log file size:
[09/Apr/2004:06:47:45 +0200] - INFORMATION - conn=-1 op=-1 msgId=-1 -
csngen_adjust_time: remote offset now 33266 sec
This error message can be ignored.
Conformance
Issues arose when both LDAP v2 and LDAPv3 applications use certificate related attributes (#4819710)
This bug has been fixed but has resulted in the creation of a new configuration attribute
nsslapd-binary-mode
under
cn=config
, as yet undocumented.