Sun Java(TM) System Directory Server 5 2004Q2 Release Notes

Sun Java™ System Directory Server Release Notes

Version 5.2 2004Q2

Part Number 817-5216

These Release Notes contain important information available at the time of release of Sun JavaSystem Directory Server 5 2004Q2. New features and enhancements, known issues and limitations, and other information are addressed here. Read this document before you begin using Directory Server 5 2004Q2.

The most up-to-date version of these release notes can be found at: Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and manuals.

These release notes contain the following sections:

Third-party URLs are referenced in this document and provide additional, related information.


Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

Release Notes Revision History

Table 1  Revision History


Description of Changes

May, 2004

About Sun Java System Directory Server 5 2004Q2

In some parts of the documentation and on Directory Server Console, the version number of the product is referred to as 5.2. Directory Server 5 2004Q2 is a maintenance release of Directory Server 5.2.

Sun Java System Directory Server 5 2004Q2 is a powerful and scalable distributed directory server based on the industry-standard Lightweight Directory Access Protocol (LDAP). Directory Server is part of the Sun Java Enterprise System enterprise infrastructure software system that delivers an integrated, core set of industry-leading enterprise network services that virtually all businesses need today.

This section includes:

What’s New in This Release

For information regarding both the standalone Directory Server 5.2 release and the 5.2 release packaged with the 2003Q4 release of Sun JavaTM Enterprise System see the Sun ONE Directory Server 5.2 Release Notes.

Due to architectural changes made in Directory Server 5.2, some features that were available in Directory Server 4.x are no longer included. These are:

Software Requirements

The following software is required for this release of Directory Server.


Before installing Directory Server on Solaris 8 Ultra SPARC and Solaris 9 Ultra SPARC, you must ensure that the required OS patches have been installed. These patches can be obtained in the form or a patch cluster or as individual patches from The required OS patch cluster includes an installation script that installs the patches in the correct order. The clusters are updated periodically as new patch revisions are released. Select the “Patches” link on the SunSolve site and follow the links to obtain the required OS patch clusters.

Table 2  Solaris SPARC Software Requirements 


Platform Requirement

Operating System

Solaris 8 Ultra SPARC Platform Edition with patches required for Java Enterprise System (Sun Cluster 3.1 Release 04/04 has been qualified to run on Solaris 8 02/02 (with the recommended patches installed) and Solaris 8 HW 05/03 (PSR 2))

Solaris 9 Ultra SPARC Platform Edition with patches required for Java Enterprise System (Sun Cluster 3.1 Release 04/04 has been qualified to run on Solaris 9 04/04)


256 Mbytes for evaluation purposes and 1 Gbyte as a recommended minimum

Disk space

3 Gbytes recommended

Note that:

- this figure is based on a sample production deployment with between 10 000 and 250 000 entries

- DS binaries and default logs account for 1.2 Gbytes per Directory Server instance

- for an evaluation (i.e. minimum data stored in the directory) 1.4 Gbytes should suffice

Table 3  Solaris x86 Software Requirements 


Platform Requirement

Operating System

Solaris 9 x86 Platform Edition (Sun Cluster 3.1 Release 04/04 has been qualified to run on Solaris 9 04/04 x86 Platform Edition)


256 Mbytes for evaluation purposes and 1 Gbyte as a recommended minimum

Disk space

3 Gbytes recommended

Note that:

- this figure is based on a sample production deployment with between 10, 000 and 250, 000 entries

- DS binaries and default logs account for 1.2 Gbytes per Directory Server instance

- for an evaluation (i.e. minimum data stored in the directory) 1.4 Gbytes should suffice

Table 4  Linux Software Requirements 


Platform Requirement

Operating System

RedHat Advanced Server 2.1 Update 2

Patches or service packs


Additional software



Sun Java System Directory Server 5.2 has been validated with Sun Cluster 3.1.

Specific operating system patches may need to be installed before Directory Server 5.2 can be installed. For further information, refer to the Directory Server Installation and Tuning Guide issued with the initial release of Directory Server 5.2. You can obtain Solaris patches from

Bugs Fixed in This Release

