|Failure in processing events||The error details can be obtained from the reconciliation tables, such as:
|Failure occurring in kernel orchestration handler||The orchestration ID can be tracked from the reconciliation table, which can further be used to check the status of related handlers, such as:
There is no UI that displays LDAP synchronization during reconciliation. Therefore, you can only track LDAP success or failure by checking the status of LDAP sync event handlers in orchestration based on the ID available in RB_NOTE/RE_NOTE columns.
|After a job run, a lot of events are in Data Received status||Check if related batches are in Ready For Processing status by using the following statement:
select rb_batch_status, rb_note from recon_batches where rb_batch_status = 'Ready For Processing' and rj_key = JOB_ID_ON_UI
In addition, in the RECON_BATCHES.RB_NOTE, there is some generic exception, such as Connection issue. Fix the issue, and then perform any one of the following:
|Race Condition – Events are in failed status because some dependent attribute is still not reconciled, for example, user’s manager/organization needs to be reconciled before user.||
|The following error is generated when performing user update for trusted source reconciliation:
ORA Error Code =>ORA-00001: unique constraint (.) violated
|For of trusted source reconciliation, if the matching rule is based on Usr_login, then the matching rule must not be case-sensitive. Otherwise, updating users work as creating users, and the error might be generated.
- OIM 11g R2 – Running Reconciliation in a Multi-Threaded Environment
- Generic Technology Connectors – Common Errors Encountered During Reconciliation