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
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
Multi-App Collector Circuit Breaker trips incorrectly in SecurID Governance & Lifecycle Number of Views updateReviewItems web service fails to update review items when the UserID is the same for two users in RSA Identity Gover… Number of Views Multi-app Entitlement Data Collector (MAEDC) fails with DuplicateNameException in RSA Identity Governance & Lifecycle Number of Views Cisco ACS / ASA sends two requests to Authentication Manager 8.x Number of Views In RSA Identity Governance & Lifecycle, duplicate entries are created when a user switches between two Identity Data Colle… Number of Views
Don't see what you're looking for?
