Generation of the Aveksa System Report (ASR) fails.
Generation of Log Artifacts fails in step generate ASR report.
One of the following ERROR messages (ORA-31061 or ORA-19202) is logged in
aveksaServer.log file:
01/07/2021 20:16:47.143 ERROR (SystemReportGenerator) [SystemErr] Caused by: com.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 287
ORA-06512: at line 1
06/03/2021 11:39:54.914 ERROR (SystemReportGenerator) [SystemErr] Caused by: com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-19202: Error occurred in XML processing
ORA-01489: result of string concatenation is too long
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 287
ORA-06512: at "SYS.DBMS_XMLGEN", line 237
ORA-06512: at "SYS.DBMS_XMLGEN", line 271
ORA-06512: at "AVUSER.SRXML", line 76
ORA-06512: at "AVUSER.SRXML", line 104
ORA-06512: at "AVUSER.SRSECTION_OBJECTS", line 23
ORA-06512: at "AVUSER.SRSECTION_OBJECTS", line 23
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 200
ORA-06512: at "AVUSER.SYSTEM_REPORT", line 259
ORA-06512: at line 1
This is a known issue that may occur in the following versions of the product that include additional workflow information in the ASR report:
- RSA Identity Governance & Lifecycle 7.2.0 P05
- RSA Identity Governance & Lifecycle 7.2.1 P01
- RSA Identity Governance & Lifecycle 7.5.0
This issue occurs for some customers who have legacy workflow data for the looping workflow section of the report that exceeds 4000 characters.
This issue is resolved in the following versions which cap the data that are gathered at 15 loops:
- RSA Identity Governance & Lifecycle 7.2.0 (please upgrade to 7.2.1)
- RSA Identity Governance & Lifecycle 7.2.1 P06
- RSA Identity Governance & Lifecycle 7.5.0 P03
If you are unable to patch to one of the versions where this is resolved please contact RSA Customer Support for a work-around for this issue.
