000035732 - No enum constant com.aveksa.server.core.DataCollector.Status.InActive when exporting metadata in RSA Identity Governance and Lifecycle

Document created by RSA Customer Support Employee on Dec 15, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000035732
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: All
 
IssueMetadata export fails with either "The request could not be handled" error:
User-added image
or a "No enum constant" error:
User-added image
The aveksaServer.log has this error:
 

11/09/2017 14:53:01.780 ERROR (default task-117) [com.aveksa.gui.pages.admin.metadata.edit.general.ExportWizard] buildTable error
java.lang.IllegalArgumentException: No enum constant com.aveksa.server.core.DataCollector.Status.InActive
at java.lang.Enum.valueOf(Enum.java:236)

 
CauseThere is a column in the T_DATA_COLLECTORS table called 'STATUS' which is allowed to have only three values:  'Active', 'Inactive', or null. This error occurs when  one or more rows in table T_DATA_COLLECTORS contains an invalid value in the STATUS column (i.e. a value other than 'Active', 'Inactive', or null.) These values are case-sensitive. In the example presented in this article, several collector definitions had a value of 'InActive' in the STATUS column. Note the capital 'A'. 
 
ResolutionTo resolve this issue, run a query to detect the invalid values and update them to valid values. Then try running the metadata export again.
1. Run this query to detect any invalid values:
     select distinct(status) from t_data_collectors;
In this example, there were several statuses of 'InActive' which need to be changed to 'Inactive.'
2. Run the update statement:
     update t_data_collectors set status='Inactive' where status='InActive';
3. Commit the changes:
     commit;
4. Verify the changes have been made by running the first query again and making sure at most only three values are returned ('Active', 'Inactive', null):
     select distinct(status) from t_data_collectors;
5. Run the metadata export again.

Attachments

    Outcomes