Oracle® Fusion Middleware

Release Notes for Oracle Unified Directory

11g Release 2 (11.1.2.1)

E23738-10

January 2017

This document contains the release information for Oracle Unified Directory 11g Release 2 (11.1.2.1). It describes the difference between Oracle Unified Directory (OUD) and its documented functionality.

Oracle recommends you review its contents before installing or working with OUD.

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://docs.oracle.com/cd/E49437_01/relnotes.111220/e23738/toc.htm

These Release Notes include the following topics:

- System Requirements and Specifications

- Software Environment Limitations and Recommendations

- Oracle Unified Directory (OUD) Known Issues and Workarounds

- Oracle Directory Service Manager (ODSM) Known Issues and Workarounds

- Documentation Accessibility

1 System Requirements and Specifications

Before performing any installation, you should read the system requirements and certification documents to ensure that your environment meets the minimum installation requirements for the products you are installing. The following documents are available on Oracle Technology Network (OTN):

- Oracle Fusion Middleware System Requirements and Specifications for Oracle Identity and Access Management
This document contains detailed information related to hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches when installing OUD with other Oracle products.

- Oracle Fusion Middleware Supported System Configurations
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

This landing page contains links to certification information for all products in Fusion Middleware suite.

- Oracle Unified Directory (OUD) 11gR1 (11.1.2.x) Certification Matrix
This document contains the most detailed information about supported application servers, supported clients, JDK requirements, and IPv4/IPv6 certifications for installing OUD. This document is updated when new information becomes available.

To access this document, on the Oracle Fusion Middleware Supported System Configurations landing page, follow the link to "System Requirements and Supported Platforms for Oracle Unified Directory 11gR1."

- Oracle® Fusion Middleware Installation Guide for Oracle Unified Directory 11g Release 2 (11.1.2)
Chapter 1, "Before You Install Oracle Unified Directory" contains pre-installation system notes and other information you should review prior to OUD installation.

The following sections describe additional information specific to OUD installation requirements:

- Section 1.1, "Hardware Requirements"

- Section 1.2, "Software Requirements"

- Section 1.3, "Certified Languages"

1.1 Hardware Requirements

As a general guideline, the following hardware is recommended:

Table 1 Recommended Hardware

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 100 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.

While the directory server can be used with databases and logs installed on NFS-mounted file systems, related files must not be accessed at same time from different systems. Sufficient space should be provided for the database.

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.

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.

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.

1.2 Software Requirements

In addition to the operating system, application server, and JDK requirements described in this document:

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

be sure to resolve the following OS-specific requirements:

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

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

1.2.1 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.2.2 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.3 Certified Languages

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

2 Software Environment Limitations and Recommendations

The Oracle Unified Directory 11g Release 2 (11.1.2.1) 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 2.1, "Oracle Unified Directory 11g Release 2 (11.1.2.1) Limitations"

- Section 2.2, "Oracle Unified Directory Software Recommendations"

2.1 Oracle Unified Directory 11g Release 2 (11.1.2.1) Limitations

This section lists the limitations of Oracle Unified Directory 11g Release 2 (11.1.2.1). 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 and Active Directory 2012

- Novell eDirectory 8.8

- Oracle Unified Directory 11g Release 2

- The proxy server provides the best search performance when the search queries ask for the specific required attributes (rather than all the attributes) of an entry.

2.2 Oracle Unified Directory Software Recommendations

This section lists the recommendations for using Oracle Unified Directory 11g Release 2 (11.1.2.1). 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.

3 Oracle Unified Directory (OUD) Known Issues and Workarounds

The following sections describe known issues and limitations with the Oracle Unified Directory 11g Release 2 (11.1.2.1) core server at the time of this release.

3.1 (Bug 16529038) When you Setup EUS with OUD as proxy, then the context does not get installed.

When you setup Oracle Enterprise User Security with Oracle Unified Directory configured as a proxy, the Oracle Enterprise User Security context does not get installed.

Workaround

The workaround is to apply a patch that addresses Bug 16529038 (Setup of EUS with OUD as a proxy does not install the EUS context). A patch for the current release is available as Patch ARU 16424146 (merge request on top of 11.1.1.2.1 for Bug 16529038). This patch can be downloaded from My Oracle Support.

