Oracle® Fusion Middleware Release Notes for Oracle Unified Directory 11g Release 2 (11.1.2) Part Number E23738-02 |
|
|
PDF · Mobi · ePub |
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"
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 |
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 |
This issue has been resolved. The following features are now available for the
The debug messages can be displayed using the |
11938169 |
The result code |
This issue has been resolved. The result code now returned for a failed silent-bind operation is 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 |
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 |
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 |
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 |
This issue has been resolved. |
12992083 |
When you modified the schema file, the new file contained duplicate values for |
This issue has been resolved. |
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. |
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. |