Microsoft Azure Data Lake Storage Gen2 Connector > Mappings and mapping tasks with Microsoft Azure Data Lake Storage Gen2 > Troubleshooting a mapping or mapping task
  

Troubleshooting a mapping or mapping task

Mapping failed with a Java heap space error
When you read from or write large data sets to Microsoft Azure Data Lake Storage Gen2, certain mappings might fail with the following error:
[ERROR] java.lang.OutOfMemoryError: Java heap space
You must increase the heap size to run the mappings successfully. The recommended heap size is 1 GB.
Perform the following steps to configure the JVM options in the Secure Agent to increase the memory for the Java heap size:
  1. 1. Select Administrator > Runtime Environments.
  2. 2. On the Runtime Environments page, select the Secure Agent for which you want to increase memory from the list of available Secure Agents.
  3. 3. In the upper-right corner, click Edit.
  4. 4. In the System Configuration Details section, select Data Integration Server as the service and DTM as the type.
  5. 5. Edit the JVMOption property, and enter -Xmx1024m.
  6. Note: The recommended heap size is 1 GB. You can increase the heap size based on the data you want to process.
  7. 6. Click Save.
Unicode character strings are written incorrectly to the target
When you run a Microsoft Azure Data Lake Storage Gen2 mapping on a Linux machine, parameterize the source connection and object, and append data to the existing target, the Unicode character strings in the data are not written correctly to the target.
To resolve this issue, set the environment variable LC_ALL="en_US.UTF-8" in the Secure Agent on the Linux machine, and restart the Secure Agent.
Mapping fails if the directory name or subdirectory name contains Unicode characters
When you read from or write to a flat file in Microsoft Azure Data Lake Storage Gen2 and if the directory name or subdirectory name contains Unicode characters, the mapping fails.
To resolve this issue, set the environment variable LC_ALL="en_US.UTF-8" in the Secure Agent, and restart the Secure Agent.