Heap growth during runLocally & Unable to allocate commu

[mandyli]

Hi

We are using Datastage 8.7.

We are converting job from 8.1 into 8.7. At present I am getting one job with following error.

" : Heap growth during runLocally(): 786560 bytes" from ORACLE Enterprise Stage" and after Source Oracle EP Stage I am getting another error from Join stage.
Join_LeftOuter,0: Fatal Error: Unable to allocate communication resources .

But the same job ran fine in DEV,QA & IT Datastage v 8.7 environments. The only difference is ORACLE exadata. even I can't view data from ORACLE stage.

is this anything missing here ?

Thanks
Man

[chulett]

Is Oracle Exadata supported by the connector? And what exactly do you mean by its "the only difference"?

[mandyli]

Thanks Lot.

But some other jobs run against Exadata using oracle EP stage.


Thanks
Man

[chulett]

You didn't really answer either of my questions, at least not directly.

I'd also suggest you double-check your kernal tunables in the problem environment.

[mandyli]

Hi

Now I am not connect to exadata connect to old ORACLE 11g database.

again I am getting below error

" Fatal Error: Unable to allocate communication resources". But the same job run on IT without any issue.

Is this anything I have see and view ulimt or something else?

my job design :

read from File set and --> transformer stage -- Join -- Sequential File.

Thanks
Man

[mandyli]

and also I am seeing following error .

FF_1,0: Export failed.
FF_1,0: Output file full
FF_1,0: Failure during execution of operator logic.
FF_1,0: Input 0 consumed 3070150 records.
FF_1,0: Fatal Error: No file descriptor was supplied.

FF_1 means : final target Sequential file.


Thanks
Man

[Mike]

FF_1,0: Output file full

Hi Man,

The above is your clue...

"Unable to allocate communication resources" most likely means either out of disk space or out of virtual memory.

"Heap growth during runLocally(): " is informational and not a concern as long as you're only seeing one or a few of these messages.

Check space usage in the file system where FF_1 is being written. Check the space usage in the file system where your project directory is located, and check space usage in the tmp file system.

Ideally, monitor the space usage while your job runs.

Mike

[mandyli]

we have enough space at /tmp.

I am getting error after FS_Extract,1: Progress: 80 percent.
FF_1,0: Export failed.
FF_1,0: Output file full
FF_1,0: Failure during execution of operator logic.
FF_1,0: Input 0 consumed 2995232 records.
FF_1,0: Fatal Error: No file descriptor was supplied.
Xfr_ObFilterListings,0: Fatal Error: Unable to allocate communication resources

Thanks
Man

[mandyli]

is there anything I have to increase limit to 2 GB?

May be the issue file system 2GB limit.

Thanks
Man

[mandyli]

Thanks lot.

I have fixed this issue. I have found the issue with filesystem and /GB Block size.

df -g /opt/IBM/IIS/Staging

Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/stg 24.00 3.12 88% 5329 1% /opt/IBM/IIS/Staging

I have asked UNIX Admin to increase GB blocks from 24.00 to 400.00 GB and then Job ran fine.

So the issue with /opt/IBM/IIS/Staging space.


Thanks
Man