Lkp_CoverDetail_Ins_Upd,0: Could not map table file "/u03/Datasets/lookuptable.20071219.suos0lb (size 1700927896 bytes)": Not enough space
Lkp_CoverDetail_Ins_Upd,0: Error finalizing / saving table /u04/tmp/dynLUT95869231003dcb
Lkp_CoverDetail_Ins_Upd,0: The runLocally() of the operator failed.
The server configuration is: -
RAM - 16 GB
Disk space -
/u03/Datasets/ - 260 GB
/u04 - 40 GB
4 Processors
. We tried on 2 different servers but the job aborts at the same point. The IBM people are saying that its not a space issue. Can anyone please help in this regard
Thanks & Regards
Parag Saundattikar
Certified for Infosphere DataStage v8.0
There are 40 million plus records comming in. Also I had to use lookup because business wants to use the data of reject link. and hence I had to use lookup stage so that, the reject records will be used by business
Thanks & Regards
Parag Saundattikar
Certified for Infosphere DataStage v8.0
ray.wurlod wrote:The "not enough space" is in /u04/tmp. ...
Hi,
we were monitoring the memory and disk usage while running the job.
What we found out is, The temp file getting created is of 4 GB size, also it created 300 partitions in the disk, but we could not monitor the RAM usage.
Also the problem is if I use a joiner, then to get the reject link data I'll have to use an extra transformer stage and will have to do a left outer join on entire database.
Thanks & Regards
Parag Saundattikar
Certified for Infosphere DataStage v8.0
This looks suspiciously like the problem I was asked to look at yesterday. Was the 2-node APT_CONFIG file that I recommended used, one which cross-mapped the /u03 and /u04 partitions for dataset and scratch directories?
What does "300 partitions on the disk" mean?
Also, why do you say that the job is failing because of insufficient memory? That is not the case and certainly not shown in the log files.