Likely what has happened is that the RESIZE set the "active resize" bits for the records which were copied to the temp file. The good news is that this is an easy fix, maybe. At the UNIX prompt run "filepeek FILENAME". Then use the "rcl" command to clear the active resize bits. When this completes try to access the file -- my bet is that you will be able to. Remove the resizexxxx file that the RESIZE created and you should be home free.
Hope this helps! Jeff Fitzgerald Fitzgerald & Long, Inc. www.fitzlong.com > > From: "Andrew Gissing" <[EMAIL PROTECTED]> > Date: 2004/09/22 Wed AM 03:35:47 EDT > To: <[EMAIL PROTECTED]> > Subject: [U2] Help - clobbered file ! > > I made two stupid errors today - one, typing in a command that caused a > RESIZE on a live file... and two.. doing a kill -9 on the resize process. > > Thanks to an online backup of this file, we're up and running with a copy > from last night. > > What i'm now trying to do is see if there have been any changes to this file > since last night. The sort of file it is I expect some. It's more or less a > static file with a handful of updates during each day. It's not a heavy > transaction file. We don't have logging or transaction logs or such. > > Where I am: > > I've got a copy of the file immediately after the aborted resize. > > I can list it and select it, but I can't ED or CT - it's as if there is a > record lock - but there is none. From TCL my screen freezes but I can still > control-backslash out. > > I've made a unix copy of the file and tried same.. and also done a uvfixfile > which reports: > > ------------------------------------------------ > >UVFIXFILE DRVR-ag > > Beginning TRACE of DRVR-ag. > TRACE of DRVR-ag completed. > > Scanning overflow buffers. > Scan complete. > > 531 group(s) processed. > 655 group buffer(s) processed. > 1076 record(s) processed. > Number of data bytes = 756796. > ------------------------------------------------- > > At unix level the file is reported as being 1345536 bytes - so it's only > processing 1/2 the file ? However it could be oversized ? > > Any pointers on how to go about accessing the 1076 records in thsi file > would be great. I'm already doing the manual one by checking with users. > 1076 by the way is the expected number of records - so it doesn't look like > we've lost any. > > > > Thanks in advance, > > > > Andrew Gissing > ------- > 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/
