Repairing Exchange 2003 Databases

Check for Clean Shutdown
Run the following commands
    Eseutil /mh priv1.edb
    Eseutil /mh pub1.edb
Check for logs needed. If the report shows Logs Required 0/0 then delete all log files.
Delete *.log
If the shutdown was clean, skip to the defrag section of this FAQ.

OK, so IF the logs required was not 0/0 then lets try and repair the database.  The text in bold that follows are the commands you need to run.

Attempt a Soft Recovery

    Eseutil /r E00

If soft recovery fails, do a hard repair

    Eseutil /p priv1.edb
    Eseutil /p pub1.edb
    Delete *.log
    Mount and then dismount stores one at a time.

OK, by now your transaction logs should all be committed.  Let's move on and defrag the database to free up the space within the database that was being used up by deleted users.

 To ignore streaming file mismatch

• To ignore a streaming file mismatch, add the /I switch to the Eseutil command line. For example:
  
  
  ESEUTIL /P priv1.edb /I
                    

 Streaming File is Missing

If the streaming database has been destroyed, or is missing, you can still successfully complete a repair, but with the loss of all data in that file. If the majority of your users are MAPI clients (Microsoft® Office Outlook® users), the data loss involved may be negligible. If most users connect via Post Office Protocol version 3 (POP3) or Internet Message Access Protocol version 4 (IMAP4), the data loss is likely to be catastrophic.
Follow this step to run Eseutil /P when a database streaming file is missing or when repair is unable to finish with the current streaming file:

 To create a new streaming file

• To create a new streaming file, use the /CREATESTM switch. For example:
  
  
  ESEUTIL /P PRIV1.EDB /CREATESTM

 
http://www.tek-tips.com/faqs.cfm?fid=5581
http://technet.microsoft.com/en-us/library/aa997215%28EXCHG.65%29.aspx