Sun Java System Directory Server Release Notes for Microsoft Windows

Sun Java™ System Directory Server Release Notes for Microsoft Windows

Version 5.2 2005Q4

Part Number 819-4267-10

These Release Notes contain important information available at the time of release of Sun Java System Directory Server 5.2 2005Q4 for Windows. Known issues and limitations, and other information are addressed here. Read this document before you begin using Directory Server 5.2.

The most up-to-date version of these release notes can be found at the Sun Java System documentation web site: Check the web site prior to installing and setting up your software. Then check the web site periodically thereafter to view the most up-to-date release notes and product documentation.

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

February 2006

Revenue release.

November 2005

Beta release.

About Directory Server 5.2 2005Q4

Directory Server 5.2 2005Q4 is part of the Sun Java Enterprise 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 Directory Server 5.2 2005Q4

Directory Server 5.2 2005Q4 is a maintenance release of Directory Server 5.2 2004Q2. No new features have been introduced in Directory Server 5.2 2005Q4:

For information about the bugs fixed in Directory Server 5.2 2005Q4, see Bugs Fixed in This Release.

The following feature was available in Directory Server 4.x but is not available in Directory Server 5.2:

Database Backend Plug-in Interface. The enhanced pre-operation interfaces may be used instead of the database backend plug-in interface, to implement plug-ins that are designed to provide access to alternative directory data stores.

Hardware and Software Requirements

The following software is required for Directory Server 5.2 2005Q4.

Table 2  Windows Hardware and Software Requirements 


Platform Requirement

Operating System

Windows 2000 Advanced Server, Service Pack4
Windows Server 2003 Enterprise Edition
Windows XP Professional, Service Pack 2


512 Mbytes

Disk Space

50 Mbytes


Directory Server 5.2 has been validated with Windows 2000, 2003, XP.

Bugs Fixed in This Release

Table 3  Fixed Bugs in Directory Server 5.2 2005Q4

Bug Number

Bug Synopsis


allow “Administrators” to reset the password


Account validation via LDAP bind without user password


DS 5.2. db2ldif -r removes the guardian file


Deletion operation is not flagged as dependent of a previous modification


MMR+SSL: Can’t stop or use master after total update that failed


Add the rc code inside the could not be logged in the Changelog error


Hub not replicating due to Wrong ReplicaId 65535 in the Hub RUV


lack of out of disk space causes looping in db2bak internal TASK


Huge memory leak on mixed 5.1/5.2 topology (5.1 protocol)


DS 5.2patch2/aci returns incorrect results when fix for 4886766 is applied


fix 4974942 (in 5.2patch2) is wrong and can lead to a race condition when closing the connections


Memory leak in search "cn=config"


Memory leak in each replication session coming from a hub


Online indexation task request + search (evaluating role aci) -> DS deadlock hang


bad server side sorting performances when data contains a lot of identical values


ns-slapd Memory leak when dn_normalization failed


Index corruption


passwordRetryCount does not get incremented when passwordResetFailureCount is set to 0


performance degradation in sub string searches using P2


DS5.2: Memory leak in Individual Password Policies


performance problems when doing searches with the en-US collation rule


Random crash with DSML pdu larger than 2K


memory leak with virtual attributes


add/delete of an attribute in one ldapmodify is not replicated correctly


multivalued substring index of DN syntax gets corrupted if value deleted


fildif is not able to work with files larger than 2GB (CU LDIF export file in this case is 28GB)


Retro Changelog plugin fails to record changes if "regular" replication is disabled


Deleting multivalued attribute(s) in directory server 5.2 patch2 results in high etimes


Directory server crashes while processing ldapmodify with Retro Changelog plugin turned on


DS exits when acllas__handle_group_entry()tries to allocate 4GB


Directory Server hangs when running stop-slapd command

6252452 -r may hangs the server


duplicate nsunique ids can be generated


COS doesn’t get effective for sub-sub-org. cos attributes are empty for a user in sub-sub-org


DS 5.2 P2 forces a checkpoint at the specified checkpoint interval even when no mods performed


On UNIX, Directory Server may crash if #fd resource limit is dynamically increased


Error during the creation of subsuffix or clone under a search workload


Searches for subtype attributes does not work correctly with nsslapd-search-tune enabled


Deadlock in database while evaluating the acls in a modify operation


DS 5.2p3: crash in is_pending_value_mods because of uid uniqness plugin


Replication may be slow to restart after a network outage


Restart of a Fractional Consumer breaks replication with WARNING<10271> - Partial Config Error


DS5.2 Patch3 Core Dumps within ids_sasl_check_bind due to NPE


A consumer does not detect there is pending operation and when closing an ’idle’ replication cnx


DS5.2p3: modification lost when using ldapmodify


ds5ReplicaConsumerTimeout cannot be configured


Directory Server can hang if replication agreement is being initialized from another master


Performance issue when deleting non existent attribute


Remove time bomb in ns-slapd

Important Information

This section covers the following topics:

Installation Notes

For information about patch requirements and installation, see the following sections:

Patch Requirement Information

The following table gives the numbers and minimum versions for the alignment patches. All patches referred to in this section are the minimum version number required for upgrade. It is possible that a new version of the patch has been issued since this document was published. A newer version is indicated by a different version number at the end of the patch. For example: 123456-04 is a newer version of 123456-02 but they are the same patch ID. Refer to the README file for each patch listed for special instructions.

To access the patches, go to

Table 4  Directory Server 5.2 2005Q4 Alignment Patches Required For Windows

Patch Number

Patch Description


Windows (MSI): Sun Java™ System Administration Server 5 2005Q4


Windows (MSI): Sun Java™ System Directory Server 5 2005Q4

For detailed information about Upgrade procedure of the Directory Server from JES3 to JES4 refer Sun Java Enterprise System 2005Q4 Upgrade Guide for Microsoft Windows located at

General Installation Information

Documentation Notes

Man Pages

Directory Server commands and Administration Server commands are now documented as man pages and delivered in the following formats:

For information about how to access the man pages, see the Java Enterprise System Installation Guide.

Product Version Number

In some parts of the Directory Server documentation and console, the version number of the product is referred to as 5.2. Directory Server 5 2005Q4 is a maintenance release of Directory Server 5.2.

Localized Documentation

Localized documentation is posted to as it becomes available.

Accessibility Features for People With Disabilities

To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at:

For information on Sun's commitment to accessibility, visit

Known Issues and Limitations

This section contains a list of the known issues and limitations with Directory Server 5.2 2005Q4. The issues are grouped into the following categories:

Installation, Uninstallation, and Migration

Cannot Install Directory Server When the Root Suffix Contains Spaces (4526501)

A root suffix cannot contain space characters.


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 When Running migrateInstance5 Script (4529552)

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


Duplicate Value Error Logged in the Configuration Directory Server During Installation (4841576)

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


Ignore the error message.

Configuration of Directory Server Fails When Using a Remote Configuration Directory (4931503)

When configuring Directory Server by using a remote configuration directory, configuration fails if the administration domain of the remote directory does not match the administration domain in the setup procedure.


When configuring Directory Server by using a remote configuration directory, use the same administration domain as defined in the remote configuration directory.

Installation Fails When the Base DN Contains a White Space (5040621)

During installation, if the base DN contains a white space (for example, o=example east) the directoryURL entry is incorrectly parsed for the UserDirectory global preferences. Consequently, all operations to the userDirectory fail to find the entries in user/groups in the console.


Modify the base DN value in one of the following ways:

nsSchemaCSN Has Multiple Values After upgrade of AS and DS (5041885)

After upgrade of Administration Server or Directory Server, the nsSchemaCSN attribute has several values. This issue occurs because the 60iplanet-calendar.ldif file and the 99user.ldif file both contain the nsSchemaCSN attribute. The nsSchemaCSN attribute should be in the 99user.ldif file only.


  1. Remove the nsSchemaCSN attribute from 99user.ldif file and the 60iplanet-calendar.ldif file.
  2. Rename the script from
  3. <server_root>\slapd-<instance>\



  4. Copy the template file from
  5. <server_root>\bin\slapd\admin\scripts\



  6. Edit the new file as follows:
    1. Replace {{PERL-EXEC}} by !<server_root>\bin\slapd\admin\bin\perl
    2. Replace {{MY-DS-ROOT}} by <server_root>\slapd-<instance>
    3. Replace {{SEP}} by "\"
  7. Add the execute mode to the file.
  8. Force the schema replication by running the script, as follows:
  9. <server_root>\

  10. Confirm that the nsSchemaCSN attribute has been added to 99user.ldif file.

To backout, restore the original file under <slapd-instance>.

Backout Fails When the Previous Version Is Not Configured (6196574)

Backout fails in the following scenario:

The backout fails because the <ServerRoot>\admin-serv\upgrade\versions.conf file does not contain the correct information.


Configure the previous version of Directory Server and Administration Server before installing the latest version of Directory Server and Administration Server.

