Oracle Identity Manager 11g R2 – Troubleshooting Reconciliation

Problem Solution
Failure in processing events The error details can be obtained from the reconciliation tables, such as:

  • For batch processing, the exception is stored in RECON_BATCHES.RB_NOTE column
  • For single event processing, the exception is stored in RECON_EVENTS.RE_NOTE column
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:

  • For batch processing, the postprocess only orchestration ID can be read from the RECON_BATCHES.RB_NOTE column
  • For single event processing, end-to-end orchestration ID can be read from the RECON_EVENTS.RE_NOTE column

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:

  • If there is a lot of data, then rerun the reconciliation job.
  • There is a scheduled task provided for manual retry of such failed batches Retry Reconciliation Batch. This can be used for retrying specific batches only. Multiple comma-separated batches are supported.There is no predefined job associated with this schedule task. A job can be created as required.
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.

 

Leave a Reply

Your email address will not be published. Required fields are marked *