Multi-App Entitlement Data Collector (MAEDC) fails with ORA-30926 if two MAEDCs overlap in Application Name and Internal ID in RSA Identity Governance & Lifecycle
Originally Published: 2019-04-26
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.0.2, 7.1.0
Issue
ORA-30926: unable to get a stable set of rows in the source tables ORA-06512: at "AVUSER.MAEDC_DATA_COLLECTOR", line 127 ORA-06512: at "AVUSER.MAEDC_DATA_COLLECTOR", line 409 ORA-06512: at line 1
Cause
As a example, consider two MAEDCs that collect from ApplicationAAA. Internally one has ID=5 and one has ID=415. In this case they evaluate the same:
where name like '%5-ApplicationAAA' where name like '%415-ApplicationAAA'
If ID 415 was 414, it would be fine as they would be seen as two separate MAEDCs:
where name like '%5-ApplicationAAA' where name like '%414-ApplicationAAA'
Resolution
Related Articles
Amazon Web Services IAM - Session Tags Configuration - RSA Ready Implementation Guide Number of Views Multi-app Entitlement Data Collector (MAEDC) fails with DuplicateNameException in RSA Identity Governance & Lifecycle Number of Views How a Multi-App Entitlement Collector (MAEDC) resolves entitlement relationships with accounts and groups collected by a M… Number of Views RSA Identity Governance and Lifecycle 7.0.1 rule pre-processing taking longer time to complete Number of Views Entitlements manually added when an Application has 'Complete Manual Activity Before Collection' enabled are not removed w… Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager 8.9 Patches and Hotfixes Readme Google Cloud Workforce Identity – RSA Ready Implementation Guide How to set up the REST RSA SecurID Authentication API for Authentication Manager 8.2 SP1
Don't see what you're looking for?
