RESIZE issue for hashed file

ray.wurlod · Post by **ray.wurlod** » Thu Sep 21, 2006 5:03 am

You were too late. You had to resize it before it reached 2GB. Now it is in a corrupted state, so that must be fixed first.

If you can afford the time to reload the hashed file completely, the quickest way is to clear the hashed file, then resize it while empty.

Otherwise, those backward link errors will need to be repaired, which is a specialized activity. Your support provider may have the skills, but repairing damaged hashed files is chargeable.

ray.wurlod · Post by **ray.wurlod** » Thu Sep 21, 2006 3:24 pm

Resizing the dictionary portion of the hashed file for 64-bit addressing is a complete waste of time. Yet this is what you've done. The file dictionary, in which metadata is stored, will never get anywhere near 2GB.

You have to resize the data portion of the hashed file. It is the data portion that is corrupted, so you will need to clear it first, as observed earlier.

Incidentally, the word USING does not appear in the syntax you reported. I assume this is a transcription error.