ASR fails to generate and the log file has 'ORA-04063: package body "AVUSER.SRSECTION_SYSTEM" has errors' errors in RSA Identity Governance & Lifecycle 
2 years ago
Originally Published: 2017-01-12
Article Number
000040234
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle 
RSA Version/Condition: 7x
Platform (DB): Remote Oracle database
 
Issue
The Aveksa Statistics Report (ASR) cannot be generated in RSA Identity Governance & Lifecycle.

NOTE: An ASR is generated by going to (Admin > Diagnostics > Create Report) or (Admin > System > Diagnostics tab > Create Report) depending on your version of RSA Identity Governance & Lifecycle.

SYMPTOMS:
  1. The RSA Identity Governance & Lifecycle user interface (Admin > Diagnostics) shows all Statistics Reports with a status of Started:
User-added image
 
  1. The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) has the following errors:
01/10/2017 03:29:16.509 ERROR (SystemReport) [com.aveksa.server.system.SystemReport] ASR Params:
[Lcom.aveksa.server.db.ProcedureParameter;@6a560991
com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-04063: package body "AVUSER.SRSECTION_SYSTEM" has errors
ORA-06508: PL/SQL: could not find program unit being called: "AVUSER.SRSECTION_SYSTEM"
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 49
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 234
ORA-06512: at line 1
at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1520)
at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1378)
at com.aveksa.server.db.PersistenceManager.runStoredProcedure(PersistenceManager.java:255) at com.aveksa.server.system.SystemReport.backgroundGenerateReport(SystemReport.java:97)
at com.aveksa.server.system.SystemReport.access$000(SystemReport.java:30) at com.aveksa.server.system.SystemReport$1.run(SystemReport.java:42)
at java.lang.Thread.run(Thread.java:745) Caused by: java.sql.SQLException: ORA-04063: package body "AVUSER.SRSECTION_SYSTEM" has errors
ORA-06508: PL/SQL: could not find program unit being called: "AVUSER.SRSECTION_SYSTEM"
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 49
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 234
ORA-06512: at line 1
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:205)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1043)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3613)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3714)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4755)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1378)
at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.execute(WrappedPreparedStatement.java:404)
at com.aveksa.server.db.persistence.PersistenceServiceProvider.executeCallableStatement(PersistenceServiceProvider.java:1555)
at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1483)
... 6 more
01/10/2017 03:29:16.510 ERROR (SystemReport) [SystemErr] Exception in thread "SystemReport"
01/10/2017 03:29:16.510 ERROR (SystemReport) [SystemErr] java.lang.RuntimeException: com.aveksa.server.db.PersistenceException:
java.sql.SQLException: ORA-04063: package body "AVUSER.SRSECTION_SYSTEM" has errors
ORA-06508: PL/SQL: could not find program unit being called: "AVUSER.SRSECTION_SYSTEM"
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 49
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 234
ORA-06512: at line 1
  1. Under Admin > Diagnostics > Invalid Database Objects, the following invalid object is seen:
Object Name:  SRSECTION_SYSTEM
Object Type:  INVALID
 
Clicking the Recompile Invalid Objects button has no effect.
  1. Recompiling the invalid object in SQL*Plus is also unsuccessful:
    1. Logon to SQL*Plus as AVUSER:
    2. Attempt to recompile the SRSECTION_SYSTEM package by using the following command.  Note the Warning message returned.
SQL> alter package SRSECTION_SYSTEM compile body;
Warning: Package Body altered with compilation errors.
  1. The DBA_ERRORS table shows the following information on package SRSECTION_SYSTEM:
    1. Logon to SQL*Plus as the SYSDBA user:
    2. Execute the following SQL statement to review the contents of the DBA_ERRORS table:
SQL> select NAME,TYPE,SEQUENCE,LINE,TEXT,MESSAGE_NUMBER 
> from DBA_ERRORS where NAME='SRSECTION_SYSTEM';
If you have this issue, the output will look similar to the following:
201          9
PL/SQL: SQL Statement ignored
ERROR                  0

AVUSER
SRSECTION_SYSTEM                                PACKAGE BODY      5
       205         48
PL/SQL: ORA-00942: table or view does not exist
ERROR                  0

AVUSER
SRSECTION_SYSTEM                               PACKAGE BODY      6
       205         9
PL/SQL: SQL Statement ignored
ERROR                  0

AVUSER
SRSECTION_SYSTEM                               PACKAGE BODY      7
       209         55
PL/SQL: ORA-00942: table or view does not exist
ERROR                  0

AVUSER
SRSECTION_SYSTEM                               PACKAGE BODY      8
       209         9
PL/SQL: SQL Statement ignored
ERROR                  0

AVUSER
SRSECTION_SYSTEM                               PACKAGE BODY      9
       213         54
PL/SQL: ORA-00942: table or view does not exist
ERROR                  0

AVUSER
SRSECTION_SYSTEM                               PACKAGE BODY      10
       213         9
PL/SQL: SQL Statement ignored
ERROR                  0

181 rows selected

SQL>
  1. If this database was migrated from a previous version, the migrate.log file ($AVEKSA_HOME/wildfly/standalone/log/migrate.log) will have a similar error. See RSA Knowledge Base Article 000034682 -- 'Error(s) occured while compiling invalid object SRSECTION_SYSTEM:' during database migration in RSA Identity Governance & Lifecycle for more information.

  Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log and migrate.log files for your specific deployment if you are on a WildFly cluster or a non-WildFly platform. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
 
Cause
The procedure SRSECTION_SYSTEM executes a SQL SELECT statement against system table DBA_FREE_SPACE and AVUSER has not been granted access to that table. This issue occurs when the RSA Identity Governance & Lifecycle Oracle database has not been setup properly as per the RSA Identity Governance & Lifecycle Database Setup and Management Guide.
 
Resolution
As the SYSDBA user, GRANT SELECT on table DBA_FREE_SPACE to AVUSER in SQL using this command:​ 
SQL> GRANT SELECT on DBA_FREE_SPACE to AVUSER;

NOTE: Since the above GRANT was not performed on the database, it is possible that other required database setup may not have been completed on the database. Review the RSA Identity Governance & Lifecycle Database Setup and Management Guide for your version and ensure that the database has been properly configured for use with RSA Identity Governance & Lifecycle. In particular, see the section entitled Configure the User Schema Privilege Grants to view what needs to be executed against the Oracle database to ensure AVUSER has appropriate access to Oracle system views. 
 


 

Related Articles

Trending Articles

Don't see what you're looking for?