'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
3 years ago
Originally Published: 2020-03-27
Article Number
000042596
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1
 
Issue
When generating a Log Artifact zip file for RSA Identity Governance & Lifecycle Support by navigating to the Admin > Diagnostics > Log Artifact tab and pressing the Generate Zip File button, the zip file fails to generate with the following errors in the user interface:
 
User-added image
 
10/03/2019 08:11:48.896 ERROR (LogArtifactJob) [com.aveksa.server.system.SystemReport] Exception checking for internal table usage in collectors
java.lang.NullPointerException
    at com.aveksa.server.system.SystemReport.appendCollectorContainerName(SystemReport.java:357)
    at com.aveksa.server.system.SystemReport.appendCollectorRow(SystemReport.java:344)
    at com.aveksa.server.system.SystemReport.checkCollector(SystemReport.java:330)
    at com.aveksa.server.system.SystemReport.checkForSuspiciousCollectors(SystemReport.java:313)
    at com.aveksa.server.system.SystemReport.getDBLockdownInfo(SystemReport.java:224)
    at com.aveksa.server.system.SystemReport.backgroundGenerateReport(SystemReport.java:121)
    at com.aveksa.gui.pages.admin.downloadLogs.LogArtifactJob.generateASRReport(LogArtifactJob.java:618)
    at com.aveksa.gui.pages.admin.downloadLogs.LogArtifactJob.collectLogs(LogArtifactJob.java:414)
    at com.aveksa.gui.pages.admin.downloadLogs.LogArtifactJob.handleLogArtifactJob(LogArtifactJob.java:716)
    at com.aveksa.gui.pages.admin.downloadLogs.LogArtifactJob.access$200(LogArtifactJob.java:51)
    at com.aveksa.gui.pages.admin.downloadLogs.LogArtifactJob$1.run(LogArtifactJob.java:81)
    at java.lang.Thread.run(Thread.java:748)
 
After a few minutes, more errors occur:
 __ 
10/03/2019 08:13:20.259 INFO  (LogArtifactJob) [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 15138
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 252
ORA-06512: at line 1
 __ 
10/03/2019 08:13:20.262 ERROR (LogArtifactJob) [SystemErr] java.lang.RuntimeException: com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 15138
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 252
ORA-06512: at line 1
 __ 
10/03/2019 08:13:20.262 ERROR (LogArtifactJob) [SystemErr]     
  at com.aveksa.server.system.SystemReport.backgroundGenerateReport(SystemReport.java:133)
10/03/2019 08:13:20.262 ERROR (LogArtifactJob) [SystemErr]     
  at com.aveksa.gui.pages.admin.downloadLogs.LogArtifactJob.generateASRReport(LogArtifactJob.java:618)

Once this error occurs, the Generate Zip File option is greyed out and can no longer be chosen.
 
User-added image

 
Cause
This issue occurs when the Aveksa Statistics Report (ASR) cannot be generated.

This is a known issue reported in engineering ticket ACM-101766.
 
Resolution
Please refer to RSA Knowledge Base Article 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 for resolution.
 

Related Articles

Trending Articles

Don't see what you're looking for?