You must perform the following steps for each new EUS suffix that was setup before applying the patch:

1. Create a copy of file of eusData.ldif file. You can obtain the file from the following location:
OUD_INSTALL_ROOT/OracleUnifiedDirectory/config/EUS/eusData.ldif

2. Edit the copy of eusData.ldif file as follows:

1. Replace all the occurrences (27) of 'dc=example,dc=com' with the DN of the EUS suffix.

2. Replace all the occurrences (6) of 'cn=orcladmin' with the Root User DN that you had provided in the setup.

3. Import the contents of the edited file in Step 2 using the import-ldif command as follows:

<OUD_INSTANCE_ROOT>/OUD/bin/import-ldif -n oraclecontext<SUFFIX_NUMBER> -l \
<PATH_OF_THE_EDITED_FILE> -F --hostname <OUD_HOST_NAME> \
--port <OUD_ADMINISTRATION_PORT> --bindDN <OUD_ROOT_USER_DN> \
--bindPasswordFile <PATH_OF_FILE_WITH_OUD_ROOT_USER_PASSWORD> \

3.2 (Bug 16555520) Mild warning when upgrading to 11GR2PS1.

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.

Workaround

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

3.3 (Bug 16477758) Entry cache might not be correctly updated.

Entry cache might not be correctly updated.

Workaround

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

3.4 (Bug 16375185) Upgrade requires manual copy of files.

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

Workaround

There is currently no workaround for this issue.

3.5 (Bug 16372925) Upgrade installation does not check for existing OUD Home Directory.

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.

Workaround

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.

3.6 (Bug 16214645) While setting up the Enterprise User Security (EUS) configuration, an error may occur.

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

Workaround

1. Launch Oracle Wallet Manager, and open the wallet which is by default stored under:
$ ORACLE_BASE/admin/<SID>/ wallet

2. Provide the password for wallet which was given while registering using DBCA.

3. Select the auto-login check box from the wallet manager File > Auto-login menu.

4. Save the wallet again to create the cwallet.sso.

3.7 (Bug 16053072) The server does not start after an upgrade.

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

Workaround

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.

3.8 (Bug 15939456) The dsreplication status command displays incorrect information when replica is stopped.

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

Workaround

There is currently no workaround for this issue.

3.9 (Bug 14772631) If an AddOutboundTransformation definition contains a dot, then a search request might fail.

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.

Workaround

There is currently no workaround for this issue.

3.10 (Bug 14768705) Errors occur while configuring the client-attribute value for an AddOutboundTransformation.

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.

Workaround

Be sure to use curly brackets {} while configuring the client-attribute value for AddOutboundTransformation.

3.11 (Bug 14768666) When you use the addoutboundattr transformation, the ldapcompare command might erroneously return FALSE.

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.

Workaround

There is currently no workaround for this issue.

3.12 (Bug 14753554) gicadm command should check server version

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

Workaround

There is currently no workaround for this issue.

3.13 (Bug 14562017) JVM server might stop if you export data using JDK1.7.0_05 or higher.

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

Workaround

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

3.14 (Bug 14283300) Running Java 6 Update 32 or later on Microsoft Windows throws an error.

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.

Workaround

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.

3.15 (Bug 14080885) The moveplan interface does not have a field to update the path for keystore pin file.

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

Workaround

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

3.16 (Bug 14065106) Translation is not supported for some error message and online Help.

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

Workaround

There is currently no workaround for this issue.

3.17 (Bug 14055062) If the value for parameter -j, --rootUserPasswordFile is provided as a relative path, commands fail.

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.

Workaround

Provide an absolute path for -j, --rootUserPasswordFile parameter.

For example:

-j C:\local\Password.txt

3.18 (Bug 13996369) The gicadm command does not import a catalog.

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

Workaround

Specify an absolute path to import a catalog.

3.19 (Bug 13965857) If you specify an alternative location for a cloned server instance, the cloned server instance is not completely configured.

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.

Workaround

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

3.20 (Bug 13954545) The ldapsearch.bat client incorrectly handles a trailing asterisk character.

