Log Artifacts generation fails due to ORA-31061 error in ASR report generation in RSA Identity Governance & Lifecycle
Originally Published: 2021-03-11
Last Modified: 2022-06-20
Article Number
000045166
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.1, 7.2.0, 7.2.1
 
Issue

The Log Artifacts generation fails when generating the ASR (Aveksa System Report). The following error is logged in the aveksaServer.log:

02/01/2021 13:17:51.664 WARN (LogArtifactJob) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 31061, SQLState: 99999
02/01/2021 13:17:51.664 ERROR (LogArtifactJob) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] ORA-31061: XDB error: special char to escaped char conversion failed.


The ASR (Aveksa System Report) fails when generated from the UI > Admin > Diagnostics tab. The following error is logged in the aveksaServer.log:

01/07/2021 20:16:47.131 ERROR (SystemReportGenerator) [com.aveksa.server.system.SystemReportGenerator] ASR Params: [Lcom.aveksa.server.db.ProcedureParameter;@62c33be7com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-31061: XDB error: special char to escaped char conversion failed.ORA-06512: at "AVUSER.SYSTEM_REPORT", line 287ORA-06512: at line 1
Cause
The ASR (Aveksa System Report) fails when parsing certain items in legacy custom data related to workflows.
Resolution
This issue is resolved in the following versions.  The patch migration contains a cleanup script ACM-109255-0127.sql that removes the problem data.
  • RSA Identity Governance & Lifecycle 7.1.1 P13
  • RSA Identity Governance & Lifecycle 7.2.0 P08
  • RSA Identity Governance & Lifecycle 7.2.1 P03
Workaround
If you are running into this issue and unable to apply the patches, please contact RSA Customer Support and quote this KB article 000039590 for a cleanup script to remove the problem data. 

Related Articles

Trending Articles

Don't see what you're looking for?