Exchange 2010 Public Database Corrupt, Errors in Event Log, but functional? How to repair?

1st I encountered this.................................................................
Log Name:      Application
Source:        ESE
Date:          6/4/2013 8:00:34 PM
Event ID:      447
Task Category: Database Corruption
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
Information Store (7992) PublicDatabase: A bad page link (error -327) has been detected in a B-Tree (ObjectId: 45, PgnoRoot: 108) of database D:\Program Files\Microsoft\Exchange Servier\V14\Mailbox\Public Folder Database 0162114069\Public Folder Database 0162114069.edb (8516 => 8517, 0). 

Open in new window


Then I saw this................................................................................
Log Name:      Application
Source:        ExchangeStoreDB
Date:          6/4/2013 8:00:35 PM
Event ID:      209
Task Category: Database recovery
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
At '6/4/2013 8:00:34 PM' the Exchange store database 'PublicDatabase' copy on this server detected corruption on the active copy of the database. To help identify the specific failure, consult the Event log on the server for other storage and "ExchangeStoreDb" events.  Service recovery was attempted by failover to another copy, which was unsuccessful in restoring the service. Error: There is only one copy of this mailbox database (PublicDatabase). Automatic recovery is not available.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ExchangeStoreDB" />
    <EventID Qualifiers="49156">209</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-06-05T00:00:35.000000000Z" />
    <EventRecordID>880803</EventRecordID>
    <Channel>Application</Channel>
    <Computer>
    <Security />
  </System>
  <EventData>
    <Data>PublicDatabase</Data>
    <Data>4908c384-4e23-41c0-9af3-7f0546c95924</Data>
    <Data>Ese</Data>
    <Data>Corruption</Data>
    <Data>PublicDatabase</Data>
    <Data>
    </Data>
    <Data>There is only one copy of this mailbox database (PublicDatabase). Automatic recovery is not available.</Data>
    <Data>6/4/2013 8:00:34 PM</Data>
    <Data>None</Data>
    <Data>D:\Program Files\Microsoft\Exchange Servier\V14\Mailbox\Public Folder Database 0162114069\Public Folder Database 0162114069.edb</Data>
    <Data>0</Data>
    <Data>0</Data>
  </EventData>
</Event>

Open in new window


Then I ran a database repair request and found this.............................
Log Name:      Application
Source:        MSExchangeIS Public Store
Date:          6/4/2013 7:43:32 PM
Event ID:      10063
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:    
Description:
Corruption(s) detected during online integrity check for request dadde4ac-fc14-4365-a82f-db3adfe36cf7 
Database:Public Folder Database 0162114069 
Table:ReplState 
Corruption	Is Fixed	FID	Property	Resolution 
Public Folder Replication State, Yes, 1-FFFFFFFF0000, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, 2-FFFFFFFF0003, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, 6-16, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, 6-18, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, 6-A6907, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, d-114D8, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, d-114D9, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, d-7012F, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, d-145331, 0x66980102, Remove mismatched replication state entries

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeIS Public Store" />
    <EventID Qualifiers="16390">10063</EventID>
    <Level>4</Level>
    <Task>6</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-06-04T23:43:32.000000000Z" />
    <EventRecordID>879960</EventRecordID>
    <Channel>Application</Channel>
    <Co
    <Security />
  </System>
  <EventData>
    <Data>dadde4ac-fc14-4365-a82f-db3adfe36cf7</Data>
    <Data>Public Folder Database 0162114069</Data>
    <Data>ReplState</Data>
    <Data>Public Folder Replication State, Yes, 1-FFFFFFFF0000, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, 2-FFFFFFFF0003, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, 6-16, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, 6-18, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, 6-A6907, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, d-114D8, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, d-114D9, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, d-7012F, 0x66980102, Remove mismatched replication state entries
Public Folder Replication State, Yes, d-145331, 0x66980102, Remove mismatched replication state entries
</Data>
  </EventData>
</Event>

Open in new window


Still getting errors though. Any Ideas??
tcssupportAsked:
Who is Participating?
 
tcssupportConnect With a Mentor Author Commented:
The system is up and running ok, I just see the errors above. Should I even attempt repairs?
0
 
strivoliConnect With a Mentor Commented:
Eseutil is the tool used for Database Recovery and this link should help.
0
 
strivoliConnect With a Mentor Commented:
You can run eseutil to check the database without making any change (fresh full backups are ALWAYS strongly suggested, anyway). After the check is over, take a close look at the results and post them and/or decide by yourself to proceed or not with a repair.
A periodic check using eseutil on all databases is part of the Best Practices.
0
 
colin_PaulCommented:
Hello Tcssupport,

Please checked if the databases are in a dirty shutdown state or clean state?

Open command prompt and do the following:-
Navigate to the directory where you EDB database is located...

eseutil /mh <databasename.edb>

Look for "State" if it is Dirty Shutdown then you will need to repair this database before you can bring it back online (mount).

If the shutdown is Dirty do the following...

eseutil /r /l <databaseLogs> /d <database edb location>

If using the /r switch does not work you can then use the /p switch will usually get it to a clean shutdown state.

eseutil /p <DatabaseName>

Once you have done this you can then check the state again using the eseutil /mh <databasename.edb>

Once the state is a "clean shutdown state" you can then re-mount the database to Exchange.

Take a look at the following link for additional details...
http://blog.pluralsight.com/eseutil-exchange-2010

Please refer following articles to resolve issue.
1. http://technet.microsoft.com/en-us/library/bb123587(v=exchg.141).aspx
2. http://support.microsoft.com/kb/976066
3. http://technet.microsoft.com/en-us/library/aa995829(v=EXCHG.65).aspx


Thanks
Colin Paul
0
 
tcssupportAuthor Commented:
post created by ex employee
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.