Skip Headers
Oracle® Identity Manager Connector Guide for Database Application Tables
Release 9.1.0

E11194-13
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

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

4 Known Issues, Workarounds, and Troubleshooting

This chapter discusses the following topics related to connector testing:

4.1 Known Issues and Workarounds

This chapter describes known issues that you might encounter while creating or using Database Application Tables connectors. It includes the following topics:

See Also:

4.1.1 Connector Issues

The following are issues and workarounds associated with the connector:

4.1.1.1 Deletion of a Record from the Target System is not Reconciled into Oracle Identity Manager

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.

This is a known issue, and a workaround is currently not available.

4.1.1.2 Update Child Record Provisioning Operations

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.

4.1.1.3 Stored Procedure for Performing CRUD Operations

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

This is a known issue, and a workaround is currently not available.

4.1.1.4 ArrayIndexOutOfBounds Exception

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 directory:

    OIM_HOME/xellerate/ext and JBOSS_HOME/server/default/lib

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

4.1.1.5 Connector is Not Created when No Value is Specified for the Unique Attribute

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.

This is a known issue, and a workaround is currently not available.

4.1.1.6 No Support for Date Data Type in Microsoft SQL Server 2008 Target System

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.

4.1.2 Oracle Identity Manager Issues

The following is an issue associated with Oracle Identity Manager:

4.1.2.1 UI Text is Displayed in English in non-English Locales

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

This is a known issue, and a workaround is currently not available.

4.2 Troubleshooting

Table 4-1 lists solutions to some commonly encountered issues associated with the Google Apps connector:

Table 4-1 Troubleshooting

Problem Description Solution

Database Application Tables connector creation may fail with the following error, if the precise length of the NUMBER field in the Database Column Type is not defined.

DBProvisioningTransportProvider/sendData encounter some problems: DB_CREATE_PARENTRECORD_ERROR

Define a fixed precise length for the NUMBER field in the Database Column Type.

For example: NUMBER (10)