Search for account search tag matchingruleWhereClause, as shown in the

4-20 Oracle Fusion Middleware Users Guide for Oracle Identity Manager Here, the matchingruleWhereClause is the following: matchingruleWhereClauseUD_ADUSER.UD_ADUSER_OBJECTGUID=RA_ADUSER7.RECON_OBJE CTGUIDmatchingruleWhereClause

3. After identifying the columns constituting the matching rule in the user entity,

create the indexes accordingly. Selecting Indexes for Target Resource Reconciliation With Multi-Valued Data To select indexes based on the matching rule criteria in target resource reconciliation with multi-valued data:

1. Open the AD user profile file in a text editor.

2. For entitlements, search for the matchingruleWhereClause tag under childreconeventdata. Here, the matchingruleWhereClause tag is the following: matchingruleWhereClauseUD_ADUSRC.UD_ADUSRC_GROUPNAME=RA_UD_ADUSRC.RECON_MEM BEROFmatchingruleWhereClause 3. After identifying the columns constituting the matching rule in the user entity, create the indexes accordingly.

4.2.2.8.2 Collecting Database Schema Statistics for Reconciliation Performance

Database statistics is essential for the Oracle optimizer to select an optimal plan in running the SQL queries. Oracle recommends that the statistics are collected regularly for Oracle Identity Manager schema. Because Oracle Identity Manager 11g Release 1 11.1.1 uses lot of database SQL features for reconciliation process, make sure that the schema statistics are updated before running the reconciliation. Note: The AD user profile must be imported from the MDS by using the MDS utilities. See MDS Utilities and User Modifiable Metadata Files in the Oracle Fusion Middleware Developers Guide for Oracle Identity Manager for information about the MDS utilities. Note: Pointers for required indexes can also be taken by monitoring the real-time running of reconciliation process from the database side by using a performance-monitoring tool, such as Oracle Enterprise Manager Console, or through the Automatic Workload Repository AWR Reports available in Oracle Database 11g. Deployment Configurations 4-21 Because Oracle Identity Manager reconciliation process is a data-intensive process and quickly brings in large volume of data, database statistics must also be able to represent the underlying data correctly. To achieve this, refer to the following guidelines: ■ Make sure that statistics is collected for reconciliation on a fresh setup or with a low volume with no or negligible existing data in the Oracle Identity Manager schema. Maximum row count in relevant Oracle Identity Manager tables must be between 100 and 1000 rows. Examples of tables are USR table for trusted source reconciliation and parent account table for target resource reconciliation. ■ For the statistics to be a proper representative of data distribution after reconciliation has started and is expected to bring in a large volume of data, such as more than 20000 users or accounts, collect Oracle Identity Manager schema statistics in the following manner: a. Plan to gather statistics after the initial collection only after reconciliation has started successfully and has been running for a while. To verify this, check the counts of a few key tables from the Oracle Identity Manager schema, such as USR table for trusted source reconciliation and parent account UD_ tables for target resource reconciliation. b. After reconciliation has brought in almost 20000 to 25000 rows in the USR table or in the parent account tables, statistics can be collected. ■ After the statistics is collected, the performance might not improve immediately. However, as older SQL Plans are cleared from the shared pool of the Oracle Database, new and more efficient plans are created and performance improves.

4.2.2.9 Connector for Reconciliation

The connector refers to the software that extracts the changes from the target system and creates events in the reconciliation schema by calling the reconciliation APIs. If the connector that you want to use is shipped with a predefined reconciliation module, then a scheduled task definition is available. You use this component to control the frequency at which the target system is polled for changes to track data and other connector-specific parameters. Note: ■ Other options with DBMS_STATS.GATHER_SCHEMA_STATS API can be used as required, such as DEGREE,ESTIMATE_PERCENT based on the environment, data profile, Oracle DB Edition and underlying hardware capabilities. ■ See Database Performance Monitoring in the Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager for more information about collecting database schema statistics. Note: ■ Statistics can be gathered concurrently with reconciliation running. ■ The row counts specified in the guidelines are examples and you can determine any other row count for collecting statistics.