Hello

I get status 100 when trying to rebuild large file
(either from server console or from workstation)

Server is Win2003 with PVSW 8.6 - 1.8GB RAM cache allocated for Pervasive.
File is 3 segment (2+2+1=5GB).

This file used to rebuild without a problem under Novell server (1.5GB RAM).

This happens either using GUI utility or rbldcli from command line.

Thanks in advance
Przem

PS. Exact error message:
The rebuild operation start time is 06/23/05 12:00:03.
rbldcli -c -s -f8 -bY:\gm1 Y:\GM\GMPODO4.DAT
REBUILD-20: The utility is processing Y:\GM\GMPODO4.DAT.
REBUILD-68: Status code 100 was returned while copying records from the
following file:
Y:\gm1\_rblda00876.
REBUILD rejected a total of 8629800 records.
REBUILD copied a total of 993203 records.
REBUILD rebuilt a total of 0 indexes.
The rebuild operation end time is 06/23/05 12:13:44.

The cache size is probably set too high.
Under Win2003 the OS only allows a total address space of 2GB* for an
application (no matter how much physical memory is installed). 1.8GB
for Cache does not leave very much for "every else" the database
engine may need, especially if you have raised the threads which the
OS reserves 1MB EACH for stack space.

To see if this is indeed the issue, check the pvsw.log in the windows
directory, it will probably have memory allocation errors at the same
time as the status 100.
You can also monitor Perfmon -> Process -> ntdbsmgr.exe -> Virtual
Bytes. When it hits 2GB (2147483648 bytes) bad things typically
happen.

To "fix" this, just lower the cache size and or thread settings.

* On certain versions of Windows "enterprise" versions under certain
circumstances allow the setting of the "/3GB" boot.ini switch. This
would allow the database engine to have up to 3GB of address space
allocated. For details check with the OS vendor.

Leonard

On 23 Jun 2005 05:57:27 -0700, przemm (AT) poczta (DOT) onet.pl (Przem) wrote:

Thank you Leonard,
I'll try this

Przem

Leonard <lharvey (AT) austin (DOT) rr.com> wrote