Oracle® Identity Manager Connector Guide for Oracle E-Business User Management Release 9.1.0 Part Number E11203-03 |
|
|
View PDF |
The following are known issues associated with this release of the connector:
Bug 7207232
Some Asian languages use multibyte character sets. If the character limit for fields on the target system is specified in bytes, then the number of Asian-language characters that you can enter in a particular field may be less than the number of English-language characters that you can enter in the same field. The following example illustrates this point:
Suppose you can enter 50 characters of English in the User Last Name field of the target system. If you have configured the target system for the Japanese language, then you would not be able to enter more than 25 characters in the same field.
See Section 4.5, "Modifying Field Lengths on the Process Form" for information about working around this issue.
Bug 8504052
The Test Connectivity option does not work for the IT resource that you create to hold information about the SoD engine.
Bug 8513985
The "Lookup properties not configured correctly" message might be displayed on the Administrative and User Console even when lookup field values are correctly displayed. You can ignore this message.
Bug 8501508
During SoD-enabled provisioning, the connector does not provision entitlements if a conflict is encountered. When this occurs, you must revoke the conflicting entitlement and retry the entitlement provisioning operation. An error is thrown if you try to update the conflicting entitlement.
Bug 8535215
The "ORA-00904 OBJ_UDF_KEYFIELD is invalid" error is thrown during reconciliation. To resolve this problem, deselect the Sequence Recon check box on the Resource Objects form of the Design Console. See Oracle Identity Manager Design Console Guide for more information about this flag.
Bug 8534970
During reconciliation, the "java.sql.SQLException: ORA-01858" error is thrown if a date literal is included in the reconciliation query without specifying a format for the date literal. To avoid this problem, you must ensure that formats for date literals are specified by the use of the TO_DATE function. For example, instead of specifying a date value as '31-Dec-4712'
use TO_DATE('31-Dec-4712','DD-Mon-YYYY')
.