Posted by Bob A on November 19, 2010 at 09:03:48:
got a 9A when reading the largest file we have (5,071,488KB for the data and 1,963,921KB for the index/.I00)
this was on a stand alone TEST system which is periodically refreshed
1) one of the utilities said it couldn't help because this file had extended keys... really don't think so since it's way too old for that (how do I verify?)
2) checking FSTAT$ returns a size of 4 gig (@FFFFFFFF@) is there any other place I can look in FSTAT$ to find the real size from within COMET?)
3) if I have to do a KEYBLD.... should I specify Extended Keys even though some of my utilities won't work when I do this?
4) is the most useful way to deal with this to wait until the next REFRESH and hope that the problem was not just a result of the last copy?
we're in the process of scoping out stripping this file of old data (the program that got the 9A was just INQUIRE-ing to gauge how many records we have during each of the various years in the past)
I can't imaging how many hours/days it would take to run KEYBLD with so many records.
Thanx
Bob "A"
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.