Heap allocation failed

[saraswathi]

Hi,
I'm getting the below fatal errors, with different jobs
1) cs}}},1: Caught exception from runLocally(): APT_BadAlloc: Heap allocation failed..

2) main_program: /usr/lib/dld.sl: Call to malloc() failed to create BOR jump table
/usr/lib/dld.sl: Not enough space

3)Contents of phantom output file =>
RT_SC62/OshExecuter.sh[20]: 9278 Abort(coredump)

4) Parallel job reports failure (code 134)

What may be the reason for thse types of errors

[ArndW]

... Call to malloc() failed to create BOR jump table
/usr/lib/dld.sl: Not enough space

malloc() is a UNIX routine that is used to get program working memory. If this call fails it means the process has no more virtual memory or that the system has no more virtual memory available.

[ray.wurlod]

Cure: simple supply and demand. Supply more memory or reduce overall simultaneous demand for memory.

[priyadarshikunal]

... Call to malloc() failed to create BOR jump table
/usr/lib/dld.sl: Not enough space

malloc() is a UNIX routine that is used to get program working memory.

Its a function of C that allocates memory dynamically to the program that calls it depending on the parameter passed

Since the Unix kernel is made using assembly language and C

it uses the same method i.e. malloc() to allocate working memory (as ArndW said).

else the answer is same as ArndW and Ray have written.

Regards,

[/b]

[priyadarshikunal]

... Call to malloc() failed to create BOR jump table
/usr/lib/dld.sl: Not enough space

malloc() is a UNIX routine that is used to get program working memory.

Its a function of C that allocates memory dynamically to the program that calls it depending on the parameter passed

Since the Unix kernel is made using assembly language and C

it uses the same method i.e. malloc() to allocate working memory (as ArndW said).

else the answer is same as ArndW and Ray have written.

Regards,

[/b]

[ray.wurlod]

DataStage uses its own malloc(), not the standard UNIX one - it overloads the function. Be extremely careful making any assumptions about how malloc() works in a DataStage context. Indeed, it's better that you don't make any assumptions at all.