There should be a rszxxxxx (where xxxxxx is some temp file unique Unidata name) file in whatever directory you have defined for TMP (if this is UNIX, do !echo $TMP) that should be the file after it was resized. I am guessing that the memresize got interrupted right at the point where Unidata was copying the rszxxxx file over the top of your TEMP file. I would set up a temporary VOC pointer to the rszxxxx file and see if it looks like the info that you expect to find in TEMP. - Rod
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Butera Sent: Wednesday, April 15, 2009 5:47 AM To: [email protected] Subject: [U2] Unidata File Corruption Unidat a 7.1.8 on Solaris 9. I have a file that was mistakenly interrupted during a memresize. Now I if I try LIST, SELECT or guide I get: File size(16908288) is < minimum hash file size, blocksize(8192) * (modulo(5147) + 1). TEMP is not a UniData data file TM failed to open file 'TEMP'. I assume at this point I'm SOL. Anyone have other ideas? I have backups and only appear to have 31 records added since the backup was created, but any insight as to how I might recover data would be appreciated. Jeff Butera, Ph.D. Administrative Systems Hampshire College [email protected] 413-559-5556 "Dad, you're talking in grown-up and need to stop." Catherine Butera ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