The tables below describe the bugs fixed in Directory Server 5.2 in the following areas:

Important Information

This section contains the latest information that is not contained in the core product documentation. This section covers the following topics:

Installation Notes

This topic contains important patch requirement and general installation information, and is divided into the following subsections:

Patch Requirement Information

If you have Directory Server 5.2 installed from Solaris packages and wish to bring it in line with Directory Server as delivered in Java Enterprise System 2004Q2, install the following patches with at least the given version number or more, available at


To avoid breaking product dependencies, it is mandatory to install the patches in the order provided in the following tables.

Table 15  Directory Server 5.2 Java Enterprise System 2004Q2 Alignment Patches Required For Solaris 8 (SPARC)

Patch Number

Patch Description


SunOS 5.8: International Components for Unicode Patch


SunOS 5.8: Netscape Portable Runtime(4.1.4)/Network Security System(3.3.4)


SunOS 5.8: NSPR4.1.6 / NSS 3.3.6 / JSS


SunOS 5.8: Simple Authentication and Security Layer (2.01)


SunOS 5.9_sparc: Sun ONE AdminServer 5.2 patch

Note that this patch is also valid for Solaris 8


SunOS 5.9 : Sun ONE Directory Server 5.2 patch

Note that this patch is also valid for Solaris 8

Table 16  Directory Server 5.2 Java Enterprise System 2004Q2 Alignment Patches Required For Solaris 9 (SPARC)

Patch Number

Patch Description


SunOS 5.9: International Components for Unicode Patch


SunOS 5.9: Netscape Portable Runtime(4.1.4)/Network Security System(3.3.4)


SunOS 5.9: NSPR4.1.6 / NSS 3.3.6 / JSS


SunOS 5.9: Simple Authentication and Security Layer (2.01)


SunOS 5.9_sparc: Sun ONE AdminServer 5.2 patch


SunOS 5.9 : Sun ONE Directory Server 5.2 patch

Table 17  Directory Server 5.2 Java Enterprise System 2004Q2 Alignment Patches Required For Solaris 9 (x86)

Patch Number

Patch Description


SunOS 5.9_x86: International Components for Unicode Patch


SunOS 5.9_x86: Netscape Portable Runtime(4.1.4)/Network Security System(3.3.4)


SunOS 5.9_x86: NSPR4.1.6 / NSS 3.3.6 / JSS


SunOS 5.9_x86 : Sun ONE AdminServer 5.2 patch


SunOS 5.9_x86: Sun ONE Directory Server 5.2 patch

For more information on the Sun Java Enterprise System, see

General Installation Information

Compatibility Notes

Documentation Notes

Known Issues and Limitations

This section contains a list of the known problems and issues with Directory Server 5.2. The following product areas are covered:

Installation, Uninstallation, and Migration

Multibyte characters at installation cause configuration problems (#4882927)

At installation, using multibyte characters for anything other than the suffix name causes Directory Server and Administration Server configuration to fail.

Use monobyte characters for all fields other than the suffix name.

Multibyte characters cannot be used in the suffix name during installation of the traditional Chinese (zh_TW) version (#4882801)

If multibyte characters are entered as the suffix name during installation of the traditional Chinese (zh_TW) version, the suffix name does not display correctly in the console. This issue is restricted to 32-bit and 64-bit installations from Solaris packages on SPARC processors.


  1. Create a monobyte suffix at installation. Once installation is complete, create the desired multibyte suffix using the console.
  2. Upgrade your JRE to version 1.4.1 or later.

Harmless error message occurs on installation (#4820566)

After a successful installation, the following error is logged:

ERROR<5398> - Entry - conn=-1 op=-1 msgId=-1 - Duplicate value addition in attribute "aci"

This error is harmless and can be ignored.

A root suffix cannot contain spaces (#4526501)

If your root suffix contains space characters, correct the suffix generated at installation time to remove the spaces:

  1. In the Sun Java System Server console, select the top directory entry in the left-hand navigation pane of the Servers and Applications tab.
  2. Click Edit and modify the suffix in the User directory subtree field.
  3. Click OK to save the change.

Error message with migrateInstance5 (#4529552)

When running the migrateInstance5 script with error logging disabled, a message is displayed indicating that the migration procedure is attempting to restart the server while the server is already running.

If error logging is disabled, you can ignore this error message.

If this message appears when error logging is enabled, consult the error log for more information.

User enters into a loop if an incorrect password is entered during command-line installation (#4885580)

When prompted for the password again, type “<“ to return to the previous input item, and then press return to keep the previous choice. When the password is requested again, enter the correct password.

Running the pkgrm command does not remove all the Directory Server distribution packages (#4911028)

Installation failure occurs if the administration domain of the remote directory being used to configure Directory Server does not exactly match the administration domain in the setup procedure. (#4931503)

During installation use the exact same administration domain as defined in the remote configuration directory.

The startconsole command may fail to start certain servers if the user running the command does not have write access to the ServerRoot directory (#5008600)

To access certain servers Server Console may have to download JAR files into the ServerRoot directory. If the user running the startconsole command does not have write access to the ServerRoot directory, the console will refuse to open the servers in question.

Either run the startconsole command as the user who owns the ServerRoot directory or install and configure the server packages on the host running Server Console.

Only use the restart-admin command on the active node in a cluster-enabled environment (#4862968)

Cannot remove patch ID 115614-08 (Directory Server patch) from all nodes on a cluster (#5035139)

The patchrm command for patch ID 115614-08 on a cluster will only work correctly when removing the patch from the first node. On attempting to remove the patch from the second and subsequent nodes, the following error message is displayed:

The backout of data cannot occur because the sync-directory binary is missing. Please contact your Sun support

Once you have successfully removed the patch from the first node in your cluster, and if you have received the above error message, create a symbolic link in ServerRoot/shared/bin to point to the sync-directory binary as follows:
ln -s /usr/ds/v5.2/sbin/sync-directory ServerRoot/shared/bin

Then reapply the procedure to remove the patch.

Directory Server installation is partial and will not remove all installed files (#4845960)

The slapd process does not restart after adding patch ID 115614-10 on a cluster enabled environment (#5042440)


  1. Stop the slapd process and the Administration Server prior to applying patches on cluster
  2. Patch all nodes in the cluster irrespective of whether ns-slapd fails to start or not
  3. When all nodes are patched start the slapd process
  4. Run the directoryserver sync-cds command for the Administration Server and slapd

When migrating from 4.x to 5.x some plug-ins may not be migrated (#4942616)

Edit the 4.x slapd.ldbm.conf configuration file and insert quotation marks around the plug-in path for the plug-in to be migrated. For example the plug-in post-operation on referential integrity post-operation which appears as /mydirectory/ds416/lib/<.....> needs to be edited to “/mydirectory/ds416/lib/”<.....>

Cannot restart the Administration Server from the Console on a Solaris 9 x86 in a cluster enabled environment (#4974780)

During an initial installation of Directory Server, if a base DN value contains a blank space, for example o=example east, the directoryURL entry will be incorrectly parsed for the user directory global preferences. As a result entries will not be found in the Users and Groups tab of Server Console (#5040621)

Modify the base DN value either by correcting the nsDirectoryURL attribute in the console to reflect the correct base DN or by performing an ldapmodify on the nsDirectoryURL attribute and an ldapdelete on the nsDirectoryFailoverList attribute via the command line.

When migrating from a 5.1 Directory Server to a 2004Q2 Directory Server any modifications you made to the set of default indexes will not be migrated (#5037580)

The SUNWasha and SUNWsdha files should not be relocated (#5035882)

Duplicate value error is logged in the Configuration Directory Server when ACI is added to the server group entry during a new server installation (#4841576)

During Directory Server configuration an ACI on the server group entry for each new server installation is added. If the entry already exists and this ACI value already exists on the entry (which is the case when Administration Server is installed after Directory Server), then the following benign duplicate value error is logged in the Configuration Directory Server:

[07/May/2004:16:52:29 +0200] - ERROR<5398> - Entry - conn=-1 op=-1msgId=-1 - Duplicate value addition in attribute "aci" of entry "cn=Server Groups,,,o=NetscapeRoot"


DNS keyword in ACIs (#4725671)

If the DNS keyword is used in an ACI, any DNS administrator can access the directory by modifying a PTR record, and can thereby provide the privileges granted by the ACI.

Use the IP keyword in the ACI, to include all IP addresses in the domain.

Incorrect error message in error logs, when passwordisglobalpolicy attribute is enabled (#4964523)

When the passwordisglobalpolicy attribute is enabled on both masters in a 2-master multi-master replication topology it works correctly but may generate the following incorrect error message:

Ignore the incorrect error message.

ldapmodify update operations over SSL that are referred to a master replica from a consumer replica do not succeed (#4922620)

Invalid value accepted for passwordMinLength attribute when configuring an individual password policy (#4969034)

Using the attribute encryption functionality may result in generating duplicate values for the UID attribute (#4997578)

The insync replication monitoring tool prints the password on UNIX when “-” is entered for the -w option (#4902013)

Account lockout after password change (#4527623)

Account lockout remains in effect after a user password has been changed. If users forget their passwords and are locked out of the directory, the rootDN or entry entitled to change the user password can reset the account lock.


Additional documentation required on using referential integrity plug-in with legacy replication (#4956596)

When replicating from a 4.x master to a 5.x consumer, with referential integrity enabled, you must reconfigure the referential integrity plug-in on the 4.x master to write referential integrity changes to the 4.x change log. This enables referential integrity changes to be replicated. If you do not reconfigure the plug-in, referential integrity will not work correctly.

To reconfigure the referential integrity plug-in in this environment:

  1. Stop the 4.x server.
  2. Open the slapd.ldbm.conf file located in ServerRoot/slapd-ServerID/config/.
  3. Locate the line that begins:
  1. Modify this line by changing the argument that appears just before the list of attributes from 0 to 1.
  2. For example, change:

  1. Save the slapd.ldbm.conf file.
  2. Restart the server.
  3. Reinitialize the 5.x consumer from the 4.x supplier.

The insync command-line tool has no concept of partial replication (#4856286)

The insync command-line tool has no concept of fractional replication which may result in the reported delays being inaccurate if fractional replication is configured.

Multi-master replication over SSL (#4727672)

In a multi-master replication scenario, if replication is enabled over SSL using simple authentication, it is not possible to enable replication between the same servers over SSL using certificate-based client authentication.

To enable replication over SSL using certificate-based client authentication, restart at least one of the servers.

Aborting a total update (#4741320)

If a total update is aborted while in progress, it is not possible to launch another total update, or to re-enable replication on the suffix.

Do not abort a total update while it is in progress.

Replication monitoring tools and literal IPv6 addresses (#4702476)

The replication monitoring tools (entrycmp, insync and repldisc) do not support LDAP URLs containing literal IPv6 addresses.

Local schema modifications may be overwritten when a consumer database is created (#4537230)


The replication monitoring tools rely on read access to cn=config to obtain the replication status. This should be taken into account particularly when replication is configured over SSL.


In Directory Server 5.2, the schema file 11rfc2307.ldif has been altered to conform to rfc2307. If replication is enabled between 5.2 servers and 5.1 servers, the rfc2307 schema MUST be corrected on the 5.1 servers, or replication will not work correctly. To ensure correct replication between a 5.2 server and a 5.1 server:

Initially, certain schema attributes may be replicated between the servers as they synchronize other schema elements but this is benign and will not cause any problems. See the Installation Notes for details on how the schema has changed.

Schema modifications are not replicated immediately if there are no non-schema modifications to replicate (#4868960)

If you modify the schema and do not make any other non-schema related modifications, your schema modifications will not be replicated immediately.

Either wait 5 minutes for your schema modifications to be replicated or use the Send Updates Now option in Directory Service Console to force replication.

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.

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)

Avoid adding entries with objectClass=nstombstone

Using the scheduled replication functionality may result in erratic replication behavior (#4999132)

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.


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.

Previously the LDAPv2 protocol specified that the attribute should be xxxxx (where xxxxx is one of: UserCertificate, CACertificate, CertificateRevocationList, AuthorityRevocationList, or CrossCertificatePair.) whereas the LDAPv3 protocol specifies that the attribute should be xxxxx;binary. Directory Server considered the values associated with xxxxx;binary and xxxxx as two different values. In practice, this was not always what was required.

The new configuration attribute nsslapd-binary-mode has been created to change this behavior and can have one of the following three values:

compat51 is the default value and provides the original behavior. xxxxx and xxxxx;binary refer to distinct values (where xxxxx is one of: UserCertificate, CACertificate, CertificateRevocationList, AuthorityRevocationList, or CrossCertificatePair.)

auto implies that the server considers xxxxx and xxxxx;binary as the same attribute. Searches return either the attribute specifically requested or xxxxx in LDAPv2 and xxxxx;binary in LDAPv3.

strict is the same as auto except that requests that do not conform are rejected with an INVALID PROTOCOL error (reject ;binary subtype in an LDAPv2 request or without subtype in an LDAPv3 request.)

DN normalization puts everything in lower case, by not taking attribute syntax and the associated matching rule into account, thus restricting user entry possibilities (#4933500)

When the nsslapd-rewrite-rfc1274 attribute is turned on, the translation of userCertificate;binary and caCertificate;binary attributes is done from LDAP v2 to LDAP v3 instead of from v3 to v2 (#4861499)

Directory Server Console

The console does not support passwords containing a colon (#4535932)

The console does not support passwords containing a colon (:).

Do not use colons in passwords.

The console and external security devices (#4795512)

The console does not support the management of external security devices, such as Sun Crypto Accelerator 1000 Board.

External security devices must be managed via the command line.

Trailing spaces are not preserved during a remote console import operation (#4529532)

Trailing spaces are preserved during both local console and ldif2db import operations.

Incorrect sorting of German entries in Directory Server Console (#4889951)

In certain search contexts internal search mechanisms cause Directory Server Console to display a yellow warning flag (#4983539)

In certain search contexts a yellow warning flag may be displayed, indicating that Directory Server internal search mechanisms have encountered an All IDs Threshold / Sorting issue. This flag does not highlight a user issue and should not, therefore, be cause for concern.


We recommend creating a browsing index (VLV index) to prevent this situation from occurring.

Referral information is not displayed correctly in the Directory Server Console (#4969992)

When certain multi-byte characters are entered into the text field of the Directory Server’s Online Help Search Index, additional characters are prepended and an ArrayOutofBounds exception error is displayed. (#5025653)

Although this error does not cause the online help system to crash, users may prefer to use the online help contents list as an alternative search method.

On a Directory Server cluster node (active or not) Browse buttons in the Directory Server console are grayed out (#5044629)

Ensure you are running the console on the active cluster node, and use the node name (as opposed to the logical host name) to connect to the Administration Server.

Copyright information in Online Help contains different years for different languages (#5046691)

In the French Online Help the copyright is 2002 and 2003, in the English, German, and Spanish Online Help 2003 and 2004. This issue may also apply to other languages.

French and German Online Help content sometimes displays html tags instead of rendered characters (#5046714)

Missing symbolic links for Online Help in EMEA languages other than English (#5045854)

When you try to open the help content in Spanish, French, or German via the Directory Server Console menu it opens in English. If you try to open the Online Help Index via the Directory Server Console menu, it displays an empty window and the terminal window issues a 404 Not Found error. The Help buttons in certain Directory Server Console windows also sometimes fail to display help content in Spanish, French, or German. These problems are caused by the fact that the help directories do not contain symbolic links to the slapd directory.

Create the missing symbolic link using the ln command as follows:

ln -s /usr/sadm/mps/admin/v5.2/manual/lang/slapd /var/opt/mps/serverroot/manual/lang/slapd

Error when loading Online Help in the Directory Server Login dialog box in non-English locales (#5046970)

The path to the help .htm file for the Directory Server Login dialog box in non-English locales, for example in Korean, is incorrect: manual/ko/console/help/help/login.htm

Apply the following workaround which takes the Korean locale as an example:

  1. Close Directory Server Console
  2. Change directory to the /usr/sadm/mps/console/v5.2/java directory
  3. Extract the mcc52_ko.jar file using for the jar xvf mcc52_ko.jar command
  4. Remove the mcc52_ko.jar file
  5. Open a text editor and edit the com/netscape/management/client/console/ file by changing the login-help=manual/ko/console/help/help/login.htm path to
  6. Recreate the following mcc52_ko.jar META-INF/* com/* jar file using the
    jar cvf mcc52_ko.jar META-INF/* com/* command
  7. Restart Directory Server Console

Core Server

Stopping the server during export, backup, restore, or index creation may cause it to crash (#4678334)

Database becomes unavailable if the LDIF file is inaccessible during import (#4884530)

If a non-existent file is specified for an online import, the server still deletes the existing database.

Chained suffixes return mixed case DNs in lower case (#4917152)

A mixed case DN retrieved using getDN will be returned exactly as originally specified. If the DN is retrieved using a chaining suffix, the DN will be returned all lower case.

When exporting a subtree using the db2ldif -s option, an error message may be generated despite the operation having been successful (#4925250)

When using the -s option of the db2ldif script to export a subtree, the following incorrect error message may be generated and can therefore be discounted:

Incorrect error message if the transaction log directory is missing (#4938877)

If you try to start Directory Server with a custom transaction log directory and that directory either does not exist or is not writable, then the server will not be able to start. The error log indicates erroneously that the database home directory is the cause.

Backend instances (databases) called “Default” will not function (#4966365)

Do not name your database “Default” as it will not function correctly. Should you need to rename your database you can do so by selecting the Options button in the New Suffix panel and then enter your database name in the Use custom text field of the Database Information section.

Installing 64-bit packages locks out the 32-bit Directory Server databases (#4786900)

Running db2ldif with the -r option results in a disorderly shutdown of the database (#4869781)

Deleting an attribute subtype value deletes all attribute values (#4914303)

If you create an entry with an attribute which has, for example, 3 values, one of which has a subtype tag on it, and you then delete the attribute with the subtype tag, every value of that attribute is deleted.

Searches based on a substring filter for the telephonenumber attribute fail if the filter contains a blank space directly after the ‘*’ substring (#4866642)

db2ldif produces unexpected errors when sub-suffixes are given in the -s option (#4889077)

When indexes are configured with nsMatchingRule, db2ldif and ldif2db issue an “unknown index rule” warning which means that the index created does not include the matching rule (#4995127)

Use and instead of db2ldif and ldif2db as they do not issue “unknown index rule” warnings and create the index with the matching rule.

Unless an output file is defined as an absolute path, the db2ldif command (and the db2ldif option of the directoryserver command) creates the output file under /installdir/bin/slapd/server/sparcv9 as opposed to under /ServerRoot/slapd-serverID as stated in the Directory Server Administration Guide (#5029598)

Directory Server Plug-ins

If two entries with duplicate uids are added to Directory Server simultaneously, then UID uniqueness is not enforced (#4987124)

If the plug-in configuration entry attribute values in the dse.ldif end with extra blank spaces, Directory Server will either fail to start or behave in unexpected ways (#4986088)

When the Pass-Through Authentication plug-in (PTA plug-in) detects that a suffix configured for pass-through authentication is local to the machine, the plug-in is not automatically disabled (#4938821)

If you have two Directory Server instances DS1 and DS2 with your Configuration Directory Server installed on DS1, and you subsequently replicate the o=NetscapeRoot configuration information to DS2, as opposed to automatically disabling the PTA plug-in will continue to point to DS1for any o=NetscapeRoot relevant searches despite the fact that the information is now local.

When running a search on a non-existent base DN, the post-operation plug-in function is not called (#5032637)

Product documentation states that post-operation plug-ins are called after a client request has been processed whether or not the operation completes successfully. However when performing a search on an non-existent base DN, this does not happen.


Statistics for SNMP subagents (#4529542)

On UNIX platforms, statistics are generated only for the last SNMP subagent that is started. This implies that you can monitor only one Directory Server instance at a time with SNMP.

Changing the maximum size of the transaction log file has no effect if log files already exist in the database directory (#4523783)

Stop the server, modify the nsslapd-db-logfile-size attribute in the dse.ldif configuration file manually, remove all log.* files from the database directory, and restart the server.

ldapsearch on Linux systems (#4755958)

On Linux systems, an ldapsearch operation without a host name, such as

ldapsearch -D ... -w ... -h -p 389

returns an error 91 (ldap_simple_bind: Can't connect to the LDAP server - No route to host). On other platforms, an error 89 (LDAP_PARAM_ERROR) is returned. This is because on Linux systems, it is possible to resolve a host such as "-p", so the connect function attempts to do so, and fails.

International substring search on unaccented characters returns only unaccented characters (#4955638)

Instead of returning the unaccented character and all of its possible accented variants, which would seem to be the logical approach, a search on an unaccented character only returns the unaccented character in question. Searching for an accented character however, returns not only that character but all other variants.

SSL does not start for a Directory Server with the instance name “test-cert” (#4971699)

Avoid naming your Directory Server instance “test-cert”.

Modifying the port or secure port number of your user directory server does not make the necessary port number changes to certain scripts and requires that these scripts be modified manually. (#5029807)

If you modify the port or secure port number of your user directory server, the following scripts remain hard-coded to the original port number:,,, check-slapd,,, monitor,,, ldif2ldap,,

If you want to use these scripts after a port modification you will need to edit them manually. Note that the script names given here are the standalone tool names and that the check-slapd command is not documented as it is not part of the publicly exposed API. For more information see Chapter 1 “Command-Line Tools Reference” of the Directory Server Administration Reference.

Audit, Access and Error Logs are all limited to 2 Gbytes each (#4976129)

Directory Server hangs when performing both a VLV browsing index update during add operations and a VLV search operation (#4973380)

When creating a new chained suffix with an IPv6 address using the New Chained Suffix window of the console a “Testing connection parameters” popup window does not close automatically. However, although the local configuration of the chained suffix succeeds, the validity check of the IPv6 address is not performed which may lead to problems in the event of anything being incorrect (#5019414)

Certain error messages reference a database error guide which does not exist (#4979319)

With Directory Server and Administration Server installed and configured to run as root, when the console is used to create another instance of Directory Server which you specify to run as a user other than root, that instance is successfully created but many of the files pertaining to that instance are not owned by the same user (#4995286)

Change the ownership of the files and directories manually.

The directoryserver monitor command-line tool does not work on non-active nodes in a cluster enabled environment (#5005446)

When the ldapsearch sizelimit option is hit on a chained suffix an error message is issued and the access number of entries count is incorrect (#5029026)

Redistributable Files

Sun Java System Directory Server 5.2 2004Q2 does not contain any files which you can redistribute.

How to Report Problems and Provide Feedback

If you have problems with Sun Java System Directory Server, contact Sun customer support using one of the following mechanisms:

So that we can best assist you in resolving problems, please have the following information available when you contact support:

You might also find it useful to subscribe to the following interest groups, where Sun Java System Directory Server topics are discussed:

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions. Use the web-based form to provide feedback to Sun:

Please provide the full document title and part number in the appropriate fields. The part number can be found on the title page of the book or at the top of the document, and is usually a seven or nine digit number. For example, the part number of these Directory Server 5.2 Release Notes is 817-5216.

Additional Sun Resources

Useful Sun Java System information can be found at the following Internet locations:

Copyright � 2004 Sun Microsystems, Inc. All rights reserved.

Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at and one or more additional patents or pending patent applications in the U.S. and in other countries.


U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

Use is subject to license terms.

This distribution may include materials developed by third parties.

Portions may be derived from Berkeley BSD systems, licensed from U. of CA.

Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.

Copyright � 2004 Sun Microsystems, Inc. Tous droits r�serv�s.

Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plus des brevets am�ricains list�s � l'adresse et un ou les brevets suppl�mentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.


L'utilisation est soumise aux termes du contrat de licence.

Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.

Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.

Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.

Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.