Article Number
000067881
Applies To
RSA Identity Governance & Lifecycle 7.5.0
SecurID Governance & Lifecycle 7.5.2
Issue
A database collector of type Oracle fails when pressing the Test Connection button with the following error message:
10/07/2021 09:03:46.203 ERROR (Thread-825 (ActiveMQ-client-global-threads)) [com.aveksa.server.utils.NodeMessageBroker] Exception while getting test data from collector
com.aveksa.server.runtime.ServerException: com.aveksa.common.DataReadException: Could not get user data.. Caused by com.aveksa.common.DataReadException: Could not read data from resultset. Caused by java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): IW8ISO8859P8 Caused By
Cause
The files needed to support the legacy Oracle method of encoding international characters are not included by default in the product. This only occurs when NLS_CHARACTERSET value is set to IW8ISO8859P8 in the target Oracle Database.
This is a known issue in the following versions when connecting against Oracle databases that use international character sets:
- RSA Identity Governance & Lifecycle 7.5.0
- SecurID Governance & Lifecycle 7.5.2
Resolution
This is resolved in the following versions that include additional files (
orai18n-19.3.0.0.jar and
module.xml) required to support this character method:
- RSA Identity Governance & Lifecycle 7.5.0 P08
- SecurID Governance & Lifecycle 7.5.2 P04
Workaround
For the Wildfly server, add the files orai18n-19.3.0.0.jar and module.xml to the directory $AVEKSA_HOME/wildfly/modules/com/oracle/main. Restart acm for the changes to take effect.
For remote Aveksa Agents, add the files orai18n-19.3.0.0.jar and module.xml to the directory AveksaAgent/common/lib. Restart the aveksa agent for the changes to take effect.
Please contact RSA Customer Support and quote this article number to obtain the required files, orai18n-19.3.0.0.jar and module.xml.
