"Error - could not execute query" shows instead of the role name when listing roles in RSA Identity Governance & Lifecycle
Originally Published: 2018-09-17
Last Modified: 2023-11-30
Article Number
000041123
Applies To
RSA Product Set: RSA Identity Governance &Lifecycle
RSA Version/Condition: 7.0.2 and 7.1.0
 
Issue
The role name is not displayed properly:
User-added image

The following error is logged in the aveksaServer.log: 
03/13/2017 12:30:37.446 ERROR (default task-153) [com.aveksa.gui.components.table.core.TableView] 
org.hibernate.exception.GenericJDBCException: could not execute query
	at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:140)
	at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:128)
        ......................................................................
	at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.sql.SQLException: Invalid character encountered in
	at oracle.sql.CharacterSet.failUTFConversion(CharacterSet.java:2865)
	at oracle.sql.CharacterSetAL32UTF8.toString(CharacterSetAL32UTF8.java:186)
	at oracle.xdb.XMLType.processString(XMLType.java:3090)
	at oracle.xdb.XMLType.processThin(XMLType.java:3211)
	at oracle.xdb.XMLType.<init>(XMLType.java:1413)
	at oracle.xdb.XMLType.createXML(XMLType.java:846)
	at oracle.xdb.XMLType.createXML(XMLType.java:823)
	at com.aveksa.server.db.StringToXMLTypeMapper.nullSafeGet(StringToXMLTypeMapper.java:98)
Cause
This error is due to Oracle bug 19629322.
Resolution
This  issue is fixed in RSA Identity Governance & Lifecycle 7.0.2 P10 and 7.1.0 P04.
 

Related Articles

Trending Articles

Don't see what you're looking for?