000038424 - ASR fails to generate with 'ORA-31011: XML parsing failed' and 'LPX-00225: end-element tag "ROWSET" does not match start-element tag "APPLICATION_NAME" ' errors in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Feb 5, 2020Last modified by RSA Customer Support Employee on Aug 4, 2020
Version 31Show Document
  • View in full screen mode

Article Content

Article Number000038424
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1
IssueAn 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.

The RSA Identity Governance & Lifecycle user interface (Admin > Diagnostics) shows all Statistic Reports with a status of Generating.
User-added image

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

10/13/2019 18:22:21.636 ERROR (SystemReport) [com.aveksa.server.system.SystemReport]
Exception checking for internal table usage in collectors
at com.aveksa.server.system.SystemReport.appendCollectorContainerName(SystemReport.java:359)
at com.aveksa.server.system.SystemReport.appendCollectorRow(SystemReport.java:346)
at com.aveksa.server.system.SystemReport.checkCollector(SystemReport.java:332)
at com.aveksa.server.system.SystemReport.checkForSuspiciousCollectors(SystemReport.java:315)
at com.aveksa.server.system.SystemReport.getDBLockdownInfo(SystemReport.java:226)
at com.aveksa.server.system.SystemReport.backgroundGenerateReport(SystemReport.java:121)
at com.aveksa.server.system.SystemReport.access$000(SystemReport.java:52)
at com.aveksa.server.system.SystemReport$1.run(SystemReport.java:71)
at java.lang.Thread.run(Thread.java:748)
10/13/2019 18:24:43.210 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 11325
LPX-00225: end-element tag "ROWSET" does not match start-element tag "APPLICATION_NAME"
ORA-06512: at "SYS.XMLTYPE", line 272
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 257
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 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.)
CauseThis issue can occur when there are references to internal tables in collector definitions.

This is a known issue reported in engineering ticket ACM-101728.

Note: This issue also causes the problem reported in RSA Knowledge Base Article 000038645 -- 'Exception checking for internal table usage in collectors' and 'java.lang.NullPointerException' errors when generating a Log Artifact zip file in RSA Identity Governance & Lifecycle.
ResolutionThis issue is resolved in the following RSA Identity Governance & Lifecycle versions and/or patch levels:
  • RSA Identity Governance & Lifecycle 7.1.1 P05
  • 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.
WorkaroundCheck the collector definition(s) for references to internal RSA Identity Governance & Lifecycle tables and modify these references to use public views as documented in the RSA Identity Governance & Lifecycle Public Database Schema Reference for your version.