Oracle® Fusion Middleware Release Notes for Oracle Unified Directory 11g Release 2 (11.1.2) Part Number E23738-05 |
|
|
PDF · Mobi · ePub |
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"
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:
|
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. |
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. |