000030451 - ACM - Reports Fail with ORA-01031: insufficient privileges

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

Article Content

Article Number000030451
Applies ToRSA Product Set: RSA Via Lifecycle and Governance
RSA Product Set: RSA Identity Management and Governance
RSA Product Set: Aveksa Access Certification Manager
RSA Version/Condition: 6.9
Platform: Linux
Oracle Remote Database
IssueWhen running the Admin Error Report an error is thrown and this stack trace is present in the aveksaServer.log

aveksa.server.runtime.ServerException: com.aveksa.server.runtime.ServerException: com.aveksa.server.runtime.ServerException: com.aveksa.server.db.PersistenceException: com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-01031: insufficient privileges
ORA-06512: at "SYS.DBMS_SESSION", line 114
ORA-06512: at "AVUSER.REPORTING_PKG", line 598
ORA-06512: at line 1
at com.aveksa.server.report.Report.fillReport(Report.java:1674)
at com.aveksa.server.report.Report.fillReport(Report.java:1652)
at com.aveksa.gui.objects.report.GuiReport.getPreview(GuiReport.java:916)
at com.aveksa.gui.pages.report.report_definition.edit.tabular.BaseEditTabularReportWizard.updatePreview(BaseEditTabularReportWizard.java:200)
at com.aveksa.gui.pages.report.report_definition.edit.tabular.BaseEditTabularReportWizard.handlePreview(BaseEditTabularReportWizard.java:143)
at com.aveksa.gui.pages.report.report_definition.edit.tabular.BaseEditTabularReportWizard.handleRequest(BaseEditTabularReportWizard.java:101)
at com.aveksa.gui.pages.PageManager.forwardRequest(PageManager.java:559)
at com.aveksa.gui.pages.PageManager.handleRequest(PageManager.java:323)
at com.aveksa.gui.pages.PageManager.handleRequest(PageManager.java:254)
at com.aveksa.gui.core.MainManager.handleRequest(MainManager.java:182)
at com.aveksa.gui.core.MainManager.doGet(MainManager.java:131)
at com.aveksa.gui.core.MainManager.doPost(MainManager.java:417)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
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 com.aveksa.gui.util.security.XSSFilter.doFilter(XSSFilter.java:20)
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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
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:701)
Caused by: com.aveksa.server.runtime.ServerException: com.aveksa.server.runtime.ServerException: com.aveksa.server.db.PersistenceException: com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-01031: insufficient privileges
ORA-06512: at "SYS.DBMS_SESSION", line 114
ORA-06512: at "AVUSER.REPORTING_PKG", line 598
ORA-06512: at line 1
CauseWhen the remote database was configured the DBA did not create the AV_REPORT_CONTEXT.
ResolutionIn our Database_Setup_and_Management_Guide we give the following instructions:

Create a Report Context
The report context holds the filtering values for RSA IMG reports.
To create a report context, run the following command:
create or replace context AV_REPORT_CONTEXT using AVUSER.Reporting_Pkg;
NotesTo verify if the context exists in your database, from SQL execute the following query as sys:
select namespace from dba_context;

Attachments

    Outcomes