An Aveksa Statistics Report (ASR) cannot be generated in RSA Identity Governance & Lifecycle.
The RSA Identity Governance & Lifecycle user interface (
Admin >
Diagnostics) shows all Statistic Reports with a status of
Generating.
Image description
The
aveksaServer.log file has the following errors:
04/22/2019 05:01:37.070 INFO (WebContainer : 0) [com.aveksa.gui.core.LoginLogout] User logged in:
AveksaAdmin::SessionCount=1::UserCount=1
04/22/2019 05:02:22.746 INFO (SystemReport) [com.aveksa.server.db.persistence.PersistenceServiceProvider]
executeCallableStatement giving up after hitting SQLException:
ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 2722
LPX-00225: end-element tag "PROPERTY_VALUE" does not match start-element tag "Version"
ORA-06512: at "SYS.XMLTYPE", line 272
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 252
ORA-06512: at line 1
Please refer to RSA Knowledge Base Article
000030327 -- Arrtifacts to gather in RSA Identity Governance & Lifecycle to find the location of the
aveksaServer.log file for your specific deployment. The
aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (
Admin >
System >
Server Nodes tab > under
Logs.)
Certain WebSphere configuration values that have XML tags can cause this issue.
This is a known issue reported in engineering ticket ACM-97611.
This issue is resolved in the following RSA Identity Governance & Lifecycle versions and/or patch levels:
- RSA Identity Governance & Lifecycle 7.0.2 P14
- RSA Identity Governance & Lifecycle 7.1.0 P07
- RSA Identity Governance & Lifecycle 7.1.1 P01
- RSA Identity Governance & Lifecycle 7.2
Please contact
RSA Identity Governance & Lifecycle Support to move the report(s) from
Generating status to
Completed status. The report(s) may then be deleted.