csiemoneit
asked on
eseutil /p: process "deleting unicode fixup table" seems to hang
hello, i have a sinlge exchange server 2003 sp2, the database size of priv1.1 edb is 65 gb.
we had to run a repair, at the first try the process "deleting unicode fixup table abused" at the end of the repair-process aborted with the error "process aborted with failure -1808, no free disk space". i then started a second try with the parameter /tx:\path, where x: is a mounted network share with 100 gb free disk-space. now the "deleting unicode fixup table abused"-process seems to hang, there seems to be no progress since five hours. how many hours can this progress take? should i abort the process and try again? or should i wait? are there any ways to check, if the process ist still working or if it hangs indeed?tia
we had to run a repair, at the first try the process "deleting unicode fixup table abused" at the end of the repair-process aborted with the error "process aborted with failure -1808, no free disk space". i then started a second try with the parameter /tx:\path, where x: is a mounted network share with 100 gb free disk-space. now the "deleting unicode fixup table abused"-process seems to hang, there seems to be no progress since five hours. how many hours can this progress take? should i abort the process and try again? or should i wait? are there any ways to check, if the process ist still working or if it hangs indeed?tia
This is the longest part of the process and I would let it run, A really big Exchange Database can take several hours to run. Get lunch and come back to it.
leave it over night that can take ages especially if it is going across the network.
local disk is always better.
if it times out or fails or hangs or anything like that it will give you an error ALWAYS
local disk is always better.
if it times out or fails or hangs or anything like that it will give you an error ALWAYS
Microsoft also states that running eseutil /p can take anywhere between 1 to 10 GB an hour based on corruption so you are still within range. I would expect the process to take 8 -10 hours for /P another 4 hours for the eseutil /d and 30 -60 minutes for the isinteg -s SERVERNAME -fix -test alltests
I have done a 125 gb database that took over 24 hours for the /p
I have done a 125 gb database that took over 24 hours for the /p
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.