Database Corruption Error: A Bad Page Link in B-Tree - HELP!
Posted on 2006-06-01
Today I had a couple users complain that some customers were getting "Delivery Status Notification" Delay errors. I took a look at my Event Viewer (application) and noticed that it was completely FULL of errors. The Errors are Source: ESE, Catagory: Database Corruption, and EventID: 447. The description is as follows:
Information Store (3832) First Storage Group: A bad page link (error -338) has been detected in a B-Tree (ObjectID: 18604, PgnoRoot: 3962053) of database E:\exchsrvr\mdbdata\priv1.edb (3962053 => 3962060, 2781903).
I clicked the link at the bottom of the error and Microsoft says:
A corrupted page link was detected in a B-Tree.
Available space in the Exchange Server Information Store database is in the form of a list of pages that can be used to store new data. The available space is called a space tree. The space tree is held as a binary tree that is searched whenever a block of new data needs to be added to the database.
During an online defragmentation, a problem was discovered in this tree.
This is often caused by a hardware failure or anti-virus scanning of the database file directory.
If you receive these errors in your application log, it is suggested that you restore from an online backup as soon as you can. A bad page link error signifies logical corruption at the Jet level in the database, and it is not safe to continue using the database. NOTE: The restore must be performed using a backup before this error occurred. In a worst case scenario, a hard repair followed by an isinteg -fix and then an ExMerge of the database may be required if no good backup exists. If you need help with a hard repair followed by an isinteg -fix and and then an ExMerge or if the problem persists, contact Microsoft Product Support Services. "
I am not sure what to do about this, and am wondering if anyone can tell me what is going on. Sounds like a bad (physically bad) hard drive, or hard drive sector maybe?