Wierd Error -- Phantom 29287

Vinodanand · Post by **Vinodanand** » Wed Sep 12, 2007 7:13 am

Hi,

I got the following error when there was an attempt to read the Hash File.there was no change done to the jobs.Please advise.

I am not sure what this error means though.Any clues.I did check the Phantom and the line number points to a stage variable where the Keys are built.

Thanks for your help.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
Program "JOB.1914151762.DT.1433475379.TRANS1": Line 524, Internal data error.
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x807F7800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x807F9000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x807F3000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x80800000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x807F4800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x807FA800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x807F1800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x807FC800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x806D6000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x806DF000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x806D3000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x806D9800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x806DA800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x80E2A800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x80E24800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x80E30000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x80E23000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x80E21000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA4C does not match expected blink of 0x0!
Detected within group starting at address 0x80D91800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x80D9A800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x80D94800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA4C does not match expected blink of 0x0!
Detected within group starting at address 0x80D9F000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA4C does not match expected blink of 0x0!
Detected within group starting at address 0x80D9D000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x807FA800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x807F4800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x80800000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA80 does not match expected blink of 0x0!
Detected within group starting at address 0x807F3000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x807F0800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x80298800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x80298000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x8029E000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x80292000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x80294000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x80156800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x8015C800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x80150800!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!
Detected within group starting at address 0x8015C000!
File '/dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187/DATA.30':
Computed blink of 0xA50 does not match expected blink of 0x0!

Regards,
Vinod

chulett · Post by **chulett** » Wed Sep 12, 2007 7:33 am

Your hashed file is corrupted. Search the forums for 'computed blink' to find several conversations on what a 'backwards link' is and how it got horked up. Typically your 32bit hashed file exceeded the 2.2GB boundary and needs to be 64bit...

Vinodanand · Post by **Vinodanand** » Wed Sep 12, 2007 7:47 am

Hi,

If that is the Case should it not fail while data is written to the Hash File.I computed the size by taking the data.30 size in bytes which is 2136631296 bytes. Should I include the overflow size too

Regards,
Vinod

ArndW · Post by **ArndW** » Wed Sep 12, 2007 3:27 pm

As Craig has stated, the file is corrupted and needs to be repaired or, failing that, cleared out. The blink errors denote internal corruption. Sometimes files with blink errors in some groups allow adding data into other groups, so the error won't always manifest itself on writes.

Quickest fix is a CLEAR.FILE, but you can try to repair it with UVFIXFILE or FIXTOOL.

Vinodanand · Post by **Vinodanand** » Wed Sep 12, 2007 4:17 pm

ArndW wrote:As Craig has stated, the file is corrupted and needs to be repaired or, failing that, cleared out. The blink errors denote internal corruption. Sometimes files with blink errors in some groups allow adding data into other groups, so the error won't always manifest itself on writes.

Quickest fix is a CLEAR.FILE, but you can try to repair it with UVFIXFILE or FIXTOOL.

Thanks Arnd I deleted the file and recreated the Hashed file as 64 bit using the parameters of HFC.

But for 2.8 million records below is teh command I used to create

mkdbfile /dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_14187 30 1140457 4 20 20 80 1628 -64BIT

but it took close to 5 hrs to write to this hashed file and I am sure that reading would be slow. I have 68 columns in the Hashed file and my key is 24 bytes. Please help.

Regards,
Vinod

ArndW · Post by **ArndW** » Wed Sep 12, 2007 5:36 pm

Didn't we go through a similar performance thread on this file recently? If you do an ANALYZE.FILE on this file (you might need to use SETFILE to set up a VOC pointer to the file) what is the modulo after filling up the file - is it close to your 1,140,457 minimum? What percentage fill do you have?

If you work out how many Kb/second you achieve while writing to this file how does it compare to write speeds to other files? Write speeds are not necessarily indicative of read speeds.

Also, if you know (approximately) what you maximum file size is going to be, it might be best and most efficient to use a static hashed file in this case.

Vinodanand · Post by **Vinodanand** » Wed Sep 12, 2007 7:47 pm

Hi Arnd,

We did go through the same issue last time and it is still not resolved,but I managed to tune the parameters so that the job writes to the Hashed file in 1 hr but it stilll takes close to 4 hrs to read from it.I tried using a Static file too but the result was not as expected.Let me analyze the file and post the details.Thanks for your help.

Vinod

Vinodanand · Post by **Vinodanand** » Thu Sep 13, 2007 6:58 am

Hi ,

I am closing this topic and am continuing the same with already existing topic viewtopic.php?t=112399&postdays=0&postorder=asc&start=0

Thanks,
Vinod