- Database Statistics against T_AV_EXPLODEDUSERENTITLEMENTS table are running after every collection in RSA Identity Governance & Lifecycle.
- Collections are slow in Step 11/12 Relationship Processing: Update Statistics.
- AWR reports show a query similar to the following running for a long time:
/* SQL Analyze(0) */ select /*+ full(t) parallel(t, 5) parallel_index(t, 5) dbms_stats cursor_sharing_exact use_weak_name_resl dynamic_sampling(0) no_monitoring xmlindex_sel_idx_tbl opt_param('optimizer_inmemory_aware' 'false') no_substrb_pad */to_char(count("ID")), substrb(dump(min("ID"), 16, 0, 64), 1, 240), substrb(dump(max("ID"), 16, 0, 64), 1, 240), to_char(count("RUN_ID")), substrb(dump(min("RUN_ID"), 16, 0, 64), 1, 240), substrb(dump(max("RUN_ID"), 16, 0, 64), 1, 240), to_char(count("DC_ID")), substrb(dump(min("DC_ID"), 16, 0, 64), 1, 240), substrb(dump(max("DC_ID"), 16, 0, 64), 1, 240), to_char(count("APPLICATION_ID")), substrb(dump(min("APPLICATION_ID"), 16, 0, 64), 1, 240), substrb(dump(max("APPLICATION_ID"), 16, 0, 64), ETC....This issue may occur on systems where the T_AV_EXPLODEDUSERENTITLEMENTS table is very large. Normally database statistics is run on this table after each collection. In some instances, the cost of this run may be more than the benefit.
This issue is resolved in the following versions that introduce a Custom Parameter
CollectorStatsConditional that can be used to enable conditional Database Statistics on the T_AV_EXPLODEDUSERENTITLEMENTS table.
- RSA Identity Governance & Lifecycle 7.2.1 P04
- RSA Identity Governance & Lifecycle 7.5.0
After patching to the version where this is resolved, set the following parameter from
Admin > System > Settings > Custom section. When this parameter is set, the Database Statistics will only run on the T_AV_EXPLODEDUSERENTITLEMENTS table if more than 5% of the table has changed.
| Parameter | Value |
| CollectorStatsConditional | True |
