Performance of EBS Full Reconciliation taking Longer than Expected, Slow Performance on EBS Database.
Last updated on OCTOBER 13, 2017
Applies to:Identity Manager - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
When a full or incremental EBS UM reconciliation is executed from OIM, a select statement from the connector bundle (stored in search.properties file in 220.127.116.11+ versions of connector) is executed to fetch the EBS data for consideration. There are a lot of factors that determine how efficiently that SQL runs, but in general, the parameter filters and row_number ranges are appended far removed from the underlying hz_parties and fnd_users tables -- resulting in multiple full table scans of those tables (regardless of any existing indexes). This is not normally catastrophic, but the method in which the reconciliation batches the rows by using an aggregate function to determine row_number means that the same SQL must be executed numerous times as determined by the total number of rows / batch size.
Essentially, the retrieval of EBS data on the EBS database by the select identified in search.properties can be slow, and will be executed numerous times depending on the total number of users and the batch size specified in the IT Resource.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms