mihirnayak -> RE: Help to resolve this issue (ESE 467) (3.Aug.2011 3:02:09 AM)
|
Hi , 467 is very imp alert to DB and we can't ignore it. However, if there are corruption errors either at the page or database level that are in addition to index page corruption, it may not be sufficient to use eseutil /d. There may be some cases in which, as a last resort, you will need to repair the database using eseutil /p, then Isinteg -fix. In this case, after running eseutil /p and Isinteg -fix, you will need to use ExMerge to rebuild the database before putting the database back into production. Once you have done that, immediately perform an online Exchange-aware backup of the database
|
|
|
|