InfoSphere DataStage job with large VARCHAR fields errors with ORCHESTRATE step execution terminating due to SIGINT error and the OOM Killer is activated.
Why do DataStage jobs with larger varchar fields produce SIGINT errors and activate the OOM killer?
Internally varchar fields are stored as a fixed length string for the full length defined for column length
Resolving the problem
The reason for this issue is a performance issue.
To have only the length of the data stored in the field, you will want to set the environment variable needed for each version
APT_OLD_BOUNDED_LENGTH=1 for Information Server 8.0.1,
APT_COMPRESS_BOUNDED_FIELDS=1 for Information Server 8.0.1 fp3 going forward.
In 8.5, the compress setting is the default.
Translate this page: