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

11g Release 2 (11.1.2)

E23738-05

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 PS1 (11.1.2.1.0)

- 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 PS1 (11.1.2.1.0) Limitations

- 1.5.2 Oracle Unified Directory Software Recommendations

2 Known Issues

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

- 2.2 Known Issues with Oracle Directory Services Manager

3 Resolved Issues

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

- 3.2 Resolved Issues for Oracle Directory Services Manager

Oracle® Fusion Middleware

Release Notes for Oracle Unified Directory

11g Release 2 (11.1.2)

E23738-05

July 2013

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

E23738-05

Copyright © 2010, 2013, 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 PS1 (11.1.2.1.0).

Audience

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

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 PS1 (11.1.2.1.0). They are as follows:

- Oracle Fusion Middleware Installation Guide for Oracle Unified Directory

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

- Oracle Fusion Middleware Developer'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 PS1 (11.1.2.1.0) 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 PS1 (11.1.2.1.0)"

- 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 PS1 (11.1.2.1.0).

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

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

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 PS1 (11.1.2.1.0) 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 PS1 (11.1.2.1.0) software, see Oracle Fusion Middleware Installation Guide for Oracle Unified Directory.

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 1,000 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.

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 1,000 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 5,000 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 PS1 (11.1.2.1.0) 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 = 65536

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 PS1 (11.1.2.1.0) 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 PS1 (11.1.2.1.0) Limitations"

- Section 1.5.2, "Oracle Unified Directory Software Recommendations"

1.5.1 Oracle Unified Directory 11g Release 2 PS1 (11.1.2.1.0) Limitations

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

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

- Oracle Unified Directory when setup for Enterprise User Security is currently validated for proxy for the following directory servers:

- Sun Java System Directory Server Enterprise Edition 6.3

- Microsoft Active Directory 2008 R2

- Novell eDirectory 8.8

- Oracle Unified Directory 11g Release 2

- 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 PS1 (11.1.2.1.0). 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 PS1 (11.1.2.1.0) and its components. It includes the following topics:

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

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

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

Table 2-1 lists known issues and limitations with 11g Release 2 PS1 (11.1.2.1.0).

Table 2-1 Known Issues with Oracle Unified Directory

Bug Number

Description

Workaround

11678445

When you run the oud-setup command and set the INSTANCE_NAME variable to a path for which you do not have the appropriate file permissions, the command fails.

The workaround is to have the required file permissions for the path to which INSTANCE_NAME variable points.

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.

11810392

If an entry has non-ASCII characters used in its name or any property, then the result returned when you run the ldapsearch command has those non-ASCII characters suppressed in the print.

There is currently no workaround for this issue.

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.

12266690

If you delete the load balancing workflow element or the load balancing algorithm, the load balancing routes are also deleted without any warning.

There is currently no workaround for this issue.

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.

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.

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.

13919632

The error log may contain servere_warning while setting the file permissions on Microsoft Windows using Java 6.

The workaround for this issue is to apply access-control restrictions from the top-level folder of any Oracle Unified Directory instance. In addition any Oracle Unified Directory process running on Microsoft Windows should be granted FULL access to the selected folder.

This issue does not appear in Java 7, because Oracle Unified Directory uses Java 7 File APIs to set permissions.

13954545

On Windows system with a JDK 1.7 JVM instance running, the ldapsearch.bat client might not handle the trailing "*" correctly.

The workaround is to download the latest JDK version to leverage the fixes and updates that are added to the Java SE platform.

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 does not 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

14065106

Oracle Unified Directory does not support translation of both messages and Help for oudCopyConfig, oudExtractMovePlan, and oudPasteConfig commands.

There is currently no workaround for this issue.

14080885

The moveplan does not have a field to update the path for keystore pin file during the cloning process.

The workaround is to use the dsconfig command on the cloned instance to update the key-store-pin-file value of JKS Key Manager Provider while cloning.

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 Unified Directory install is complete.

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

14562017

When you export data using JDK1.7.0_05 or higher the server is stopped.

