000031009 - Active Directory Account Collector runs significantly longer after upgrading to version 7.0.0 of RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Aug 8, 2020
Version 7Show Document
  • View in full screen mode

Article Content

Article Number000031009
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.0
 
IssueWhen running an Active Directory Account Collector for the first time on RSA Identity Governance & Lifecycle 7.0.0 (Collectors > Account Collectors > {Collector name} > Collect Accounts button), the collector takes significantly longer to run than expected.

Oracle Enterprise Manager (OEM) for the top query at the time the collector is running shows the following query consuming resources: 
 

MERGE INTO T_AV_USER_ACCOUNT_MAPPINGS MAP
USING (SELECT ACCOUNT_ID, USER_ID
FROM GTT_DC_ACCOUNT_MAP WHERE OP_TYPE = :B1 )
GTT ON (MAP.ADC_ID = :B2 AND MAP.ACCOUNT_ID = GTT.ACCOUNT_ID
AND MAP.USER_ID = GTT.USER_ID)
WHEN MATCHED
THEN UPDATE SET MAP.STATE='VA', DELETED_BY = NULL
WHERE DELETED_BY IS NOT NULL AND STATE='IC'


 
CauseThis is a known issue reported in engineering ticket ACM-56128.

There is a nightly job that gathers statistics on certain tables to assist the Oracle optimizer in choosing the optimal execution path when executing SQL queries. A change in the way RSA Identity Governance & Lifecycle 7.0.0 gathers statistics causes the Oracle optimizer to choose the incorrect execution path.
 
ResolutionThis issue is resolved in RSA Identity Governance & Lifecycle 7.0.1.

The fix is to remove the existing statistics on collection tables prior to a collection run so that Oracle will dynamically gather statistics at collection run time and determine the best path for query execution.
 

Attachments

    Outcomes