Oracle Fusion Middleware Release Notes for Oracle Unified Directory, 11g Release 2 (11.1.2)

11g Release 2 (11.1.2)

E23738-02

Contents

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction

- 1.1 Latest Release Information

- 1.2 Purpose of this Document

- 1.3 Overview of Oracle Unified Directory 11g Release 2 (11.1.2)

- 1.3.1 Support for the Oracle Directory Integration Platform

- 1.3.1.1 Synchronization between Oracle Unified Directory and Oracle Internet Directory

- 1.3.1.2 Synchronization between Oracle Unified Directory and Third-Party Directories

- 1.4 System Requirements and Specifications

- 1.4.1 Hardware Requirements

- 1.4.2 Supported Operating Systems

- 1.4.3 Operating System Requirements

- 1.4.4 Java Requirements

- 1.4.5 File Descriptor Requirements (Linux Systems)

- 1.4.6 Specific Requirements for Installation in Solaris Zones

- 1.4.7 Supported Application Servers

- 1.4.8 Certified Languages

- 1.5 Software Environment Limitations and Recommendations

- 1.5.1 Oracle Unified Directory 11g Release 2 (11.1.2) Limitations

- 1.5.2 Oracle Unified Directory Software Recommendations

2 Known Issues

- 2.1 Known Issues with Oracle Unified Directory 11g Release 2 (11.1.2)

- 2.2 Known Issues with Oracle Directory Services Manager

3 Resolved Issues

- 3.1 Resolved Issues for Oracle Unified Directory 11g Release 2 (11.1.2)

- 3.2 Resolved Issues for Oracle Directory Services Manager

- 3.3 Documentation Errata

Oracle® Fusion Middleware

Release Notes for Oracle Unified Directory

11g Release 2 (11.1.2)

E23738-02

August 2012

Oracle Fusion Middleware Release Notes for Oracle Unified Directory, 11g Release 2 (11.1.2)

E23738-02

Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Devanshi Mohan

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Preface

This document contains the release information for Oracle Unified Directory 11g Release 2 (11.1.2).

Audience

This book is intended for administrators and users who want to deploy Oracle Unified Directory 11g Release 2 (11.1.2).

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see other documents in the Oracle Unified Directory documentation set for 11g Release 2 (11.1.2). They are as follows:

- Oracle Fusion Middleware Installation Guide for Oracle Unified Directory

- Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction

Oracle Unified Directory is a comprehensive, high-performance, highly-extensible next generation directory service that supports large-scale deployments and is easy to deploy, manage, and monitor.

This chapter introduces Release Notes for the Oracle Unified Directory 11g Release 2 (11.1.2) software and contains the following topics:

- Section 1.1, "Latest Release Information"

- Section 1.2, "Purpose of this Document"

- Section 1.3, "Overview of Oracle Unified Directory 11g Release 2 (11.1.2)"

- Section 1.4, "System Requirements and Specifications"

- Section 1.5, "Software Environment Limitations and Recommendations"

1.1 Latest Release Information

This document is accurate at the time of publication. Oracle will update the release notes periodically after the software release. You can access the latest information and additions to these release notes on the Oracle Technology Network at:

http://www.oracle.com/technetwork/indexes/documentation/index.html

1.2 Purpose of this Document

This document contains the release information for Oracle Unified Directory 11g Release 2 (11.1.2).

Oracle recommends you review its contents before installing, or working with the product.

1.3 Overview of Oracle Unified Directory 11g Release 2 (11.1.2)

Oracle Unified Directory is the newest member of the Oracle Directory Server product family. This next-generation directory server is designed for performance (fast reads and writes), scalability (vertical and horizontal), ease of use, robust availability, extensibility (numerous plug-in points), security, and maintenance.

Oracle Unified Directory 11g Release 2 (11.1.2) can function in one of the three modes:

- As an LDAP directory server, which contains data.

- As an LDAP proxy server, where the server acts as an interface between the client and the directory server that contains the data.

- As a replication gateway between Oracle Unified Directory and Oracle Directory Server Enterprise Edition.

For specific information about installing the Oracle Unified Directory 11g Release 2 (11.1.2) software, see Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.

1.3.1 Support for the Oracle Directory Integration Platform

Oracle Directory Integration Platform consists of a set of services and interfaces that facilitates synchronization and provisioning solutions between the directory and other repositories.

If you want to use Directory Integration Platform to enable synchronization for Oracle Unified Directory, you need to enable the Oracle Unified Directory changelog. For more information about how to enable the changelog in Oracle Unified Directory, see Oracle Fusion Middleware Administration Guide for Oracle Unified Directory.

Directory Integration Platform synchronization can be described as follows:

- Section 1.3.1.1, "Synchronization between Oracle Unified Directory and Oracle Internet Directory"

- Section 1.3.1.2, "Synchronization between Oracle Unified Directory and Third-Party Directories"

1.3.1.1 Synchronization between Oracle Unified Directory and Oracle Internet Directory

Oracle Directory Integration Platform 11.1.1.5 and higher supports synchronization between Oracle Internet Directory and Oracle Unified Directory. For more information about the synchronization procedure, see the chapter, Integrating with Oracle Directory Server Enterprise Edition in the Directory Integration Platform Administrator's guide. Oracle Directory Server Enterprise Edition was formerly known as the Sun Java System Directory Server. You need to replace all references of SJSDS in the guide to OUD for synchronization to work accurately.

1.3.1.2 Synchronization between Oracle Unified Directory and Third-Party Directories

To enable synchronization of data between Oracle Unified Directory and third-party directories, you need to integrate Oracle Directory Integration Platform with Oracle Unified Directory. You can obtain Oracle Directory Integration Platform by installing Oracle Identity Management release 11.1.1.6.0.

1.4 System Requirements and Specifications

Oracle Unified Directory installation and configuration will not complete successfully unless users meet the hardware and software prerequisite requirements before installation.

To ensure optimal server performance, your system must meet the following requirements:

- Section 1.4.1, "Hardware Requirements"

- Section 1.4.2, "Supported Operating Systems"

- Section 1.4.3, "Operating System Requirements"

- Section 1.4.4, "Java Requirements"

- Section 1.4.5, "File Descriptor Requirements (Linux Systems)"

- Section 1.4.6, "Specific Requirements for Installation in Solaris Zones,"

- Section 1.4.7, "Supported Application Servers"

- Section 1.4.8, "Certified Languages"

1.4.1 Hardware Requirements

For optimal performance, your system must have sufficient RAM memory for the JVM heap and database cache. For more information about setting the JVM heap and database cache, see "Configuring the JVM, Java Options, and Database Cache" in Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.

On Solaris systems, the operating system should be configured to have at least twice as much virtual memory as JVM heap. To achieve this, you might need to increase the size of the operating system swap space.

Your system should also have enough disk space to store the generated log files. The server log files can consume up to 1 GB of disk space with default server settings. In replicated environments, the change log database can grow up to 30-40 GB with loads of 1000 mods/sec. For information about setting the log file size, see "Configuring Log Rotation Policies" in Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory.

You can configure Oracle Unified Directory in such a way that it uses substantially less, or more, disk space depending on your application and performance needs. Any setup considerations must determine the amount of memory for the server's database and log files.

As a general guideline, the following hardware is recommended:

Hardware Component

Requirement

RAM

Evaluation purposes: At least 256 MB of free memory for a small database.

Production: Minimum of 2 GB.

Note: For large databases or large global index catalogs that require more than 4 GB of RAM, your system should use 64–bit architectures.

Local disk space

Evaluation purposes: For a small database and sufficient space for log files, your system should have at least 100 MB of free local disk space. Preferably, you should have at least 1 GB of disk space.

Production: For a typical production deployment with a maximum of 250,000 entries and no binary attributes, such as images, 4 GB of disk space might be sufficient for the database only. You might need an additional 1 GB of disk space for log files. You need to determine disk space for the change log database (DB), which is dependent on the load (updates per second) and on the replication purge delay (that is, the time the server should keep information about internal updates). The change log DB can grow up to 30-40 GB with loads of 1000 modifications per second.

When you use global index replication, ensure that you have enough disk space for the replication change logs. By default, the change log stores changes from the last 24 hours. The configuration should be based on the expected size of the service. For example, you would need 150 GB for 5000 modify/seconds.

The directory server does not support databases and logs installed on NFS-mounted file systems. Sufficient space should be provided for the database on a local file system, for example, in /var/opt or /local on UNIX or Linux machines.

1.4.2 Supported Operating Systems

For information about certified Operating Systems for Oracle Unified Directory 11g Release 2 (11.1.2) refer to the certification matrix on the following Web page

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

1.4.3 Operating System Requirements

The following table outlines the Operating System requirements.

Item

Requirement

Operating System TCP/IP Ports

The directory server uses the following ports by default:

- Administration connector, default port 4444

- LDAP, default port 389

- LDAPS, default port 636

- SNMP, default port 161 if configured

- JMX, default port 1689

- Replication port 8989

- The ports can differ between root and non-root users for some protocols.

File Descriptor Limits

On some Linux systems, the default file descriptor limit is set to 1024. This value might be too small when processing the total number of client connections, database files, and log files that the directory server requires to operate. It is strongly advised to increase the file descriptor limit to 64K or (65536 field descriptors).

1.4.4 Java Requirements

For information about certified Java version for each Java implementation, refer to the following Web page

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

1.4.5 File Descriptor Requirements (Linux Systems)

The issue described in this section affects Linux systems only. All other supported platforms are unaffected.

To ensure optimal server performance, the total number of client connections, database files, and log files must not exceed the maximum file descriptor limit on the operating system (ulimit -n). By default, the directory server allows an unlimited number of connections but is restricted by the file descriptor limit on the operating system. Linux systems limit the number of file descriptors that any one process may open to 1024 per process.

After the directory server has exceeded the file descriptor limit of 1024 per process, any new process and worker threads will be blocked. For example, if the directory server attempts to open a Oracle Berkeley JE database file when the operating system has exceeded the file descriptor limit, the directory server will no longer be able to open a connection that can lead to a corrupted database exception. Likewise, if you have a directory server that exceeds the file descriptor limit set by the operating system, the directory server can become unresponsive as the LDAP connection handler consumes all of the CPU's processing in attempting to open a new connection.

To fix this condition, set the maximum file descriptor limit to 65535 per process on Linux machines.

To view the maximum file descriptor limit, run the following command:

/sbin/sysctl -a | grep file-max

If the file-max value is lower than 65535, then perform the following steps:

1. Using any text editor, create or edit the /etc/sysctl.conf file, and add or edit lines similar to the following:

fs.file-max = 6815744

2. Enter the following command to change the current values of the kernel parameters:

/sbin/sysctl -p

3. Enter the command /sbin/sysctl -a | grep file-max to confirm that the values are set correctly.

4. Using any text editor, edit the /etc/security/limits.conf file, and add the following lines:

soft nofile 1024
hard nofile 65535

Note:

When you specify the values in the /etc/sysctl.conf or /etc/security/limits.conf file, they persist when you restart the system.

1.4.6 Specific Requirements for Installation in Solaris Zones

The Oracle Unified Directory software treats global, full local, and sparse zones as an independent physical system. Installing the server in any type of Solaris zone is therefore like installing on an independent system. The software does not share services or file locations with other zones.

1.4.7 Supported Application Servers

Before you begin the installation procedure, you must read the certification matrix to ensure that your environment meets the minimum installation requirement for each component.

For more information about certified application servers, refer to the certification matrix on the following Web page

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

1.4.8 Certified Languages

Oracle Unified Directory 11g Release 2 (11.1.2) is certified for the following languages:

- Chinese (Simplified)

- Chinese (Traditional)

- French

- German

- Italian

- Japanese

- Korean

- Spanish

- Portuguese (Brazilian)

Note:

Certain error messages (specifically, the SEVERE and FATAL messages) are displayed in English only.

1.5 Software Environment Limitations and Recommendations

The Oracle Unified Directory 11g Release 2 (11.1.2) software has some limitations that might affect the initial deployment of your directory server. Follow the recommendations for deployments in this section.

Administrators also should appropriately tune the Oracle Unified Directory directory server and its Java Virtual Machine (JVM) to ensure that adequately sized hardware is made available to support heavy write operations. For more information, see "Configuring the JVM, Java Options, and Database Cache" in Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.

This section describes the following topics:

- Section 1.5.1, "Oracle Unified Directory 11g Release 2 (11.1.2) Limitations"

- Section 1.5.2, "Oracle Unified Directory Software Recommendations"

1.5.1 Oracle Unified Directory 11g Release 2 (11.1.2) Limitations

This section lists the limitations of Oracle Unified Directory 11g Release 2 (11.1.2). They are as follows:

- The Oracle Unified Directory directory server provides full LDAP v3 support, except for alias dereferencing, and limited support for LDAPv2.

- To maximize performance when running the server as a proxy, you should restrict queries so that the proxy returns only the required attributes rather than all the attributes of an entry.

1.5.2 Oracle Unified Directory Software Recommendations

This section lists the recommendations for using Oracle Unified Directory 11g Release 2 (11.1.2). They are as follows:

- The directory server provides better performance when the database files are cached entirely into memory.

- The default settings of the Oracle Unified Directory directory server are targeted initially at evaluators or developers who are running equipment with a limited amount of resources. For this reason, you should tune the Java virtual machine (JVM) and the directory server itself to improve scalability and performance, particularly for write operations. For more information, see "Configuring the JVM, Java Options, and Database Cache" in Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.

- If you want to import large LDIF files by using the import-ldif command, then it is recommended that you use the --skipDNvalidation option. However, if you are not certain that the LDIF file is valid, using this option is not advised.

2 Known Issues

This chapter describes the known issues you might encounter when you install and configure Oracle Unified Directory 11g Release 2 (11.1.2) and its components. It includes the following topics:

- Section 2.1, "Known Issues with Oracle Unified Directory 11g Release 2 (11.1.2)"

- Section 2.2, "Known Issues with Oracle Directory Services Manager"

2.1 Known Issues with Oracle Unified Directory 11g Release 2 (11.1.2)

Table 2-1 lists known issues and limitations with Oracle Unified Directory 11g Release 2 (11.1.2).

Table 2-1 Known Issues with Oracle Unified Directory

Bug Number

Description

Workaround

11718654

In a replicated topology, if the server has a heavy workload then the following error message is recorded in the error log: The server failed to obtain a read lock on the parent entry dc=example, dc=com after multiple attempts.

You need to configure a larger database cache. For more information, see "Tuning the Server Configuration" in Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory.

11812850

On Windows system, if the path to your Java installation in the -jreLoc option includes a space character, then the installer does not run appropriately and terminates.

The workaround is to provide the path to your Java installation in DOS 8.3 format.

For example:

-jreloc C:\Progra~1\Java\jdk1.6.0_21

For more information, see "Installing Oracle Unified Directory" in Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.

11869296

Under heavy and sustained load the database cleaning process does not end.

The workaround is to configure a larger database cache. For more information, see "Tuning the Server Configuration" in Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory.

12280658

Modify DN (ModDN) is not supported if the DNs are indexed in the global index catalog (GIC).

If DNs are not indexed in the global index catalog, the modify DN operation is supported. Otherwise, only the modify RDN operation is supported.

12280661

When using global index replication, disabling replication on one server leaves references of that server in the other server configuration.

Run gicadm disable-replication on all global indexes of the same replication domain if you plan to reuse the removed server in another replication domain.

12291765

In a replicated topology, if a server unexpectedly stops immediately after receiving delete operations, the delete operations might not be replicated to the other servers in the topology.

The delete operations must be replayed manually on another server in the topology.

12291860

On Windows systems no SNMP trap is sent if the server is stopped by using stop-ds with no credentials. The server is, however, stopped correctly.

The SNMP trap is sent if the server is stopped by using stop-ds -D bindDN -p password.

12291880

The performance of the rebuild-index command decreases as the database IDs become unordered over time.

If possible, avoid reindexing large databases or import the database again. For more information, see "rebuild-index" in Oracle Fusion Middleware Administrator's Guide for Oracle Unified Directory.

12291930

Running the ldif-diff command on LDIF files over a certain size (around 600 Kbytes on Windows systems, larger on UNIX systems) results in a memory error similar to the following: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space.