Upgrade of a Standalone Instance of Directory Server Requires the sync-cds Command to be Run (6208268)

When a standalone instance of Directory Server 5.2 is upgraded, the upgrade procedure requires the data in the Configuration Directory Server to be synchronized. Before running the sync-cds command, Directory Server searches for the presence of the adm.conf file. When the Administration Server is not configured, the file is not present and the sync-cds command cannot run.


Create a dummy adm.conf file so that the sync-cds command can run:

  1. Create a file called <ServerRoot>\admin-serv\config\adm.conf
  2. Edit the file to contain the following line only:

Where <hostname> is a fully qualified domain name for the host that the Directory Server is running on, and <administration_domain> is typically the host domain name.

For example:

Entries With Password Expiration Cannot be Replicated to Older Versions of Directory Server (6209543)

The pwdChangedTime attribute and usePwdChangedTime attribute are defined in Directory Server 5.2 2004Q2 and later versions. These attributes are not defined in Directory Server 5.2 2003Q4 or earlier versions.

When an entry is defined with password expiration in Directory Server 5.2 2004Q2 or later versions, the entry contains the pwdChangedTime attribute and usePwdChangedTime attribute. When that entry is replicated to a supplier running Directory Server 5.2 2003Q4 or an earlier version, the supplier cannot process any modifications to that entry. A schema violation error occurs because the supplier does not have the pwdChangedTime attribute in its schema.


Define the pwdChangedTime attribute and usePwdChangedTime attribute in the 00core.ldif file for all servers in the replication topology that are running Directory Server 5.2 2003Q4 or an earlier version.

To define the attributes, add the following lines to the 00core.ldif file for each server:

During installation of Directory Server With Access Manager the Index Is Corrupted (6305723)

During installation of Directory Server, the Access Manager adds indexes for the ‘ou’ attribute if they don’t exist. When the tool is run, the index is corrupted.


Reindex the Directory Server.


Bind With Zero-Length Password Is Treated as an Anonymous Bind (4703503)

If you use a zero-length password to bind to a directory, your bind is an anonymous bind - it is not a simple bind. Third party applications that authenticate users by performing a test bind might exhibit a security hole if they are not aware of this behavior.


Ensure that your client applications are aware of this feature.

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.

LDAP Modify Operations Through SSL Fail When Referred to Master Replica From Consumer Replica (4922620)

ldapmodify update operations over SSL fail when they are referred to a master replica from a consumer replica.

Error Message At Startup When passwordisglobalpolicy Is Enabled (4964523)

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


Ignore the incorrect error message.

Invalid Values Are Accepted for passwordMinLength in Individual Password Policies (4969034)

The passwordMinLength attribute in individual password policies is 2 - 512 characters. However, values outside of this range are accepted when an individual password policy is configured.


Configure individual password policies with passwordMinLength attribute of 2 - 512 characters.


Addition of Entries With objectClass=nsTomstone Can Cause Replication to Fail (2122375/5021269)

Adding an entry with objectClass=nstombstone can cause replication to fail.


Do not add entries with objectClass=nstombstone.

Local Schema Modifications Can 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 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 Directory Server 5.2 and Directory Server 5.1, perform the following tasks:

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.

Updates to the Retro Change Log on a Master Server Can be Lost (2121137/6178461)

When a master server crashes, changes made to the retro change log on that server can be lost.


Do not to use the retro change log on a master server. Instead, use the retro change log on the consumer server. If you are implementing failover of the retro change log, ensure that you have at least two consumer servers with enabled retro change logs.

Replication Monitoring Tools Do Not Support LDAP URLs That Contain Literal IPv6 Addresses (4702476)

The replication monitoring tools entrycmp, insync, and repldisc do not support LDAP URLs that contain literal IPv6 addresses.



Multi-Master Replication Over SSL With Certificate-Based Client Authentication Does Not Work If Preceded by SSL With Simple Authentication (4727672)

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


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

After Aborting a Total Update Cannot Restart a Total Update or Re-enable Replication on the Suffix (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.

Reports of Replication Delays With the insync Command and Fractional Replication (4856286)

The insync command-line tool has no concept of fractional replication. If fractional replication is configured, false reports of replication delays can be produced.



Schema Modifications Are Not Replicated in Incremental Updates (4868960)

If you modify the schema without making any other non schema-related modifications, your schema modifications will not be replicated immediately.


Wait for five minutes for your schema modifications to be replicated, or force replication by using the Send Updates Now option in the Directory Server Console.

Errors in Multi-Master Replication When nsslapd-lastmod Attribute Set to OFF (5010186)

The nsslapd-lastmod attribute specifies whether Directory Server maintains the modification attributes for Directory Server entries. When this attribute is set to OFF errors occur in multi-master replication.


When using multi-master replication, leave the nsslapd-lastmod attribute set to ON.

During Replication an Error Message Is Written Frequently to the Error Log (5029597)

During replication the following error message can be written frequently to the error log:

This error message increases the size of the error log file.


Ignore this error message.

passwordExpirationTime Attribute Is Unsynchronized After First Password Expiration Warning (5102180)

The passwordExpirationTime attribute is reset on the master when the first password expiration warning is given to the consumer. This attributes is not reset on the consumer and is therefore out of sync after the first password expiration warning.



Directory Server Can Crash If Backoff Timer Expires When Replication Agreement Detects an External Event (6272611)

If the backoff timer set by the replication agreement expires at the same time the replication agreement receives an external event, a race condition occurs that might cause the Directory Server to crash.

The issue can occur in the following scenarios:




DN Normalization Code Does Not Treat Case Sensitive Attributes Properly (4933500)

DN normalization code puts attribute names in lower case. The DN normalization code does not take into account the attribute syntax and the associated matching rule.



Directory Server Console

Internal Search Causes Directory Server Console to Display a Yellow Warning Flag (2113362)

In some search contexts a yellow warning flag is displayed. The yellow flag indicates that the Directory Server internal search mechanism has encountered an All IDs Threshold / Sorting issue. This flag does not represent a problem.


Either ignore the flag or create a browsing index (VLV index) to prevent the flag from occurring.

Console Does Not Support Passwords That Contain a Colon “:” (4535932)

The console does not support passwords that contain a colon “:”.


Do not use a colon in a password.

Console Does Not Support the Management of External Security Devices (4795512)

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


Manage external security devices by using the command line.

slapd Daemon Takes the Administration Server Port When Restarted From the Console (5002054)

When the slapd daemon is restarted from the console, it can take the Administration Server port and prevent Administration Server from being restarted by the console.


Restart the slapd daemon from the command line.

German Entries Are Sorted Incorrectly in Directory Server Console (4889951)

In the Directory Server console some german characters are sorted incorrectly. See the following examples:



Path to Help File for Directory Server Login Dialog Box Is Incorrect for Non-English Languages (5046970)

The path to the help .htm file for the Directory Server Login dialog box in non-English languages is incorrect. For example, for the Korean language, the incorrect path is as follows: <Server-Root>\manual\ko\console\help\help\login.htm.


Change the path to the help.htm file as shown in the following example. This example uses the Korean locale:

  1. Close Directory Server Console.
  2. Change directory to the <Server-Root>\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 the following file in a text editor:
  6. com\netscape\management\client\console\

  7. Change the path from
  8. login-help=manual\ko\console\help\help\login.htm



  9. Recreate the mcc52_ko.jar META-INF\* com\* jar file by using the
  10. jar cvf mcc52_ko.jar META-INF\* com\* command.

  11. Restart Directory Server Console.

LDIF Files Exported by Using the Tasks Tab on the Console Contain Additional Unnecessary Information for Backup (6197903)

This issue concerns LDIF files exported by using the Export to LDIF button in Tasks tab on the console. When a server is configured as a supplier or a hub, an exported LDIF file starts to collect replication information to initialize consumers. The exported LDIF file cannot be used with the Import from LDIF button in Tasks tab on the console.


Select one of the following workarounds:

Workaround 1: Export the LDIF file for a suffix by using the Object/Export command from the console menu. In the Export suffix dialog box, do not tick the Export replication information box. The resulting LDIF file can be used by the Import from LDIF button in the Tasks tab and by the Object/Initialize command in the console menu.

Workaround 2: Export the LDIF file without supplementary information by using the db2ldif command.

Workaround 3: Import the LDIF file for a suffix by using the Object/Initialize command from the console menu. This command handles LDIF files correctly, with and without replication information. Note, to initialize the contents of a suffix, you require an LDIF file with replication information.

Server Console Help Index Search Does Not Work in Traditional Chinese (zh_TW) (6205531)

Core Server

Server Crashes When Stopped During Export, Backup, Restore, or Index Creation (2121645/4678334)

Stopping the server during export, backup, restore, or index creation can cause it to crash.

Backend Instances Called “Default” Do Not Work (2122630)

Backend instances, or databases, called “Default” do not work.


Do not name a database “Default”.

Database Becomes Unavailable if LDIF File Is Inaccessible During Import (2126979)

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

tcp_keepalive_interval and tcp_ip_abort_interval Configuration Attributes Cannot be Used for Timeout (5087249)

The tcp_keepalive_interval and tcp_ip_abort_interval configuration attributes cannot be used to close idle connections on Directory Server.


Use the nsslapd-idletimeout configuration attribute to close idle connections.

Directory Server Plug-ins

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 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)

Post Operation Plug-In Function Not Called When Search Operation on Non-Existent Base DNs (5032637)

The post operation plug-in function for a search operation is not called if the search is performed on a non-existent base DN. This is inconsistent with the description of post-operation plug-ins in “Extending Client Request Handling” in the Directory Server Plug-in Developer’s Guide.



Error Message When ACL Plug-In Unable to Normalize Attribute Value (5089207)

The ACL plug-in normalizes attribute values in order to compare them with DN provided in the ACL rules. If an attribute value is not a DN, an error message is logged.


Ignore the error message.

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.


Maximum Size of Transaction Log File Cannot be Changed (4523783)

If you change the maximum size of the transaction log file when the database directory contains log files, the new size is not taken into account.



Cannot Create a Chained Suffix With an IPv6 Address by Using the Console (5019414)

When you create a new chained suffix with an IPv6 address by using the New Chained Suffix window of the console the Testing connection parameters popup window does not close automatically and the validity of the IPv6 address is not tested. Although the local configuration of the chained suffix is successful, the validity of the IPv6 address is not assured.


Do not to use the Test connection option when you configure a chaining suffix with an IPv6 address.

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.

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

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

Command Line Tools

The db2ldif -s Command Causes Errors on Suffixes With a Subtree (2122385)

When the db2ldif -s command is run on a suffix with one or more subtrees, errors occur. Also, all entries under the suffix are exported, including entries under subtree. This can cause problems if the ldif2db command is used on the exported LDIF file to re-initialize the suffix.


Do not use the db2ldif -s command on a suffix with one or more subtrees. Instead, use the db2ldif -n command as shown here:

Incorrect Error Message When Exporting a Subtree by Using the db2ldif -s Option (2122386)

When the db2ldif -s command is run on a suffix to export a subtree, the following incorrect error message can be generated:


Ignore this error message.

Absolute Paths Must be Specified for the Following Commands: db2bak,, bak2db, and (4897068)

db2ldif Command Creates an Output File In an Incorrect Directory (5029598)

The db2ldif command creates output LDIF files in an incorrect default directory when the file name only is specified. The db2ldif command should create output LDIF files in this directory:


Specify the absolute path to the file name of the output LDIF file.

mmldif Command Crashes (6205803)

The mmldif command crashes when used.



createtimestamp and modifytimestamp not Generated During ldif Import (6235452)

When an ldif file is imported to directory server by using the script, the createtimestamp and modifytimestamp are not generated. Note that this feature does not occur for online adds done by LDAP clients like ldapmodify.

Workaround 1

Edit the LDIF source file before import. This workaround works for LDIF input files that do not contain any entry with createtimestamp or modifytimestamp values. This workaround is good for Substitute ALL empty lines in the LDIF source file with the following 3 lines:

createtimestamp: 20050301132421Z

modifytimestamp: 20050301132421Z


Then import the file into the Directory Server.

Workaround 2

Import the source file by using ldapmodify instead of ldif2db. This workaround is slower than Workaround 1 but it works for LDIF input files with entries with createtimestamp or modifytimestamp values.

  1. Export the contents of your Directory Server by using db2ldif:
  2. db2ldif -n $instance -a <tmp>\exported.ldif

  3. Copy the first entry of <tmp>\exported.ldif into a new file named
  4. <tmp>\rootsuffix.ldif

  5. Re-import back the database only with the root suffix:
  6. ldif2db -n $instance -i <tmp>\rootsuffix.ldif

  7. Add all of the entries in <tmp>\rootsuffix.ldif by using the ldapmodify command:
  8. ldapmodify -a -c -h <host> -p <port> -D "cn=Directory Manager" -w & lt;password> -f <tmp>\exported.ldif

ldapdelete Command Hangs When NDS Plug-in Returns a Non-zero Value (6301267)

When the pre-operation plug-in for schema deletion returns a non-zero value, the ldapdelete command hangs.


Ensure that the pre-operation plug-ins (except abandon and unbind) send back a result (by using slapi_send_ldap_result) before returning a non zero status.

Redistributable Files

Sun Java System Directory Server 5.2 2005Q4 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 819-4267-10.

Additional Sun Resources

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

Copyright � 2006 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 � 2006 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.