System information

Bugs Fixed in This Release
Page 6 of 32Directory Server 5.22004Q2•Release Notes
Table 5 Installation, Uninstallation, and Migration Related Bugs Fixed in Directory Server 5. 2
Bug Number Description
4944732 The
unconfigure
subcommand of the
directoryserver
command hung due to a shared
ServerRoot directory.
Table 6 Replication Related Bugs Fixed in Directory Server 5. 2
Bug Number Description
4719793 ACIs on
cn=schema
branch of the
cn=config
tree were not replicated.
4863943 When a master replica was disabled, the replica ID changed, and the replica then brought back
online, two replica IDs continued to co-exist which resulted in duplicate error messages when
setting referrals.
4870522 If there was a link failure on the network for more than 5 minutes then the replication session timed
out.
4881004 The change log was not purged by default.
4887252 In the knowledge that operations are grouped before the RUV is updated, If:
- a replication session had executed an
ldapmodify
delete attribute operation,
- then, on the same entry, had executed any other type of
ldapmodify
operation (which would
have resulted in the attribute state information being purged from the entry),
- and finally, the same replication session was aborted abruptly before all operations which would
normally have triggered a RUV update had been executed,
then a subsequent replication session would attempt to replay the same operations as it would
have no RUV record of them having already been executed. On attempting to replay the
ldapmodify
delete attribute operation, the replication session would fail as it would have no record
that the attribute it was trying to delete had in fact ever existed.
4891228 The server sometimes crashed if change log trimming was enabled.
4892676 The replication monitoring tool
repldisc
did not function correctly when multiple Directory Server
instances were installed on the same machine.
4911678 At startup time the RUV object was sometimes NULL, which caused the server to crash.
4923860 Certain long (>240 characters) DNs containing “,” or “;” characters caused Directory Server to
crash.
4976819 If there was a link failure on the network for more than 5 minutes then the consumer did not
recover its state when the network returned to normal, which resulted in the replicas not being
synchronized.
4976981 Using the retro change log trimming functionality, sometimes resulted in server crash.