000038391 - 'There are no entitlements in this account', 'The request could not be handled', and 'java.lang.NullPointerException' errors when performing Account Reviews in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jan 29, 2020Last modified by RSA Customer Support Employee on Feb 14, 2020
Version 20Show Document
  • View in full screen mode

Article Content

Article Number000038391
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1
IssueAccount Reviews in RSA Identity Governance & Lifecycle show accounts as having entitlements but when you click on Maintain, the review says the account has no entitlements. Further errors occur if you attempt to maintain the account using a bulk action and the account review cannot be completed.

The example below illustrates this issue:
  1. In the RSA Identity Governance & Lifecycle user interface go to (Reviews > Results > {Account Review Result Name} > Review items > {pick a tab} > {show all items}.
  2. Choose Maintain for any account.
  3. Note in the example below there are three entitlements associated with the account but once the Maintain button is toggled, the review says:

There are no entitlements in this account.


User-added image

  1. If you attempt to bulk maintain this review item, the below error occurs:

The request could not be handled.


User-added image

  1. If you click OK and OK again, this error occurs:

Error - java.lang.NullPointerException


User-added image

 The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) has the following error:

07/17/2019 10:44:03.779 ERROR (default task-510) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper]
ORA-00904: "CACHE_"."COMP_RES_CAS11": invalid identifier
07/17/2019 10:44:03.779 ERROR (default task-510) [com.aveksa.server.filter.ObjectListFilter] Exception while executing filter query
com.aveksa.server.db.PersistenceException: Executing JDBC query failed [select * from ( select  reviewComponents.ID AS REVIEW_COMP_ID,


01/02/2020 15:45:59.914 ERROR (default task-156) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper]
ORA-00904: "CACHE_"."COMP_RES_CAS12": invalid identifier
01/02/2020 15:45:59.916 ERROR (default task-156) [com.aveksa.server.filter.AccountReviewComponentFilter]
Exception running the following review component count query: select count(*) from ( select  reviewComponents.ID AS REVIEW_COMP_ID,

Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log for your specific deployment if you are on a WildFly cluster or a non-WildFly platform.
CauseThe significant error that indicates the problem cause is:

ORA-00904: "CACHE_"."COMP_RES_CASxx": invalid identifier

Starting in RSA Identity Governance & Lifecycle 7.1.0 P05, new custom attributes for business sources were added. These attributes are defined with data types CAS11 through CAS35 and are added by going to Admin > Attributes > Business Source tab > Edit > Add Attribute. The problem occurs because the feature to add the additional business source attributes was not completed and does not populate the new attributes into all the appropriate places.

This is a known issue reported in engineering ticket ACM-99694.
ResolutionThis issue is resolved in RSA Identity Governance & Lifecycle 7.2. The fix prevents this problem from occurring but if the problem has already occurred, the workaround is necessary.

Resolution steps:
  1. If you have defined any business source custom attributes that use data types CAS11 through AS35, apply the workaround below.
  2. Upgrade to RSA Identity Governance & Lifecycle 7.2.
WorkaroundRemove all business source custom attributes that have been defined using data types CAS11 through CAS35.

Please contact RSA Identity Governance & Lifecycle Support for the steps needed to remove these custom attributes and mention this RSA Knowledge Base Article ID 000038391 for reference.