Increase the heap size and rerun the command. For more information, see "Configuring the Default JVM and Java Arguments" in Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.

12329839

When you run the Oracle Unified Directory installer using the runInstaller command on SuSE Linux Enterprise Server 11, the prerequisite checks are not executed and an error is generated.

The workaround is to use the -ignoreSysPrereqs flag while running the runInstaller command.

13899662

When you use the batch file option of ds2oud, and the Oracle Directory Server Enterprise Edition configuration to be migrated includes a referential integrity plug-in, the generated batch file might contain duplicate dsconfig commands to create indexes. When you use this batch file to configure an Oracle Unified Directory instance, creation of the duplicate indexes fails, as the index already exists.

The issue can affect one or more indexes, depending on the referential integrity plug-in configuration.

Before you use the generated batch file to configure the Oracle Unified Directory instance, edit the batch file manually, to remove duplicate occurrences of the index creation command.

13965857

The -tih, -targetInstanceHomeLoc option of the oudPasteConfig command allows you to specify the location of the cloned server instance. If you specify an alternative location, for the cloned server instance, the instance is still created in the default location (TARGET_ORACLE_HOME/../TARGET_INSTANCE_NAME) and no error message is generated. However, the cloned server is configured partially as some custom parameters are not updated in the cloned server instance.

To successfully clone the server instance as the -tih parameter is mandatory, you must explicitly provide the default location for the -tih parameter as follows:

-tih TARGET_ORACLE_HOME/../TARGET_INSTANCE_NAME

13996369

The gicadm command cannot import a catalog when you specify a relative path.

You must specify an absolute path to import a catalog.

14055062

On Windows system, if the value for parameter -j, --rootUserPasswordFile is provided as a relative path, then oud-setup, oud-proxy-setup, and oud-replication-gateway-setup commands fail.

The workaround is to provide an absolute path for -j, --rootUserPasswordFile parameter.

For example:

-j C:\local\Password.txt

14283300

The following error may be written to the log files when running Java 6 Update 32 or later in a Windows environment:

category=JEB severity=SEVERE_WARNING msgID=8519808 msg=An error occurred while setting file permissions for the backend database directory C:\OUD\db\userRoot: org.opends.server.types.DirectoryException: One or more updates to the file permissions for C:\OUD\db\userRoot failed, but at least one update was successful. Some of the permissions for the file may have been altered.

When running Java 6 or later in a Windows environment you should use Windows' native security tools to assign access control on any folders containing sensitive information after the Oracle Universal Directory install is complete.

Because access permissions in Windows are inherited, you should assign access control restrictions to the top-level Oracle Universal Directory folder, and ensure that all running Oracle Universal Directory processes are granted full access to that folder.

2.2 Known Issues with Oracle Directory Services Manager

Table 2-2 lists known issues with Oracle Directory Services Manager at the time of Oracle Unified Directory 11g Release 2 (11.1.2) release.

Table 2-2 Known Issues with Oracle Directory Services Manager

Bug Number

Description

Workaround

11937031

Microsoft Internet Explorer 7 does not render some Web pages of Oracle Directory Services Manager properly. It does not lead to any loss of functionality, but some Web pages display with unnecessary scroll bars or wrapped field names.

The workaround is to upgrade the browser to Microsoft Internet Explorer 8 or Microsoft Internet Explorer 9. While using Microsoft Internet Explorer 8 or Microsoft Internet Explorer 9, you need to disable the compatibility view mode in the browser. For more information about how to disable the compatibility view mode in the browser, refer to the following Web page: http://support.microsoft.com/kb/956197

12363352

When you are in the screenreader mode, the Create, Apply, and Cancel buttons in the Oracle Directory Services Manager interface does not get focus after modification.

The workaround is to press the Tab key till you get the focus on the required button. Alternatively, you can use the mouse to activate the required button.

3 Resolved Issues

This chapter describes issues that have been resolved for Oracle Unified Directory 11g Release 1 (11.1.1) and its components. It includes the following topics:

- Section 3.1, "Resolved Issues for Oracle Unified Directory 11g Release 2 (11.1.2)"

