DSXchange

That was the first thing I did.

Then you need to ascertain what changed yesterday. If not the job iteself, then what in the job's environment? Obviously, something did - the hard part can be figuring out what. Another thing could be the data. Is there anything 'unusual' (whatever that means) about that day's data? Especially look...

The job does respond to Stop request as well as reset request. I tried stopping it, then resetting it and then restarted it. Still the same thing. Regarding the structure, the job reads records from a seq file..Does a lookup and couple of transformations. Then writes the output to another set of seq...

chulett wrote:Is the job actually running when you check from the O/S?

Code: Select all

ps -ef |grep phantom |grep -v grep

Does that show any processes that you recognize as coming from your job in question?

Yes. The command shows processes related to this job.

We have a server job which runs daily. Normally it takes approx 7 minutes to complete. But the yesterdays run of this job is still in running state. No warnings whatsoever. We are not accessing any Databases. Only seq files and hash files. All the files required are in place and have the proper righ...

We have a urgent issue in Production...We have 184 million records which have come from source. The size is 18 GB. We want them to be loaded into a hashed file. We have 64BIT Type 30 Hash file. But still after 2Gb it is aborting...Please Help

We already have 64BIT hash file...But once it reaches 2 GB limit the job aborts...If a 64bIT hashed file can hold data in terabytes..why is this happening?. It is TYPE30 file.

I just came to know that the OS is limiting hash file size. But the admin is not ready to increase this limit saying that it may affect other hash files which are fine now...Is this really an issue?

What perplexes me is that when Stage Write Cache is allowed...hash file can only accomodate 2Gb...when it is not allowed it accomodates more than that...I know it is very slow and the rate at which rows gets populated decreases as time passes...but still it does not abort...

Well..I just checked the size of DATA.30 file inside the hash file dir...It has crossed 4GB

I just tried running the same DS job with 'Allow Stage Write Cache' Option unchecked. It was checked earlier when the job aborted.

The job is running fine. Now the point where this job earlier aborted has been passed and the job is still running...

But it is very slow....

Oh! Then we have an issue here. I have to contact Unix admin. He is in the US and myself in India.

I logged in with my own id and executed this command. I am not aware what exactly do you mean by root user?

time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) unlimited
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited

The above is the output of ulimit -a in the directory where my hash file is present

Ok. Now I get your point ArndW. We have DS set up on Unix. Any idea how do we go about checking whether the OS allows this much data...or is it something for the Unix Geeks to answer?