Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Introduction to Amazon S3 V2 Connector
  3. Connections for Amazon S3 V2
  4. Amazon S3 V2 sources and targets
  5. Mappings and mapping tasks with Amazon S3 V2
  6. Migrating a mapping
  7. Upgrading to Amazon S3 V2 Connector
  8. Data type reference
  9. Troubleshooting

Amazon S3 V2 Connector

Amazon S3 V2 Connector

Troubleshooting for Amazon S3 V2 Connector

Troubleshooting for Amazon S3 V2 Connector

Java heap size configuration

This section describes the errors that you might encounter if the JVM options in the Secure Agent is not configured accordingly to read a large number of files.
"ERROR java.lang.OutOfMemoryError: GC overhead limit exceeded" occurs when you run a Mapping task to write large number of records.
To resolve this issue, perform the following tasks to configure the JVM options in the Secure Agent to increase the memory for the Java heap size:
  1. Select
    Administrator
    Runtime Environments
    .
  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. In the upper-right corner, click
    Edit
    .
  4. In the
    System Configuration Details
    section, select the
    Type
    as
    DTM
    for the Data Integration Server.
  5. Edit the
    JVMOption1
    as
    -Xms2048m
    .
    Specify the maximum and minimum heap size based on the data you want to process.
  6. Restart the Secure Agent manually.
"[ERROR] java.lang.OutOfMemoryError: Java heap space" occurs when you run a mapping to write a file of size 1.4 GB or higher and select Informatica Encryption as the encryption type.
To resolve this issue, perform the following tasks to configure the JVM options in the Secure Agent to increase the memory for the Java heap size:
  1. Select
    Administrator
    Runtime Environments
    .
  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. In the upper-right corner, click
    Edit
    .
  4. In the
    System Configuration Details
    section, select the
    Type
    as
    DTM
    for the Data Integration Server.
  5. Edit the
    JVMOption1
    as
    -Xmx8046m
    .
  6. Restart the Secure Agent manually.

FFParserRetainNullString custom property

When you read from a .csv file that contains a string named
null
, the task does not write any data to the target. To resolve this issue, perform the following tasks and configure the custom property
FFParserRetainNullString
:
  1. Select
    Administrator
    Runtime Environments
    .
  2. On the
    Runtime Environments
    page, select the Secure Agent.
  3. In the upper-right corner, click
    Edit
    .
  4. In the
    Custom Configuration Details
    section, select the
    Type
    as
    Tomcat JRE
    for the Data Integration Server.
  5. Enter the
    Name
    as
    FFParserRetainNullString
    and the
    Value
    as
    true
    .
  6. Click
    Save
    .

RedirectToSessionLog custom property

When you select a source
or a target
Amazon S3 V2 file and configure the Parquet file format option, a large number of log files might be generated. To resolve this issue and disable the logs, perform the following tasks and configure the custom property
RedirectToSessionLog
:
  1. Select
    Administrator
    Runtime Environments
    .
  2. On the
    Runtime Environments
    page, select the Secure Agent.
  3. In the upper-right corner, click
    Edit
    .
  4. In the
    Custom Configuration Details
    section, select the
    Type
    as
    DTM
    for the Data Integration Server.
  5. Enter the
    Name
    as
    RedirectToSessionLog
    and the
    Value
    as
    No
    .
  6. Click
    Save
    .

Empty struct data in JSON file

If a JSON file has a field with an empty struct data, the Secure Agent ignores the field and reads the remaining fields during metadata read.
For example, if the JSON file has the following data in the first row:
{​"id":123,"address":{​}​}
, the
address
field is ignored and does not appear in the
Fields
tab. If the JSON file has values for the
address
field in the consecutive row, you can use the
Data elements to sample
property to fetch this field.

Amazon S3 bucket does not exist or the user does not have permission to access the bucket

Do not modify the time on the machine that hosts the Secure Agent. The time on the Secure Agent must be correct as per the time zone. Otherwise, the mapping fails with an exception.

Connection timeout error

Network performance and reliability issues when connecting to Amazon S3 can cause slow response times, connection failures, or request errors.
These issues might occur due to suboptimal configuration of client-side connection management parameters such as maximum concurrent connections, connection timeout, socket timeout, and retry settings.
To resolve these issues, configure the following properties for the Secure Agent:
  • -DAWSS3MaxConnectionPool. The maximum number of simultaneous HTTP connections that the Amazon S3 client can maintain.
  • -DAWSS3ConnectionTimeOut. The timeout duration in milliseconds to establish a connection to Amazon S3.
  • -DAWSS3SocketTimeOut. The timeout duration in milliseconds to read data from an established connection.
Perform the following tasks to configure the JVM options in the Secure Agent:
  1. Click
    Administrator
    Runtime Environments
    .
  2. On the
    Runtime Environments
    page, select the Secure Agent.
  3. Click
    Edit
    .
  4. In the
    System Configuration Details
    section, select
    Service
    as
    Data Integration Server
    and
    Type
    as
    DTM
    .
  5. Edit and configure the following JVM options:
    JVM option
    Value
    JVMOption1
    -DAWSS3MaxConnectionPool=<number of connections>
    JVMOption2
    -DAWSS3ConnectionTimeOut=<duration in milliseconds>
    JVMOption3
    -DAWSS3SocketTimeOut=<duration in milliseconds>
  6. Click
    Save
    .

0 COMMENTS

We’d like to hear from you!