4 Known Issues

The following are known issues that you might encounter while creating or using Database Application Tables connectors:

See Also:

The "Known Issues of Generic Technology Connectors" chapter in Oracle Identity Manager Administrative and User Console Guide

• Bug 6644652

  Reconciliation of account deletion is not supported. In other words, if a record is deleted from the target database, then this deletion is not reconciled into Oracle Identity Manager.

• Bug 6614311

  Database Application Tables connectors do not support Update Child Record provisioning operations in this release. To work around this problem, you must first delete the record and then add the record with the required data modified.

• Bug 6696248

  Database Application Tables connectors do not support SSL communication between an Oracle Database target system and Oracle Identity Manager running on IBM WebSphere Application Server or Oracle Application Server.

• Bugs 6813795 and 7008825

  If you are using any locale other than the English locale, then on the Step 2: Specify Parameter Values page:

  • The following text is displayed as the label and description of the Unique Attribute parameter

    parentContainerUniqueKey

  • The following text is displayed as the label and description of the Database Date Format parameter

    dbDateFormat

• Bug 7009308

  While performing an Update User provisioning operation in the Administrative and User Console, if you try to modify the primary key field of the user, then the task is rejected. If you try to view the rejected task, then an error is thrown. The error message that is displayed is not localized.

• Bug 8449404

  SSL communication is not supported if IBM DB2/UDB is running on IBM z/OS.

• Bug 9831978

  On Oracle Identity Manager release 9.1.0.x, if the connector creation process fails for a particular connector, you can still create another connector. The Get Lock feature enables you to proceed with the creation of the next connector. On Oracle Identity Manager release 11.1.1, you cannot create another connector after the connector creation process fails, even if you use the Get Lock option.

• Bug 9915109

  The following issue is observed on Oracle Identity Manager release 11.1.1:

  On the Step 3: Modify Connector Configuration page, if the primary key is an auto-incremented field, then you map the primary key column of the Reconciliation Staging data set to the ID field of the OIM - Account data set. When you try saving the connector, an error is encountered.

  You can work around this issue by setting the length of the ID field to 38 or fewer characters.

• Bug 10206089

  Suppose a target system table has a primary key defined. While configuring a connector, if you designate a column as Unique, then the connector fails.

The following are limitations of the connector:

• The Database Application Tables connector does not support the use of stored procedures to perform CRUD operations against a table.

• If you are using the ojdbc6.jar file, then the ArrayIndexOutOfBounds exception is encountered during a provisioning operation on Oracle Identity Manager 9.1.0.2 BP02 or later. To resolve this issue:

  • On JBoss Application Server, replace the ojdbc6.jar file with the ojdbc14.jar file in the following directories:

    For Oracle Identity Manager release 9.1.0.x: OIM_HOME/xellerate/ext and JBOSS_HOME/server/default/lib

    For Oracle Identity Manager release 11.1.1: JAVA_HOME/jre/lib/ext

  • For all other certified application servers, apply Patch 7112447. This patch is available on My Oracle Support (formerly OracleMetaLink).

• In the case of table views (parent table view and child table view), you must specify the name of the Unique attribute while creating the connector. Otherwise, the connector is not created at the end of the procedure.

• If you are using Microsoft SQL Server 2008 as the target system, then this connector does not support the Date data type. A workaround for this issue is to use the DateTime data type.