Microsoft KB Archive/261947

= How to determine if hard repair (Eseutil /p) has been run on a database =

Article ID: 261947

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Standard Edition

-



This article was previously published under Q261947



SUMMARY
This article describes how to determine if your database has been repaired by using the Eseutil /p command.



MORE INFORMATION
To see if your database has been repaired by using the Eseutil /p command, dump the header using one of the following commands for the private information store:

ESEUTIL /mh x:\exchsrvr\mdbdata\priv.edb |more

-or-

ESEUTIL /mh x:\exchsrvr\mdbdata\pub.edb |more

The output looks similar to the following example:

Microsoft(R) Windows NT(TM) Server Database Utilities

Version 5.5

Copyright (C) Microsoft Corporation 1991-1999. All Rights Reserved.

Initiating FILE DUMP mode...

Database: d:\exchsrvr\mdbdata\priv.edb

Format ulMagic: 0x89abcdef

Engine ulMagic: 0x89abcdef

Format ulVersion: 0x620,2

Engine ulVersion: 0x620,2

DB Signature: Create time:4/5/2000 17:48:52 Rand:769046 Computer:

cbDbPage: 4096

dbtime: 556457

State: Consistent

Shadowed: Yes

Last Objid: 184

Scrub Dbtime: 0

Scrub Date: 00/00/1900 00:00:00

Repair Count: 1

Repair Date: 2/20/2000 10:48:50

If the database has not been repaired, the repair count is zero and the repair date is 1/1/1900 00:00.

Note If you run the Eseutil /p on a database that is not damaged or on a database that is damaged on a page that does not contain data (may contain only white space), the repair count is not incremented. The Repair Count=0 output indicates that no repairs have been made to the database, even if Eseutil /p has been run.

Additional query words: XADM

Keywords: kbhowto KB261947

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.