error writing into hash file..

scottr · Post by **scottr** » Wed Jan 05, 2005 9:41 am

I know there are similar posts ,but pl have a look at this one.
these are 50 warngings
PT_RPOS_Lookup.LdLookup: ds_uvput() - Write failed for record id '92612921'
PT_RPOS_Lookup.LdLookup: ds_uvput() - Write failed for record id '92453581'

and the below is the message after
Attempting to Cleanup after ABORT raised in stage

DataStage Job 482 Phantom 11440
Program "DSD.StageRun": Line 571, Internal data error.
Program "DSD.StageRun": Line 571, Internal data error.
PT_RPOS_Lookup2003andup/DATA.30':
Computed blink of 0x830 does not match expected blink of 0x0!
Detected within group starting at address 0x90603000!
PT_RPOS_Lookup2003andup/DATA.30':
Computed blink of 0x830 does not match expected blink of 0x0!
Detected within group starting at address 0x89C27800!

does any one has advise for me like what's happend here.

kcbland · Post by **kcbland** » Wed Jan 05, 2005 9:50 am

You've corrupted the hash file, probably because you exceeded 2.2 gigabytes on a 32bit file. You could have also ran out of disk space.

scottr · Post by **scottr** » Wed Jan 05, 2005 10:06 am

i think ur correct it has 2434850816 on data.30 and 586504192 on over.30
how to correct it.i have to delete the old one and create new one. or else how to increase the size of old hash file..

thanks

kcbland · Post by **kcbland** » Wed Jan 05, 2005 10:19 am

First of all, are you attempting to put 500 million rows into a hash file? If so, you better contemplate a better solution. Just figure out how much raw character storage is required: 500 million rows of 20 characters per row puts you at 1 TB.

Hash files can hold that, but is it the solution I think you're looking to find? Based on your other post, I believe you are working on your data correction problem.

To directly answer your question, search the forum for "64BIT" hash files. That should get you past the 32BIT limitation. But, you'll be loading that hash file for days or weeks.

scottr · Post by **scottr** » Wed Jan 05, 2005 10:26 am

hi,
both are different problems.this one is a daily job loads around 150k recs into the hash file.and it has been running for a couple of months.now it is oversized and correpted.so switching 64bit is the only option??

kcbland · Post by **kcbland** » Wed Jan 05, 2005 10:28 am

You are attempting to fit 11 pounds of apples into a 10 pound apple box. Either remove unnecessary columns from the hash file to relieve the amount of data going into the file, or switch to creating it as 64BIT. There is a hard ceiling on 32BIT files, there's no way to squeeze more into that container. 2.2 gigabytes is it.

scottr · Post by **scottr** » Wed Jan 05, 2005 10:34 am

thanks a lot Kenneth Bland

T42 · Post by **T42** » Wed Jan 05, 2005 9:56 pm

Also keep in mind: HASH FILES ARE NOT A PERMANENT STORAGE SOLUTION! It's the same with Datasets for EE. They are to be used as a temporary storage for efficient processing down the stream.