- Section 3.2, "Resolved Issues for Oracle Directory Services Manager"

- Section 3.3, "Documentation Errata"

3.1 Resolved Issues for Oracle Unified Directory 11g Release 2 (11.1.2)

Oracle Unified Directory 11g Release 2 (11.1.2) resolves the known issues from previous releases listed in Table 3-1.

Table 3-1 Resolved Issues for Oracle Unified Directory

Bug Number

Description

Resolution

11897202

When you performed LDAP operation on Oracle Unified Directory with super user cn=directory manager, the modifersname in the changelog was set as cn=Directory Manager, cn=Root DNS, cn=config instead of cn=directory manager.

This issue has been resolved. The modifiersname now contains the name that is used to perform the bind even when it is a short root DN.

11937398

It was not possible to estimate the completion of the import-ldif tool.

This issue has been resolved. The following features are now available for the import-ldif tool:

- The progression percentage that displays the progression of indexes for the second phase.

- Debug messages have been qualified with the DEBUG severity.

The debug messages can be displayed using the -d or --debug option of the import-ldif tool.

11938169

The result code invalid-credentials was returned for a failed silent-bind operation.

This issue has been resolved. The result code now returned for a failed silent-bind operation is unwilling-to-perform.

An explicit message is also available from the diagnostic field of the LDAP response.

11938557

Some commands had an option where the password was provided in a clear text format on the command-line interface. This resulted in security exposure, because one could retrieve the password using the ps command on a UNIX machine.

This issue has been resolved. You should now use the file-based option to store the password.

Note: The LDAP commands have not been modified with the file-based option and these commands continue to support the password in clear text format on the command-line interface.

12263728

The Oracle Unified Directory proxy could not monitor the remote LDAP server if the LDAP extension property monitoring-check-interval was set to a value smaller than 1 second.

This issue has been resolved.

12300988

In a replicated topology with heavy workload the Oracle Unified Directory database grew quickly leading to disk full.

This issue has been resolved.

12320965

When you configured a directory server on a Microsoft Windows 2008 machine, the directory server did not listen to IPv6 versions of the Internet Protocol.

This issue has been resolved. The IPv6 version of the Internet protocol works with Microsoft Windows 2008 using JDK 7.

12331051

In an native character encoding environment, the Non-ASCII characters in stop-ds command message were garbled. However, if the character encoding UTF-8 was used, then this issue did not arise.

This issue has been resolved.

12416915

Replication between Oracle Directory Server Enterprise Edition and Oracle Unified Directory worked effectively in one direction only. Changes made on an Oracle Directory Server Enterprise Edition server were successfully replicated to Oracle Unified Directory. In a topology that included Oracle Directory Server Enterprise Edition servers and Oracle Unified Directory servers, only a very limited set of changes could be performed on the Oracle Unified Directory servers.

This issue has been resolved.

12561966

The dps2oud command failed when a resource limit policy or a load-balancing algorithm not yet supported by Oracle Unified Directory was migrated.

This issue has been resolved.

12992083

When you modified the schema file, the new file contained duplicate values for "cn:schema" attribute. Everytime you restarted the server a warning appeared, which stated that the second occurrence of "cn:schema" was ignored.

This issue has been resolved.

3.2 Resolved Issues for Oracle Directory Services Manager

Oracle Unified Directory 11g Release 2 (11.1.2) resolves the known issues from previous releases for Oracle Directory Services Manager listed in Table 3-2.

Table 3-2 Resolved Issues for Oracle Directory Services Manager

Bug Number

Description

Resolution

12533807

When you opened the Oracle Directory Services Manager Web page in Mozilla Firefox 3.x, you saw both the disabled and enabled icons for the same functionality. It did not lead to any loss of functionality, but caused some confusion.

This issue has been resolved.

3.3 Documentation Errata

Table 3-3 describes documentation errata.

Table 3-3 Documentation Errata

Bug Number

Description

Resolution

12584793

The Oracle Unified Directory documentation set referred to the INSTALL_PATH instead of the INSTANCE_PATH in the command-line examples.

This issue has been resolved. The command-line examples in the Oracle Unified Directory documentation set now reflects the correct path.

Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved.