000035912 - RSA Identity Governance and Lifecycle Aveksa System Report (ASR) fails with error "ORA-31011: XML parsing failed"

Document created by RSA Customer Support Employee on Feb 19, 2018Last modified by RSA Customer Support Employee on Feb 19, 2018
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000035912
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0.0, 7.0.1, 7.0.2
 
IssueRSA Identity Governance and Lifecycle Aveksa System Report (ASR) from the Diagnostics tab on the Admin > Systems menu shows with status of Generating, but never completes and cannot be viewed.
 
User-added image

The following error shows in the /home/oracle/wildfly-8.2.0.Final/standalone/log/aveksaServer.log:

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
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059)
  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522)
  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257)
  at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587)
  at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:220)
  at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:48)
  at oracle.jdbc.driver.T4CCallableStatement.executeForRows (T4CCallableStatement.java:938)
  at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout (OracleStatement.java:1150)
  at oracle.jdbc.driver.OraclePreparedStatement.executeInternal (OraclePreparedStatement.java:4798)
  at oracle.jdbc.driver.OraclePreparedStatement.execute (OraclePreparedStatement.java:4901)
  at oracle.jdbc.driver.OracleCallableStatement.execute (OracleCallableStatement.java:5631)
  at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute (OraclePreparedStatementWrapper.java:1385)
  at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.execute (WrappedPreparedStatement.java:404)
  at com.aveksa.server.db.persistence.PersistenceServiceProvider.executeCallableStatement (PersistenceServiceProvider.java:1636)
  at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure (PersistenceServiceProvider.java:1564)
... 6 more
CauseThis failure occurs during the generation of the Aveksa System Report (ASR) if there are certain special characters in the input stream.  This often occurs when parsing the node name in a clustered installation. 
ResolutionThis issue is resolved in RSA Identity Governance and Lifecycle 7.0.2 P05.
WorkaroundThe following technique may be used from the acm server command line to generate an ASR report. 

From the command line run sqlplus as AVUSER, then execute the following command. 

EXECUTE system_report.Run(null,null,null,null,systimestamp);


The results are available from the RSA Identity Governance and Lifecycle console where the reports are normally archived under the Diagnostics Tab on the Admin > Systems menu. 


acm-702:~ # su - oracle
oracle@acm-702:~> sqlplus AVUSER

SQL*Plus: Release 12.1.0.2.0 Production on Wed Jan 17 12:07:19 2018

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Enter password: <enter AVUSER password>
Last Successful login time: Wed Jan 17 2018 11:25:23 -05:00

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> EXECUTE system_report.Run(null,null,null,null,systimestamp);

PL/SQL procedure successfully completed.

SQL>
NotesAdditionally, it is not possible to delete reports in the Generating status

Attachments

    Outcomes