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
3 years ago
Originally Published: 2019-04-26
Article Number
000046521
Applies To
RSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.0.2, 7.1.0

 
Issue
One Multi-App Entitlement Data Collector (MAEDC) runs successfully then a new MAEDC is added and now they both fail. The following errors are logged to the aveksaServer.log:
  
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
If two Multi-App Entitlement Data Collectors share the same application name and the same last digit of their internal ID, it results in duplicates during data processing and the MAEDC collections fail.


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
This issue is fixed in 7.0.2 P12 and 7.1.0 P06.

Related Articles

Trending Articles

Don't see what you're looking for?