Datastage TX 8.0 - Out of Memory issue

Formally known as "Mercator Inside Integrator 6.7", DataStage TX enables high-volume, complex transactions without the need for additional coding.

Moderators: chulett, rschirm

Post Reply
zaino22
Premium Member
Premium Member
Posts: 81
Joined: Thu Mar 22, 2007 7:10 pm

Datastage TX 8.0 - Out of Memory issue

Post by zaino22 »

Hi,

I'm having an out of memory to execute map issue in datastage TX 8.0. Has anyone encountered this error before? any proposed solutions?

Any help would be appreciated, the error message is below:

Thanks!

<MapAudit StartTime="12:14:35 November 14, 2008">
<Platform>Command Server for Windows - Version 8.0(81)</Platform>
<ExecutionSummary MapStatus="Error" mapreturn="2" ElapsedSec="572.3759" BurstRes
<Message>Not enough memory to execute map</Message>
<CommandLine>F:\Ascential\DataStageTX_8.0\Code\Maps\DW00EDW_TX_REG_ProdOTC.mm
<ObjectsFound>7348082</ObjectsFound>
<ObjectsBuilt>25739264</ObjectsBuilt>
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Get more memory? Simplify the map?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
pkalva
Participant
Posts: 4
Joined: Tue Aug 01, 2006 2:58 am

Post by pkalva »

1. use work space as file instead of memory
2. increase the page size and page count
maltu
Participant
Posts: 7
Joined: Thu Jun 25, 2009 4:00 pm

Re: Datastage TX 8.0 - Out of Memory issue

Post by maltu »

I noticed from the log that the objects found and objects built size is quite high(its not in Kbs but higher), relatively speaking.

Memory contention is a common problem within mercator when you have multiple apps running on the same server instance. Maybe there are other apps that consume high memory being executed within the same time window.

Work with the busines and see if some of the non-critical jobs can be executed during non-peak hours so you can spread out the CPU and memory contention issues - i only say this assuming page setting and using workspace instead of memory didn't fix the problem.
Post Reply