JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Fusion Middleware Release Notes for Oracle Unified Directory 11g Release 1 (11.1.1)
search filter icon
search icon

Document Information

Preface

1.  Release Notes

2.  Known Issues

Known Issues with Oracle Unified Directory 11g Release 1 (11.1.1)

Known Issues with Oracle Directory Services Manager

Known Issues with Oracle Directory Services Manager

The following table lists the bugs that are known to exist with Oracle Directory Services Manager at the time of Oracle Unified Directory 11g Release 1 (11.1.1) release.

Bug Number
Description
Workaround
Bug 12362441
When you configure replication between two hosts with IPv6 addresses through the graphical-user Oracle Directory Services Manager interface, an error is generated.
The workaround is to try again.
Bug 12363352
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.
Bug 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
Bug 12533807
When you open the Oracle Directory Services Manager Web page in Mozilla Firefox 3.x, you will see both the disabled and enabled icons for the same functionality. It does not lead to any loss of functionality, but might cause some confusion.
There is currently no workaround available for this issue.