Corrupt Key and Data Segment...lengths do not match

[Jeff Harrison]

----- Original Message -----

> From: Brad Weaver <bweaver at compuaid.com>
> To: 'filePro Mailing List' <filepro-list at lists.celestial.com>
> Cc: 
> Sent: Wednesday, November 9, 2011 11:03 AM
> Subject: Corrupt Key and Data Segment...lengths do not match
> 
> 
> 
> I have a client who today decided to modify a field length.  Naturally, he
> killed the lockfile and just went right in not checking to see if all other
> users were out.  They weren't.  He modified the file then chose to shrink
> the key and data segments.  While that was happening another user was still
> in and the file got corrupted.  I've done a lot of research through the
> newsgroup and I haven't found much positive to tell my customer.  To make
> matters worse his backups have not been running since May.  Is there any way
> to access the data for recovery?  I've been able to build a map of the key
> in a new file called KEYONLY and move the key file over and see it but I
> can't do the same with the Data file.  Since the two files have different
> numbers of records now I'm not even sure how I'd match up the two 
> segments
> even if I could retrieve them both separately and then import them back to a
> new combined file.
> 
> Suggestions are MOST welcome!
> 
> Brad Weaver
> President
> 

Try creating a filepro file that is a "non-filepro" file and map it to the data segment.  You may need to play around with the map to get it to the right record length.  If no-one has added records since the corruption you should be able to match up the new file for the key with the file for the data on a record number basis.  That is, record #1,2,3 etc. in your key file should match record #1,2,3 etc. in the file mapped to the data segment.

Good Luck.

Jeff Harrison
jeffaharrison at yahoo.com
Author of JHExport and JHImport