Repeated database corruption under SP2

[Terry]

I have a large Entourage database (about 4.2 GB), and it keeps getting
corrupted. Yesterday, I formatted the drive (80 GB PowerBook), and did a
clean install of 10.3.9, and Office 2004, SP2. I had upgraded to SP2 prior
to noticing the problem, and since SP2 changes the database structure, going
back to SP1 is not an option. My seemingly intact backup from about 2 weeks
ago is already in the SP2 format.

After restoring from the backup, things are OK for a while, but then the
error messages start ("Could not open that feature. An I/O error occurred."
is a common one). Once I get to this point (last time, this only took about
8 hours), the Database Utility can't save the file; it also reports an I/O
error. (I've only used the advanced rebuild, not the "basic"). I've run
Disk Utility to repair permissions, but this had no effect.

Are there known problems with SP2 and large databases? Any suggestions on
how to move forward? Right now, I'm stuck with a two-week-old backup, and
can't get Entourage to run for a full day without corrupting the DB.

Terry

 

[Brad]

Terry,

I've had a similiar problem, ever since I rebuilt my database after
installing SP2, I have been unable to open the database & the database
is split into "database" and "old database." MS is currently working on
an update to SP2 & they say it'll be out at the end of the month -- I
hope that'll fix our problems!

I would recommend backing up your database into an archive.

Good luck!

Brad

 

[spuriousgrowth]

Hi Terry,

Report of an IO error sounds very much like your hard disk is showing
signs of physical error. Repairing permissions, fsck or repairing the
filesystem will not fix this problem, but will fix filesystem errors
that occur as a result of your disk going bad. Other symptoms of this
are frequent long periods of spining beach ball where all applications
appear to be functioning but unresponsive. Of course, if you are unable
to validate this yourself seek expert advice. and back up anything
important, as it seems you have already done.

Jake