On a Windows system with a JDK 1.7 (previous to Update 11) JVM instance running, the ldapsearch.bat client might not handle the trailing "*" correctly.

Workaround

Download the latest JDK version to leverage the fixes and updates that are added to the Java SE platform.

3.21 (Bug 13919632) Warning appears if you start server on Microsoft Windows using Java 7.

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

Workaround

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.

3.22 (Bug 12329839) Errors occur if the runInstaller command is executed on SuSE Linux Enterprise Server 11.

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.

Workaround

Use the -ignoreSysPrereqs flag while running the runInstaller command.

3.23 (Bug 12291880) Performance of rebuild-index decreases as the IDs become unordered.

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

Workaround

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.

3.24 (Bug 12291860) No SNMP trap is sent if the server is stopped using the stop-ds command with no credentials.

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.

Workaround

There is currently no workaround for this issue.

3.25 (Bug 12280658) The ModDN operation is not supported if DNs are indexed in the global index catalog (GIC).

When a distribution is using a GIC, and the GIC indexes the entry DNs, the ModifyDN operation is not supported.

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

Workaround

Although indexing the DN is recommended for performance reasons, as a workaround in this situation, do not index the DN.

3.26 (Bug 12266690) Load balancing routes are deleted without warning.

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

Workaround

There is currently no workaround for this issue.

3.27 (Bug 11869296) Cleaning process does not end.

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

Workaround

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

3.28 (Bug 11812850) Installation fails if path to Java includes a space character.

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.

Workaround

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.

3.29 (Bug 11810392) Non-ASCII characters are displayed base64-encoded.

If DN or attribute values of returned entries contain non-ASCII characters, the DN or values are displayed base64-encoded.

Workaround

There is currently no workaround for this issue.

3.30 (Bug 11718654) Error occurs in replicated topology with a heavy workload.

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."

Workaround

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

3.31 (Bug 11678445) The oud-setup command fails when appropriate file permissions are not set.

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.

Workaround

Set the required file permissions for the path to which INSTANCE_NAME variable points.

4 Oracle Directory Service Manager (ODSM) Known Issues and Workarounds

The following sections describe known issues with Oracle Directory Services Manager at the time of Oracle Unified Directory 11g Release 2 (11.1.2.1) release.

4.1 (Bug 11937031) Microsoft Internet Explorer 7 does not render some Web pages of Oracle Directory Services Manager properly.

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.

Workaround

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

4.2 (Bug 12363352) In screenreader mode, some buttons do not get focus after modification.

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.

Workaround

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.

4.3 (Bug 15928439) Java NullPointer exception occurs if a changelog entry does not contain a specified objectclass.

When this NullPointer exception is encountered, the contents of that particular changelog entry cannot be accessed from ODSM. You can continue to use ODSM to perform other tasks and access other entries.

Workaround

To access a changelog entry with no objectclasse specified, use a different LDAP client.

4.4 (Bug 16048731) Microsoft Internet Explorer does not respond if an item of type Objectclass is clicked.

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.

Workaround

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.

4.5 (Bug 16056177) On the Advanced Search page, when you click an entry in the Search Results table, some buttons do not behave as expected.

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.

Workaround

To view the entry details, you can select the same entry from Data Browser tab.

4.6 (Bug 16056480) All attributes disappear on Advanced Search page when Pick Attributes is selected.

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.

Workaround

There is currently no workaround available for this issue.

4.7 (Bug 16167561) Object Class and Common Name Attributes are blank on Advanced Search page when Pick Attributes is selected.

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.

Workaround

There is currently no workaround available for this issue.

4.8 (Bug 16561545) Shared libraries not present if was_config is used on IBM WebSphere

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.

Workaround

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:

1. Select the check box for odsm_11.1.2.1.0 application.

2. Click Stop.

3. Select the check box for odsm_11.1.2.1.0 application.

4. Click Start.

5 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 that have purchased support 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.

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

E23738-10

Copyright © 2016, 2017, Oracle and/or its affiliates. All rights reserved.

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, then 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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2017, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

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.

Warranty Disclaimer

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.

Restricted Rights Notice

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, then 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.

Hazardous Applications Notice

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.

Trademark Notice

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.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

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 that have purchased support 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.