The issue arises, because of an issue with JDK1.7. Until this is solved in an upcoming JDK1.7 release the workaround is to use the following option:

-XX:-OptimizeStringConcat

14753554

The gicadm command is not compatible with earlier Oracle Unified Directory versions.

There is currently no workaround for this issue.

14768666

When you use the addoutboundattr transformation, for instance cn=%sn% with conflict behavior set to Merge-real-and-virtual, then the ldapcompare command might erroneously return FALSE, because comparison is done only on sn values and not on cn values.

There is currently no workaround for this issue.

14768705

If you omit the curly brackets {} while configuring the client-attribute value for an AddOutboundTransformation, for instance client-attribute:"cn=%sn%.%cn%" instead of "cn={%sn%.%cn%}" then the dsconfig command does not throw any warning. However, the transformation does not work correctly.

There is currently no workaround for this issue.

14772631

When you configure an AddOutboundTransformation with virtualAttr={%sn%.%cn%@o.com}where the definition contains a dot, then a search request with a filter on the virtualAttr parameter might not work correctly.

For instance, the sn and cn backend attribute values contain a dot, such as "sn:sn.light" and "cn:cn.light." Here, a search request with a filter on the virtualAttr, for example "virtualAttr=sn.light.cn.light@o.com" might not work correctly.

There is currently no workaround for this issue.

15939456

In a replicated topology, the dsreplication status command displays incorrect port and information when you stop a replicated server.

There is currently no workaround for this issue.

16053072

The server does not start after an upgrade on Microsoft Windows.

The workaround for this issue is to manually copy the INSTALL_DIR\bat\start-ds.bat file into the instance that needs to be upgraded.

You can then run the start-ds.bat --upgrade command, and finally the start-ds.bat command to start the server.

16214645

When you install an Oracle database version 11.1.6.0 while setting up the Enterprise User Security (EUS) configuration, you might face ORA-28030 Server encountered problems accessing LDAP directory service.

The workaround is as follows:

1. Log in to Oracle Wallet Manager.

2. Open the wallet, which is by default stored at the following location:
ORACLE_BASE/admin/SID/wallet

3. Enter the password for wallet provided while registering using DBCA.

4. From the File menu, select auto-login.

5. Select the auto-login checkbox from the wallet manager.

6. Save the wallet to create the cwallet.sso file.

16372925

On Windows, while upgrading when you provide an installation location that contains an existing Oracle Unified Directory instance, then the installer does not throw any warning that the existing Oracle Unified Directory instance will be overwritten.

There is currently no workaround for this issue, because this is an upgrade operation. Therefore, it is recommended that you ensure your objective is to upgrade the existing Oracle Unified Directory instance.

16375185

After upgrading your directory service to the latest version, you need to copy the following files manually from the installation directory to the instance directory:

For Windows:

bat/split-ldif.bat
bat/gicadm.bat
bat/gicdump.bat
bat/dps2oud.bat

For Unix:

bin/split-ldif
bin/gicadm
bin/gicdump
bin/dps2oud

There is currently no workaround for this issue.

16477758

Entry cache might not be correctly updated.

You must disable the entry cache, running the following command:

dsconfig set-entry-cache-prop \
--cache-name FIFO \
--set enabled:false\
--port ADMIN_PORT \
--bindDN cn=Directory\ Manager \
--bindPassword ****** \
--no-prompt

16555520

After upgrading to 11g Release 2 PS1 (11.1.2.1.0) release, a warning about duplicate object class for configuration entries related to indexes ds-sync-hist and objectClass might be logged.

This warning might appear as output when you start the server or in the server.out log file.

You can safely ignore this warning as it has no impact on the server behavior.

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 PS1 (11.1.2.1.0) 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.

15928439

While accessing information of a changelog entry, you might receive a Java NullPointer exception if the entry does not have an objectclass specified.

There is currently no workaround for this issue.

16048731

When you click any item of type Objectclass on the Schema tab in Microsoft Internet Explorer, then the browser hangs and does not respond.

You might observe the same behavior for Content Rules in the Schema tab and Virtual Attributes in the Configuration tab.

The workaround is to apply a patch that addresses Bug 13417997 (v1 non_edg:script on the pg is causing ie to run slowly' err running qtp scripts). A patch for the current release is available as Patch 16478722 (merge request on top of 11.1.1.6.0 for Bugs 16011916 and 13417997). This patch can be downloaded from My Oracle Support.

16056177

On the Advanced Search page, when you click an entry in the Search Results table, the Show Attributes button does not appear if Optional Attributes is already expanded. However, if you collapse Optional Attibutes and then expand, the Show Attributes button appears. But, when you click the button the Select Attributes dialog box is blank.

There is currently no workaround for this issue.

16056480

On the Advanced Search page, from the Fetched Attributes list when you select Pick Attributes and click Search, then the entries are displayed in the Search Results table as expected. If you select an entry all the information is displayed correctly in the next page. However, if you click Refresh, then all the Mandatory Attributes values and Optional Attributes values disappear.

There is currently no workaround for this issue.

16167561

On the Advanced Search page, from the Fetched Attributes list when you select Pick Attributes then the Object Class and Common Name(cn) columns are blank when you click Next to go to the second page.

There is currently no workaround for this issue.

16561545

When you deploy Oracle Directory Services Manager on IBM WebSphere using the was_config script, then the deployed application does not have the shared library references.

The workaround is to add the missing shared library references, adf.oracle.domain and oracle.jsp.next in Oracle Directory Services Manager manually using the IBM WebSphere Administrative console. Perform the following steps:

1. Log in to the IBM WebSphere Administrative Console using the following URL:
http://HOSTNAME:PORT/ibm/console

Here, PORT is port number for the WebSphere administrative HTTP transport (WC_ adminhost). The default value is 9060.

2. In the console navigation tree, expand Applications, and then Application Types and then click WebSphere enterprise applications to open the list of applications.

3. In the Enterprise Applications page, click the application that needs to refer to the shared library.
In this scenario, select odsm_11.1.2.1.0.

4. Under Configurations, click Shared library references.
Note: The Shared Libraries column is empty for the Application odsm_11.1.2.1.0.

5. In the Shared Library Mapping for Modules section, select the check box for odsm_11.1.2.1.0 application, and then click the Reference shared libraries button above the table.

6. Select the following shared library from the Available list and move it to the Selected list:
adf.oracle.domain_1.0_11.1.1.2.0

oracle.jsp.next_11.1.1_11.1.1

7. Click OK.

8. Verify the Shared Libraries column for the row Application odsm_11.1.2.1.0 in the table.

9. Click OK.

10. On the Configuration main page, click Save to commit the changes.

11. Click OK.

12. Perform the following steps to restart the application that references the shared library:
a) Select the check box for odsm_11.1.2.1.0 application.

b) Click Stop.

c) Select the check box for odsm_11.1.2.1.0 application.

d) Click Start.

3 Resolved Issues

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

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

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

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

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

Table 3-1 Resolved Issues for Oracle Unified Directory

Bug Number

Description

Comment

12291765

In a replicated topology, if the server unexpectedly stopped immediately after receiving delete operations, the delete operations sometimes did not get replicated to the other servers in the topology.

This issue has been resolved.

14107698

The search operation was slow for an entry, which had large set of attributes if it was part of a big static group.

This issue has been resolved.

15964733

The following ACI did not work as expected:

aci: (targetattr!="aci")(version 3.0; acl "Allow read,search"; allow (search, read) userdn="ldap:///anyone";)

The issue has been resolved.

If non-operational attributes are specified in a non-equal operator in a targetattr rule, the rule applies to operational and non-operational attributes.

If attributes are specified in a non-equal operator in a targetattr rule, the rule applies to operational and non-operational attributes.

16442684

The changelog service sometimes stopped, because of some DB lock expiration.

This issue has been resolved.

3.2 Resolved Issues for Oracle Directory Services Manager

Oracle Unified Directory 11g Release 2 PS1 (11.1.2.1.0) 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

Comment

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.

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