Unfortunately I don't have the time to grab it and debug it, and am instead
going to figure out an alternate way of storing the binary data so IB
doesn't get anywhere close to what appears to be a 180GB limit on NT 4 (and
a bit higher presumably on Win2k).


Thanks to you and Sean for helping me to try to figure out what was going on
with it.


Bill

-----Original Message-----
From: Ann W. Harrison [mailto:aharrison@...]
Sent: Thursday, December 06, 2001 8:16 AM
To: ib-support@yahoogroups.com
Subject: RE: [ib-support] RC1 Error - Responses

>At 04:40 PM 05-12-01 -0800, Bill Morrison wrote:
> >... read in the first 300kb from each of
> >those files. This spikes nicely, and causes the Kernel memory to jump to
> >152mb, but it still succeeds.
> >
> >It seems like there is a piece of the puzzle missing somewhere . . .

At 12:21 PM 12/6/2001 +1100, Helen Borrie wrote:

>You probably did it already, but... does (DATABASE_CACHE_PAGES *
>page_size) come out greater than SERVER_WORKING_SIZE_MAX?

If the command line gstat -h fails to open the database, we can
eliminate all of the server parameters. Gstat does its own
open and with the -h, never calls the server. If it were my
problem, and gstat -h failed, I'd build a debugging gstat and
walk through it. Confusingly, gstat is built from a source
component called utilities and uses the files dba.e & ppc.c
plus a great many of the header files from jrd.

Regards,

Ann



To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/