Eseutil /p on 65gb priv1.edb and 16gb priv.stm taking more than 9 hours or how long ?

navedj786
navedj786 used Ask the Experts™
on
I have been trying to repair the database with the eseutil /p command it's been about 12 hours and it's stuck on "deleting unicode fixup table"

Even i want to view the log file how can i view it ? and i have a space on the same drive for about 82gb and have made more just now. please advise


D:\Exchsrvr\MDBDATA>eseutil/p priv1.edb

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating REPAIR mode...
        Database: priv1.edb
  Streaming File: priv1.STM
  Temp. Database: TEMPREPAIR3256.EDB

Checking database integrity.

The database is not up-to-date. This operation may find that
this database is corrupt because data from the log files has
yet to be placed in the database.

To ensure the database is up-to-date please use the 'Recovery' operation.


                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |----|----|----|----|----|----|----|----|----|----|
          ...................................................


Scanning the database.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |----|----|----|----|----|----|----|----|----|----|
          ...................................................


Repairing damaged tables.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |----|----|----|----|----|----|----|----|----|----|
          ............
Deleting unicode fixup table.
.............

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Deleting unicode fixup table takes a long time if there is more corruption in the database.
http://support.microsoft.com/default.aspx/kb/259851 where you can see that the speed is 6-5 GB per hour.

Author

Commented:
thanks anyhow it got fixed after 17hrs however i want to know how can i check the log file as mentioned in my question what tables was corrupted and what was recovered. Moreover there was temp.edb file created while this process was going on but i can't see it now.
I have tried fixing it and have did it. once you repair the priv.edb with the eseutil command it takes approximately 15 to 24 hrs for a 81gb once the database is repaired you should backup it on a backup tape and then remove all the files from the mdbdata keeping only the following :

e00.chk
res1
res2

& all the .edb & .stm files

then start the store and it will mount and you'll start receiving the email

if you wish and have more time you can restore the backed up data on other computer and run the defrag to align the database even.
Manpreet SIngh KhatraSolutions Architect, Project Lead
Top Expert 2013

Commented:
Hi Naved good to hear the issue resolved but if you really want to knwo about the process let me know ..... i would be good to share the information that you would want .... :) :)

Author

Commented:
Thanks Rancy i'll coordinate any issues in the future with you definetly.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial