ASR fails to generate with 'ORA-31011: XML parsing failed' and 'LPX-00241: entity reference is not well formed' errors in RSA Identity Governance & Lifecycle
3 years ago
Originally Published: 2017-10-11
Article Number
000041063
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.1, 7.0.2
 
Issue
An Aveksa Statistics Report (ASR) cannot be generated in RSA Identity Governance & Lifecycle.

The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) has errors similar to the following: 
06/30/2017 22:58:51.092 ERROR (SystemReport) [com.aveksa.server.system.SystemReport] 
ASR Params: [Lcom.aveksa.server.db.ProcedureParameter;@57040449
com.aveksa.server.db.PersistenceException: java.sql.SQLException: 
ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 85614
LPX-00241: entity reference is not well formed
ORA-06512: at "SYS.XMLTYPE", line 272
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 240
ORA-06512: at line 1
 at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1601)
 at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1459)
 at com.aveksa.server.db.PersistenceManager.runStoredProcedure(PersistenceManager.java:267)
 at com.aveksa.server.system.SystemReport.backgroundGenerateReport(SystemReport.java:124)
 at com.aveksa.server.system.SystemReport.access$000(SystemReport.java:50)
 at com.aveksa.server.system.SystemReport$1.run(SystemReport.java:69)
 at java.lang.Thread.run(Thread.java:745)
Caused by: java.sql.SQLException: 
ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 85614
LPX-00241: entity reference is not well formed
ORA-06512: at "SYS.XMLTYPE", line 272
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 240
ORA-06512: at line 1

or
  
01/11/2018 09:58:03.721 ERROR (SystemReport) [com.aveksa.server.system.SystemReport] 
ASR Params: [Lcom.aveksa.server.db.ProcedureParameter;@3086e335 
com.aveksa.server.db.PersistenceException: java.sql.SQLException:
ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 129693 
LPX-00242: invalid use of ampersand ('&') character (use &)
ORA-06512: at "SYS.XMLTYPE", line 272
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 241
ORA-06512: at line 1
 at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure (PersistenceServiceProvider.java:1601)
 at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure (PersistenceServiceProvider.java:1459)
 at com.aveksa.server.db.PersistenceManager.runStoredProcedure (PersistenceManager.java:267)
 at com.aveksa.server.system.SystemReport.backgroundGenerateReport (SystemReport.java:131)
 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)
Caused by: java.sql.SQLException: 
ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 129693
LPX-00242: invalid use of ampersand ('&') character (use &)
ORA-06512: at "SYS.XMLTYPE", line 272
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 241
ORA-06512: at line 1

 
Cause
The reason for this behavior is that there are special characters in the node name.

This is a known issue reported in engineering ticket ACM-76633.
 
Resolution
This issue is resolved in the following RSA Identity Governance & Lifecycle versions and patch levels:
  • RSA Identity Governance & Lifecycle 7.0.2 P05
  • RSA Identity Governance & Lifecycle 7.1.0
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.

Please see related RSA Knowledge Base Articles:
 
Workaround
The ASR may be run from the Linux command line. Please see RSA Knowledge Base Article 000027912 -- How to create an Aveksa Statistics Report (ASR) from the linux command line using SQL in RSA Identity Governance & Lifecycle for this workaround.
 
Attachments
If the attachment does not open when clicked, please refresh the page and try again. You must be logged into view the file(s).

    Related Articles

    Trending Articles

    Don't see what you're looking for?