This chapter discusses the following topics related to connector testing:
This chapter describes known issues that you might encounter while creating or using Database Application Tables connectors. It includes the following topics:
See Also:
For Oracle Identity Manager release 9.1.0.x: "Known Issues of Generic Technology Connectors" chapter of Oracle Identity Manager Administrative and User Console Guide
For Oracle Identity Manager release 11.1.1 and 11.1.2.x: "Troubleshooting Generic Technology Connectors" chapter of Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager
The following are issues and workarounds associated with the connector:
Deletion of a Record from the Target System is not Reconciled into Oracle Identity Manager
Connector is Not Created when No Value is Specified for the Unique Attribute
No Support for Date Data Type in Microsoft SQL Server 2008 Target System
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.
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.
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.
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).
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.
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.
If you run the Evaluate User Policy scheduled job, the ProvisionAccountActionHandler fails to complete the job and the following error message appears:
<Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '76' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,238" seconds working on the request "Workmanager: OIMMDBWorkManager, Version: 0, Scheduled=false, Started=true, Started time: 237436 ms ", which is more than the configured time (StuckThreadMaxTime) of "1,200" seconds. Stack trace: java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:503) org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:810) org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) com.thortech.xl.gc.impl.common.DBFacade.getConnection(Unknown Source) com.thortech.xl.gc.impl.common.DBFacade.createParentRecord(Unknown Source) com.thortech.xl.gc.impl.prov.DBProvisioningTransportProvider.sendData(Unknown Source) .......
This is due to an issue with the Apache Commons Pool used by the connector.
To resolve this issue:
Download commons-pool-1.6.jar file from Apache Commons Pool release 1.6.
On the application server, update the com.bea.core.apache.commons.pool_1.3.0.jar and commons-pool-1.2.jar as follows:
Copy commons-pool-1.6.jar file to com.bea.core.apache.commons.pool_1.3.0.jar.
Copy commons-pool-1.6.jar file to commons-pool-1.2.jar file.
Restart the application server.
The following is an issue associated with Oracle Identity Manager:
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.
Table 4-1 lists solutions to some commonly encountered issues associated with the Google Apps connector:
| 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.
|
Define a fixed precise length for the NUMBER field in the Database Column Type. For example: NUMBER (10) |