000032076 - RSA IMG Review entitlement table is blank and a numeric overflow exception is found in the logs

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

Article Content

Article Number000032076
Applies ToRSA Product Set: Identity Management and Governance (IMG), Aveksa
RSA Version/Condition: 5.0, 5.1, 5.5, 6.0
IssueIssue most commonly presents as a completely blank table in a review (as per below screenshot).
In rarer cases, the review will be partially populated but show some entitlements as blank, or when using a user view, the users will be populated, but all their sub-components will be blank.
User-added image
In the AveksaServer.log, the following error will be logged:
 
12/12/2013 08:32:04.237 ERROR (http-0.0.0.0-8443-15) [com.aveksa.server.filter.BaseReviewComponentFilter] SUCCESS method=processResults
java.sql.SQLException: Numeric Overflow
at oracle.jdbc.driver.NumberCommonAccessor.throwOverflow(NumberCommonAccessor.java:4380)
at oracle.jdbc.driver.NumberCommonAccessor.getInt(NumberCommonAccessor.java:131)
at oracle.jdbc.driver.OracleResultSetImpl.getInt(OracleResultSetImpl.java:928)
at oracle.jdbc.driver.OracleResultSet.getInt(OracleResultSet.java:388)
at org.jboss.resource.adapter.jdbc.WrappedResultSet.getInt(WrappedResultSet.java:692)
at com.aveksa.server.utils.BaseResultSetProcessor.getIntegerValue(BaseResultSetProcessor.java:108)
at com.aveksa.server.filter.review.processor.BaseReviewComponentResultSetProcessor.getDefaultReviewComponentAttributes(BaseReviewComponentResultSetProcessor.java:105)
at com.aveksa.server.filter.review.processor.BaseReviewComponentResultSetProcessor.getReviewComponent(BaseReviewComponentResultSetProcessor.java:150)
at com.aveksa.server.filter.review.processor.UserReviewComponentResultSetProcessor.getReviewComponent(UserReviewComponentResultSetProcessor.java:43)
at com.aveksa.server.filter.review.processor.UserReviewComponentResultSetProcessor.getReviewComponent(UserReviewComponentResultSetProcessor.java:22)
at com.aveksa.server.filter.BaseReviewComponentFilter.processResults(BaseReviewComponentFilter.java:433)
at com.aveksa.server.filter.BaseReviewComponentFilter.executeCriteria(BaseReviewComponentFilter.java:299)
at com.aveksa.server.filter.ObjectListFilter.getFilteredObjects(ObjectListFilter.java:96)
at com.aveksa.server.review.component.ReviewComponentData.getFilteredComponents(ReviewComponentData.java:89)
at com.aveksa.gui.objects.review.ReviewComponentObjectStore.getFilteredComponents(ReviewComponentObjectStore.java:498)
at com.aveksa.gui.objects.review.ReviewComponentObjectStore.getMonitorReviewComponents(ReviewComponentObjectStore.java:169)
at com.aveksa.gui.objects.review.dataSource.BaseReviewDBDataSource.getMonitorReviewComponents(BaseReviewDBDataSource.java:822)
at com.aveksa.gui.objects.review.dataSource.BaseReviewDBDataSource.getMonitorObjects(BaseReviewDBDataSource.java:904)
at com.aveksa.gui.objects.review.dataSource.UserMonitorDataSource.getObjects(UserMonitorDataSource.java:31)
at com.aveksa.gui.objects.review.dataSource.BaseReviewDBDataSource.getObjectList(BaseReviewDBDataSource.java:141)
at com.aveksa.gui.pages.review.review.newEdit.BaseReviewDetailTableModel.getObjectList(BaseReviewDetailTableModel.java:318)
at com.aveksa.gui.pages.review.review.newEdit.user.ReviewDetailUserAppsTable.getObjectList(ReviewDetailUserAppsTable.java:165)
at com.aveksa.gui.components.table.core.DefaultTableModel.getObjects(DefaultTableModel.java:150)
at com.aveksa.gui.components.table.core.TableModel.refreshObjects(TableModel.java:1896)
at com.aveksa.gui.components.table.core.TableModel.handleContent(TableModel.java:539)
at com.aveksa.gui.components.table.core.TableModel.handleRequest(TableModel.java:443)
at com.aveksa.gui.components.table.TableManager.handleRequest(TableManager.java:58)
at com.aveksa.gui.core.MainManager.handleRequest(MainManager.java:139)
at com.aveksa.gui.core.MainManager.doGet(MainManager.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.aveksa.gui.core.filters.LoginFilter.doFilter(LoginFilter.java:67)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:662)
CauseThe issue is due to the ID value on the table in the database that stores individual review components exceeding the limit of the datatype being used. In this case it is the integer datatype and the limit is 2^31 -1 or 2147483647.
ResolutionIn version 6.5 we have changed the datatype involved to have a significantly higher limit. Our recommendation is to upgrade to a version above 6.5 and generate a new run of the review.

Attachments

    Outcomes