Page 1 of 1
Lookup: Fatal Error
Posted: Mon Jun 24, 2013 10:41 am
by bond88
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,
Posted: Mon Jun 24, 2013 11:33 am
by max.madsen
Didnt exist any error before that message?
Posted: Mon Jun 24, 2013 11:44 am
by bond88
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.
Posted: Mon Jun 24, 2013 11:46 am
by ArndW
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
Posted: Mon Jun 24, 2013 12:04 pm
by max.madsen
No more? Any warning before?
Posted: Mon Jun 24, 2013 3:38 pm
by bond88
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.
Posted: Mon Jun 24, 2013 3:40 pm
by bond88
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.