file too large

[scooter6 at gmail.com]

  Well, there are over 8 million records in this file - so I was looking for
a bit quicker of a solution to get this resolved
  I can't wait to get this system on a CentOS server - SCO is soooooo dang
slow haha
  I'm currently looking to export the records to a few csv files, then
delete key & data for this file and import only the most
  recent 6 months or so and then resolve the rest when I get back next week
from vacation....
  Why do these things happen the day before I'm leaving town? haha

  So, to clarify - is this a SCO OpenServer 5.0.5 issue, or is this a
filePro error? Meaning, if I upgrade tonight to 5.6.10 would this
  resolve the issue?




On Thu, Feb 3, 2011 at 4:38 PM, Jeff Harrison <jeffaharrison at yahoo.com>wrote:

>  ----- Original Message ----
>
> > From: "scooter6 at gmail.com" <scooter6 at gmail.com>
> > To: filePro Mailing List <filepro-list at lists.celestial.com>
> > Sent: Thu, February 3, 2011 4:13:05 PM
> > Subject: file too large
> >
> > We have a note line file that has apparently surpassed the 2GB size on
>  SCO
> > OpenServer 5.0.5 running filePro 5.6.07R4
> > A lot of users got stuck  recording new records to this file, so I got
> them
> > all off the system and  tried adding a record and I'm getting
> >
> > ..../appl/filepro/filename:   key  file too large
> >
> > We had previously run an archive on this file,  but I know filePro won't
> > actually 'shrink' the file size reported on the file  system.
> >
> > Are there any utilties that will 'shrink' this file below the 2GB  size
> limit
> > by 'removing blank records' ?
> >
> > So much for my vacation that  was supposed to start tomorrow........
>  uggghh
> >
> >
> >
> > Scott
>
> If your blank records are actually deleted records, then yes there are a
> number
> of utilities that can shrink your file.  You can also do this yourself -
> just
> archive all the remaining records to another (new) file (or qualifier in
> the
> same file), and then from the OS just copy the key file back on top of the
> original key.  Do the same for any other data segments that may exist.
>  Then
> rebuild all of your indexes in the original file and you should be all set.
>
> One possible "gotcha" - sometimes people actually use the record numbers as
> pointers - I assume you are not doing that?
>
> Going forward you may want to set up a periodic archive so this does not
> happen
> again.
>
> Good Luck.
>
> Jeff Harrison
> Author of JHExport and JHImport.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20110203/24535382/attachment.html