XML Stage - Heap allocation error

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
bluezed28
Participant
Posts: 6
Joined: Wed May 17, 2006 7:25 pm

XML Stage - Heap allocation error

Post by bluezed28 »

When I tried to run a large file > 200MB through XML Pluggin Stage i get the error
:
APT_CombinedOperatorController,0: Fatal Error: Throwing exception: APT_BadAlloc: Heap allocation failed.


I confirmed all the hard and soft ulimits were set to unlimited but still the 'data' resource said it was constrained. I my brain for days on this and IBM couldn't find a solution , but I found out the problem and solution:

In the dsenv file there is a couple lines near the bottom:
LDR_CNTRL=MAXDATA=0x60000000@USERREGS
export LDR_CNTRL

You need to comment it out otherwise the number of memory segments allocated is 6 and not unlimited. I can't say what are the downsides, but this is what I needed to do to get my jobs working in the test environment.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

It's been mentioned here before, but one thing to keep in mind is the fact that it is an AIX-specific solution.
-craig

"You can never have too many knives" -- Logan Nine Fingers
eostic
Premium Member
Premium Member
Posts: 3838
Joined: Mon Oct 17, 2005 9:34 am

Post by eostic »

...and be careful...you may not get a whole lot larger than what you have already.....at about 500M things hit limits in the current Stage.
Ernie Ostic

blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

True, there's still an upper limit of around 400 or 500 MBs as noted, and it seems to vary by platform. You really should be getting many small XML files rather than a small number of really big ones. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
skp
Premium Member
Premium Member
Posts: 135
Joined: Wed Dec 26, 2007 1:56 am
Location: India

Post by skp »

But if you comment it out in dsenv file.It will effect project level right.
Is there any way to reflect in only job and not at the project level.

Thanks,
Pani Kumar
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You can bring the environment variable into the job as a parameter and change its default value to the special token $UNSET.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
skp
Premium Member
Premium Member
Posts: 135
Joined: Wed Dec 26, 2007 1:56 am
Location: India

Post by skp »

Hi Ray,
Can I know which environment variable we need to use at job level?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

The one mentioned in the first post.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply