Review generation fails in RSA Via Lifecycle and Governance when double byte characters are in any of the display names defined in the Review definition
RSA Product Set: RSA Via Lifecycle and Governance (RSA Via L&G) RSA Version/Condition: 7.0, 7.0.1
The following exceptions occur in the aveksaServer.log when you try to run review definitions that include double byte characters in the any of the review definition display names. An example of double byte characters are Turkish characters. An example of review definition display names are the 'Maintain' and 'Revoke' buttons:
ERROR:-20126: The creation of reviews failed.
ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing
LPX-00007: unexpected end-of-file encountered Stored Procedure:Generate_Review execution aborted.
Stack: ORA-06512: at "XDB.DBMS_XMLPARSER", line 157 ORA-06512: at "AVUSER.ENTITLEMENT_REVIEW_PKG",
line 10679 ORA-06512: at "AVUSER.ENTITLEMENT_REVIEW_PKG", line 991 ORA-06512:
t "AVUSER.ENTITLEMENT_REVIEW_PKG", line 1755.
ERROR (Exec Task Consumer#0) [com.aveksa.server.review.ReviewDefinitionVersion] Error creating the
ORA-20128: Failed to delete the review reports.ORA-31011: XML parsing failedORA-19202:
Error occurred in XML processingLPX-00007: unexpected end-of-file encounteredStored
Function:Create_Review execution aborted.Stack:ORA-06512: at "XDB.DBMS_XMLPARSER", line 157ORA-06512:
at "AVUSER.ENTITLEMENT_REVIEW_PKG", line 9462ORA-06512: at "AVUSER.ERROR_HANDLER_PKG", line 903ORA-06512:
at "AVUSER.ERROR_HANDLER_PKG", line 917ORA-06512: at "AVUSER.ENTITLEMENT_REVIEW_PKG", line 9514ORA-06512: at line 1 at
In this scenario the review generation has no issues if the double-byte characters are removed from the display name. For example,
Below is the admin error from the Admin > -Monitoring > Run ID screen:
The problem is with how RSA Via L&G processes the review configuration which includes the Maintain and Revoke labels. These settings are stored as an XML string in the Database. The way RSA Via L&G parses the XML does not support the double byte characters.
This issue is fixed in V7.0 P04 and 7.0.1 P01. The review will not fail to generate even if we have double byte characters in the display name.
Remove the double byte characters from all display names in the review definition.