On 1/30/02 8:20 AM, "Jim Robertson" <[EMAIL PROTECTED]> wrote:
> Based on all the kind advice I've received from you and Diane, I set myself > up to emerge from my corrupted database woes. I opened Entourage using the > corrupted database, then made mbox files (folder by folder) of the messages > I wanted to save that had been sent or received since 12/9 (the date to > which an advanced rebuild had truncated my database). > > Then, I opened the rebuilt database I've been using since I discovered my > problem on 12/26 because Entourage refused to open. This database was > created by doing an advanced rebuild on the one that failed basic rebuild. > I've been using it since the advanced rebuild, but leaving a copy of every > message I receive on my ISP's server, "just in case" :-) > > Just to make sure I was OK, I decided to do a rebuild on my NEW database > before importing the mbox files. Guess what? IT FAILS the rebuild! > > The pattern is the same as previously. Compaction stops before the progress > bar reaches the high message counter, and optimization gets almost to the > end of its counter before telling me the database cannot be rebuilt. > > What I plan to do now is make backup copies of my NEW flawed database, > rebuild it (advanced rebuild), and, if it survives that, try rebuilding it > AGAIN before I do anything else with it. > > Does anyone think the problem could lie outside Entourage; e.g., OS X > directory problems, etc.? Any suggestions what I should try if I rebuild the > current database and find that it's not OK immediately after being rebuilt? Two questions: how big is your database file, and do you have enough disk space where your MUD folder is to make a copy of it? The first thing that pops into my mind is that it is a problem actually writing the database due to size constraints. The Entourage database does have a limit of 2Gig. It's huge, but there are people who have run into serious problems when they got that big (couldn't read anything). The database rebuild makes a new copy of the database leaving the old one, as you are probably aware. If you don't have enough disk space to write the new one, this may cause it to fail. Other than that, I don't know of any reason why OS X would interfere with it. Maybe you should save ALL of your messages as mbox files and then create a whole new identity with a fresh database, or wipe out your current entourage and MUD and reinstall a clean one. Then try to import the messages into a completely clean identity. At the very least, you will end up with the mbox files, which can be read as simple text or maybe even by the OS X Mail application. One final thought about the database. Someone mentioned this in another thread. If you throw out or overwrite the MUD file by copying a database into it, you should make sure the background application "microsoft database daemon" is not running. This loads automatically when you login or startup OS X. You can disable it in the OS X System Prefs/Login/Startup Items and restart. Just remember to set it back up after you are done copying. Or even easier, if you are unix savy at all, go into your terminal, find the process number for this app (type 'ps aux' to list all processes running) and kill it (type 'kill -9 process#'). --Greg -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
