Lookup: Fatal Error

bond88 · Post by **bond88** » Mon Jun 24, 2013 10:41 am

Hi,
I am getting following error

Lookup_3,0: Fatal Error: Unable to allocate communication resources

Can you please help me in resolving this issue?
I am getting 5-6 millions of records from source and after lookup I am using aggregator stage (aggregation on keys from lookup stage).

Thanks,

max.madsen · Post by **max.madsen** » Mon Jun 24, 2013 11:33 am

Didnt exist any error before that message?

bond88 · Post by **bond88** » Mon Jun 24, 2013 11:44 am

Errors Order:

node_node1: Player 7 terminated unexpectedly.

Lookup_3,1: Failure during execution of operator logic.

Lookup_3,1: Fatal Error: Unable to allocate communication resources

node_node2: Player 4 terminated unexpectedly.

Lookup_3,0: Failure during execution of operator logic.

ArndW · Post by **ArndW** » Mon Jun 24, 2013 11:46 am

There are several possible reasons for this error, I've been fighting that problem at this site for a while.

How long between job startup and getting this error? Is it around 10 seconds? If yes, then 8.7 Fixpack 2 has a fix for this issue - see APAR JR43681

max.madsen · Post by **max.madsen** » Mon Jun 24, 2013 12:04 pm

No more? Any warning before?

bond88 · Post by **bond88** » Mon Jun 24, 2013 3:38 pm

I got some warnings regarding Hash file. I thought these warnings/errors are occurring because of hash type in aggregator stage and changed it to sort type in aggregator stage then it ran successfully.

bond88 · Post by **bond88** » Mon Jun 24, 2013 3:40 pm

ArndW wrote:There are several possible reasons for this error, I've been fighting that problem at this site for a while.

How long between job startup and getting this error? Is it around 10 seconds? If yes, then 8.7 Fixpack 2 has a fix for this issue - see APAR JR43681

I was getting this error after 15-20 sec's. But I used aggregator after lookup and I changed hash type to sort type in aggregator stage then it ran successfully.