APT_BadAlloc: Heap allocation failed error in parallel job

mayurkb · Post by **mayurkb** » Mon Apr 04, 2016 11:20 am

I'm using lot of xml input stages in a parallel job. Currently I've 4 xml input stages but when I add 5th xmlinput stage, I get following error:
_CombinedOperatorController(1),0: Caught exception from runLocally(): APT_BadAlloc: Heap allocation failed..
APT_CombinedOperatorController(1),0: The runLocally() of the operator failed.
APT_CombinedOperatorController(1),0: Operator terminated abnormally: runLocally() did not return APT_StatusOk

Along with this I've lot of other lookup, scd and target database stages in the same job.
I'm not sure if I'm hitting 32 bit datastage process limit or it is something else?

UCDI · Post by **UCDI** » Mon Apr 04, 2016 1:02 pm

My C background suggests that this is 1970 speak for "you ran out of memory".

I could be wrong, but that is what the words mean to me.

chulett · Post by **chulett** » Mon Apr 04, 2016 1:20 pm

Yes indeed. And if you disable operator combination, it will tell you what actually threw the error - although it seems like you already know the answer to that.

mayurkb · Post by **mayurkb** » Mon Apr 04, 2016 1:41 pm

Thank you.
How do I disable operator combination?
what are my options here?

PaulVL · Post by **PaulVL** » Mon Apr 04, 2016 3:29 pm

You google your answer. Or you search the forums here since it's been covered before.

chulett · Post by **chulett** » Mon Apr 04, 2016 3:44 pm

Hard to know what to search for sometimes... but an exact search for "disable combination" or "disable operator combination" turns up some examples. Basically you add APT_DISABLE_COMBINATION to your job parameters and set it to TRUE.

mayurkb · Post by **mayurkb** » Tue Apr 05, 2016 12:52 pm

Thank you again. I meant what are my options if I'm running out of memory?

chulett · Post by **chulett** » Tue Apr 05, 2016 1:31 pm

Typically, one would search here for their error message to see how others have dealt with it in the past. So, an exact search for "APT_BadAlloc: Heap allocation failed" would seem to be in order. I'd start by cherry-picking any of the 67 results that are marked as Resolved and if there's no joy there dig deeper into the others.

mayurkb · Post by **mayurkb** » Fri Apr 29, 2016 12:09 pm

I was able to fix these errors by reducing the xml column widths and reducing the size on following of job parameters.
$APT_DEFAULT_TRANSPORT_BLOCK_SIZE and $APT_MAX_TRANSPORT_BLOCK_SIZE.

chulett · Post by **chulett** » Fri Apr 29, 2016 12:35 pm