Parallel job is being Aborted -- showing Not enough space

[sriramjagannadh]

Hi,

We are facing a problem with a Parallel job , which has an input dataset and a lookup dataset is being joined with a LookupStage and then output is copy stage --> Tranesformer --> creating a dataset.

But before creating the output dataset job is aborting, giving this log.


LKP,1: Could not map table file "/path/xx/lookuptable.20061006.drmm0ac (size 552711192 bytes)": Not enough space
Error finalizing / saving table /path/xx/ds_temp/dynLUT143294a5578e98

We have enough space (30GB) free, still the problem.
Please Advice.

[ArndW]

You do not have 30Gb free in /path/xx.

[sriramjagannadh]

You do not have 30Gb free in /path/xx. ...

Yes We do have that much memory 30Gb free.

Also checked all the dataset , they were not curropted.

I suspect the lookup stage have some problem.

[kumar_s]

What is the size of cumulative amount of both the files? Hope you might have checked both /path/xx and /path/xx/ds_temp for availablility of space.

[samsuf2002]

try using join instead of lookup stage

[Ultramundane]

If this is AIX I believe that the per-process memory limit for the OSH executable is 512MB. Thus, any lookup stage which attempts to load over 512 MB of memory will abort with an out of space error. However, you can configure the osh executable to use the large memory address by running the following command:

/usr/ccs/bin/ldedit -bmaxdata:0x80000000/dsa osh

[laxmi_etl]

I am having the similar issue on Px 7.5.2.
Anyone has solution for this??

[ray.wurlod]

Yeah, your hardware vendor!

[laxmi_etl]

Sorry I did not get it??

[ray.wurlod]

If you have not got enough space, whether it's memory or disk space, your hardware vendor will be happy to sell you some more space.

Otherwise you must reduce total demand for space. Run fewer processes simultaneously, tune the job designs (buffer sizes, memory limits for sort, for example), add more file systems to your disk and scratchdisk resources.

[sriramjagannadh]

Thanks

Why silly discussion and diverting the topic to hardware vendor

I am looking for real help and want to discuss in this forum ,like sam advised to use Join Stage and any problems with lookupstage in particular

[ray.wurlod]

Simple economics: supply and demand. Either demand fewer resources or supply more. Definitely not "silly" in any sense. There IS a hardware solution.

[Ultramundane]

If this is AIX I believe that the per-process memory limit for the OSH executable is 512MB. Thus, any lookup stage which attempts to load over 512 MB of memory will abort with an out of space error. However, you can configure the osh executable to use the large memory address by running the following command:

/usr/ccs/bin/ldedit -bmaxdata:0x80000000/dsa osh

More memory won't help if OSH is aborting due to lookup stage exceeding 512 MB of memory.

[jgreve]

I wonder if setting these env-vars in your
job would let it run?

Code: Select all

   APT_BUFFERIO_NOMAP=1
   APT_IO_NOMAP=1

The memory-map idea is a great performance
booster, but if your nodes are very busy, there
might not be that much memory available.
Or, as Ultramundane suggested, changing
your kernel settings to have a larger ram-limit
is a good idea.

Disabling memory-mapping is probably
easier, however.
Good luck:
John G.

Thanks

Why silly discussion and diverting the topic to hardware vendor

I am looking for real help and want to discuss in this forum ,like sam advised to use Join Stage and any problems with lookupstage in particular

[elavenil]

We had a similar problem in my earlier project so check the file size limit for the user that is used to execute the job. And lookup table size might have crossed that limit. Solution would be increase the limit for the user and execute the job.

HTWH.

Regards
Saravanan