Unable to read unicode characters when using CSE-KMS encryption
When you read data that contains unicode characters, the characters are read as junk characters.
To resolve this issue, perform the following steps:
1Click Administrator > Runtime Environments.
2On the Runtime Environments page, select the Secure Agent machine that runs the mapping.
3Click Edit.
4In the System Configuration Details section, select Data Integration Server as the Service and DTM as the Type.
5Edit the JVM Option system property and set the value to -Dfile.encoding=UTF-8.
6Click Ok to save the changes.
Test connection fails with the Profile name not found error
The issue occurs when you initially specify a named profile and not the default profile in the JDBC URL. On the subsequent run, if you remove the profile name to let the driver use the default profile, the driver still looks into the cached credentials provider and tries to use the previously specified profile name from the first run. This behavior causes test connection failure.
To resolve the issue, you must set the profile name to default in the JDBC URL.
For example, ProfileName=default.
If the problem persists, spawn a new Data Integration Server.