000038720 - Slow INSERT statement executing from the SoD_Rule_Pkg in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Apr 13, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000038720
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.1
 
IssueThe following INSERT statement executed by the SoD_Rule_Pkg (Segregation of Duties Rule Package) was reported as running too slow in RSA Identity Governance & Lifecycle during SoD rule execution.
 

INSERT INTO GTT_BUCKET1_APPS
(APPLICATION_ID, APP_CORRELATION_ATTRIBUTE, RULE_ID)
SELECT APPLICATION_ID, APP_CORRELATION_VALUE, RULE_ID FROM
(
   SELECT GTT.APPLICATION_ID, CAV.COLUMN_VALUE AS APP_CORRELATION_VALUE, GTT.RULE_ID
   FROM GTT_BUCKET1_VIOLATIONS GTT,
   TABLE(UTILITIES_PKG.TOKENIZER(APP_CORRELATION_ATTRIBUTE,',')) CAV
)
MINUS
SELECT APPLICATION_ID, APP_CORRELATION_ATTRIBUTE, RULE_ID FROM GTT_BUCKET1_APPS;


 
CauseThe cause of this issue was never determined. However, we saw this issue worsened by enabling the TEMP_UNDO_ENABLED parameter. For more information on this parameter and its use with RSA Identity Governance & Lifecycle, see RSA Knowledge Base Article 000038718 -- Oracle 12c TEMP_UNDO_ENABLED parameter for managing GTT UNDO activity in RSA Identity Governance & Lifecycle.
 
ResolutionDisable the parameter TEMP_UNDO_ENABLED:
 
Login to SQL as SYS user

 


SQL> alter session set temp_undo_enabled=false scope=both;



By setting scope=both, this parameter will take effect immediately and will remain in effect after a system reboot.


 
NotesSee related RSA Knowledge Base Article 000038723 -- Poor performance when processing SoD Rules that use a Correlation Attribute in RSA Identity Governance & Lifecycle.
 

Attachments

    Outcomes