Skip Headers
Oracle® Fusion Middleware Release Notes for Oracle Unified Directory
11g Release 2 (11.1.2)

Part Number E23738-02
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Known Issues

This chapter describes the known issues you might encounter when you install and configure Oracle Unified Directory 11g Release 2 (11.1.2) and its components. It includes the following topics:

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

Table 2-1 lists known issues and limitations with Oracle Unified Directory 11g Release 2 (11.1.2).

Table 2-1 Known Issues with Oracle Unified Directory

Bug Number Description Workaround

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.

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.

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.

12280661

When using global index replication, disabling replication on one server leaves references of that server in the other server configuration.

Run gicadm disable-replication on all global indexes of the same replication domain if you plan to reuse the removed server in another replication domain.

12291765

In a replicated topology, if a server unexpectedly stops immediately after receiving delete operations, the delete operations might not be replicated to the other servers in the topology.

The delete operations must be replayed manually on another server in the topology.

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.

12291930

Running the ldif-diff command on LDIF files over a certain size (around 600 Kbytes on Windows systems, larger on UNIX systems) results in a memory error similar to the following: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space.

Increase the heap size and rerun the command. For more information, see "Configuring the Default JVM and Java Arguments" in Oracle Fusion Middleware Installation 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.

13899662

When you use the batch file option of ds2oud, and the Oracle Directory Server Enterprise Edition configuration to be migrated includes a referential integrity plug-in, the generated batch file might contain duplicate dsconfig commands to create indexes. When you use this batch file to configure an Oracle Unified Directory instance, creation of the duplicate indexes fails, as the index already exists.

The issue can affect one or more indexes, depending on the referential integrity plug-in configuration.

Before you use the generated batch file to configure the Oracle Unified Directory instance, edit the batch file manually, to remove duplicate occurrences of the index creation command.

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 cannot 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

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

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


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 (11.1.2) 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.