v.X can't rebuild database: not enough space?!?

G

Grant Dotson

I have a Mac running 10.3 with Office v.X. Recently, I received an
error that the database could not be accessed, and advising me to
perform a typical rebuild. The typical rebuild would not run, so I
went straight to the advanced rebuild, which finished successfully and
then advised me to run a typical rebuild. When I tried to run that, I
was given a message that said the rebuild could not run because I did
not have enough free space available. But I should have plenty.

Here are the details:

1 GHz PowerBook w/ 512 MB RAM
24 GB of available disk space
3 GB Office database (lots of 2-4 MB attachments, cleaned out every 2
months)

So I figure even if Entourage had to replicate my database twice or
even three times in one sitting to rebuild it, there should still be
plenty of space left over.

Any one have any ideas?

Thanks!
 
B

Barry Wainwright

I have a Mac running 10.3 with Office v.X. Recently, I received an
error that the database could not be accessed, and advising me to
perform a typical rebuild. The typical rebuild would not run, so I
went straight to the advanced rebuild, which finished successfully and
then advised me to run a typical rebuild. When I tried to run that, I
was given a message that said the rebuild could not run because I did
not have enough free space available. But I should have plenty.

Here are the details:

1 GHz PowerBook w/ 512 MB RAM
24 GB of available disk space
3 GB Office database (lots of 2-4 MB attachments, cleaned out every 2
months)

So I figure even if Entourage had to replicate my database twice or
even three times in one sitting to rebuild it, there should still be
plenty of space left over.

Any one have any ideas?

Thanks!
Click to expand...

Entourage does need up to 3 time the size of the database in free space *on
the startup disk*, even if the MUD folder or identity files are on a
separate partition.

If you have partitioned the disk in your PB, you could be falling foul of a
bug where vX only checks free space on the startup disk. If so, you may be
able to get round this by creating a unix-style 'symbolic link' to a remote
directory rather than relying on Finder's aliases.

If this is not the case, it is possible that the corruption in the database
is too severe for the rebuild engine to cope with.
 
Top