000029739 - Unable to initialize security model. com.aveksa.server.core.DuplicateNameException: Aveksa ADC  when startup IMG

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000029739
Applies ToIMG 6.5, 6.8.1, 6.9
IssueIMG is unable to start and the following error occurs:
Unable to initialize security model. com.aveksa.server.core.DuplicateNameException: Aveksa ADC 
The aveksa security application must be initialized first by the System Operations Node(SON). 
See documentation regarding server nodes and deployment.
CauseThe SON error is not the issue here. The issue is the DuplicateNameException: Aveksa ADC. This error indicates that upon startup, the startup is attempting to create an Aveksa ADC collector but one already exists. How can this happen?
In later versions of Aveksa (IMG) there is a new application called 'Aveksa' with associated collectors called 'Aveksa ADC' and 'Aveksa EDC'. These are for the security model and should not be changed. However, these three items (application, ADC, EDC) are modifiable and if modified in any way IMG will not start up. The ability to modify these items is removed in 6.9.1.
Here is what happens. The 'Aveksa' application is defined by default and has an Aveksa ADC and EDC. Every time Aveksa starts, it checks to see if an Aveksa application exists which it normally does unless the application has been renamed. If the application has been renamed then it does not exist. Upon startup IMG will create a new application called 'Aveksa' and will also try to create the associated ADC and EDC collectors for this application. It they already exist, you get the duplicate name error and the startup fails.
 
ResolutionDo not rename the 'Aveksa' application.
Starting in 6.9.1, the name of the Aveksa application cannot be changed.
WorkaroundBefore doing these steps, backup the system. The preferred method of backup is the command line backup so it should not matter if the UI is unavailable.
1. Delete the newly created 'Aveksa' application (that was created from the restart because it no longer existed because it was renamed) from the following 2 tables: 
SQL> delete from t_applications_versions where application_id=(select id from t_applications where name='Aveksa'); 
SQL> delete from t_applications where name='Aveksa';
 
2. Rename the initially defined application of 'Aveksa' that was changed to something else back to 'Aveksa'. To do this find the Aveksa ADC in t_data_collectors and then see what application it is mapped to by using t_av_account_data_collectors. 
SQL> update t_applications set name='Aveksa' where id=( 
select ta.id 
from t_av_account_data_collectors taadc, t_data_collectors tdc, t_applications ta 
where taadc.id=tdc.id and 
taadc.resource_id=ta.id and 
tdc.name='Aveksa ADC'); 
SQL> update t_applications set alt_name='Aveksa' where id=( 
select ta.id 
from t_av_account_data_collectors taadc, t_data_collectors tdc, t_applications ta 
where taadc.id=tdc.id and 
taadc.resource_id=ta.id and 
tdc.name='Aveksa ADC'); 
SQL> commit; 

$ acm restart

Attachments

    Outcomes