This section lists the bugs fixed since the last release of Directory Server.
Importing large ldif files using db2ldif results in corrupted index files. Database corruption is seen as zeroed pages within the Sleepycat database files.
This bug fix prevents new corruptions, but does not prevent corruptions that have already occurred. If you find corrupted index files, upgrade to the latest version of Directory Server and reinitialize your database to take advantage of this bug fix and to prevent future corruptions.
The output of dpconf help-properties is not localized.
The dsconf command in Directory Server allows you to set the repl-accept-client-update-enabled property to 'off'. If you use the dsconf command to configure an instance of Directory Server 6.0, the 'off' value is rejected and a message asks you to upgrade your version of Directory Server.
Idle connections are not closed until there is some network activity.
The idle timeout is now always correctly computed.
The Directory Server dumps core when the amadmin command (for Access Manager 6.3 with 119465-11 and 119466-11) is run to update the directory.
In a search operation where ACIs have userattr and userdn with common target attributes, crashes can occur.
In an internal search isMemberOf search, a comma included in the DN name is not masked.
A deadlock occurs when a changelog trimming operation removes several records with different IDs.
The Directory Server Retro Change Log may generate records with invalid changes.
The ns-slapd process produces a memory leak when acting on consumers during various operations such as SSL replication agreements.
The dsmig command fails to migrate nested suffixes.
Memory leak on a master with the retrochangelog enabled.
Replication metadata growth unacceptable over time.
Crash with dn cache/hashtable and dn normalization.
Memory leak when performing substring searches.
Error when you force a log rotation.
The CoS Fastlookup implementation can enter into an infinite loop when processing multiple specifiers.
The Directory Server crashes when a filter with 1006 filter elements is played.
The dsconf command does not properly handle suffix with escaped characters.
Wizard hangs when trying to create an instance using the zip web console on SuSE.
The Directory Server crashes while initializing a replication management agreement if there is a missing replica object in the configuration file.
On SuSE 64–bit installations, the dsadm create command fails.
On Solaris, the instances registered as a service might not start after restarting the system.
On Linux, the Directory Server instances do not start at system restart if the maximum number of files are specified in the /etc/security/limits.conf file.
If you apply the Directory Server Enterprise Edition 6.3 patch without stopping the server instances, the dsadm info and dsadm stop will display that a server is down while the server is running.
If you configure the uniqueness plug-in to work across multiple attributes in Directory Server, an error is displayed during the Directory Server startup.
Directory Server Enterprise Edition Windows service fails to start more than one server instances when the system restarts.
After creating or adding a new certificate, Directory Server must be restarted for the change to take effect.
Directory Service Control Center fails to generate a self-signed certificate when you specify the country.
create-repl-agmt fails if an IPv6 address is specified as repl-dest HOST.
This bug has been fixed, and you can now declare an IPv6 address. You can optionally use square brackets, []. Note that if you choose to use square brackets to declare the IPv6 address, add a backslash before each square bracket. Thus the following two commands are equivalent:
dsconf create-repl-agmt -p 5566 dc=com 1234:123d:aeff:9dc9:222:4fff:fe3a:5bb2:5389 |
dsconf create-repl-agmt -p 5566 dc=com \[1234:123d:aeff:9dc9:222:4fff:fe3a:5bb2\]:5389 |