Error -1018 in Exchange 2003
Why is -1018 such a dreaded error in Exchange 2003?
What are the possible situations when you see it?
How does it impact your operations?
How do you fix it?
Reply 1)
Why is -1018 such a dreaded error in Exchange 2003?
This error indicates Hard drive error and this causes dismounting the database(s). Even if you try to mount the database you will not be able to mount the database and you might get error c1041724.
You will the -1018 error during offline defrag, but it is only if you are using any different version of eseutil utility, like if your database is belongs to 2003 and you are using eseutil of Exchange 2000 then you will get -1018 error during offline defrag process.
What are the possible situations when you see it?
If there is a problem with Hard drive then you will find a event id 474 in your Application log which mentions in the description that there could be a problem with your Hard drive. You will see the event id as below:
Date: date
Source: ESE
Time: time
Category:
Type: Error
Event ID: 474
User: N/A
Computer: Servername
Description: Information Store (2240) The database page read from the file "E:\program files\exchsrvr\mdbdata\priv1.edb" at offset 204275712 (0x000000000c2d0000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 303571876 (0x121823a4) and the actual checksum was 303571940 (0x121823e4). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup.
If you see -1018 value it means your hard drive is in trouble and you will not be able to mount the store due to bad hard drive. You need to check since when you are getting this error.
In this case you have only option is replace the bad hard drive and restore the good backup with good log files. Reply the log files with the restored backup and mount the store. You might loose the data if you don't have recent good backup.
You might not be able to mount the database(s), if the database is mounted client might facing a problem of slow connectivity. Most of the clients will not be able to access their attachments, etc.
How does it impact your operations?
If the database(s) is dismounted nobody will be able to access their mails. Database dismounting is nothing but a business impact.
How do you fix it?
You need to replace the Bad Hard drive and restore the recent good backup with good log files, ensuring that you click to clear the Last Backup Set check box in ESM. after restore, run eseutil /mk on log files to check the consistency of the log files and then replay the log files with the database by running a command eseutil /cc /t and hit enter. Then mount the database.
Reply 2)
Apart from dismounting databases, which becomes the extreme case, how else can -1018 impact operation? In other words, what things can’t be done on an Exchange server which is reporting -1018?
Reply 3)
One of the key impact you will notice due to a -1018 error is the inability to conduct online backups. Following is the sequence of events that lead to a -1018 error during an online backup
1) Exchange EDB files (not stm) stores contents in 4 KB pages (8 KB for AD and Exchange 2007)
2) In order to maintain the integrity of the data stored in each page, the system computes a checksum and includes it with the data
3) An online backup operation works by reading each page of the edb file and after verifying the checksum, writes the data to tape (or other media)
4) In case, the checksum at the time of writing does not match at the time of reading during backup, the system will presume that the integrity of the data has been compromised.
5) It will then abort the backup process and write an error in the Application log with -1018
What are the possible situations when you see it?
How does it impact your operations?
How do you fix it?
Reply 1)
Why is -1018 such a dreaded error in Exchange 2003?
This error indicates Hard drive error and this causes dismounting the database(s). Even if you try to mount the database you will not be able to mount the database and you might get error c1041724.
You will the -1018 error during offline defrag, but it is only if you are using any different version of eseutil utility, like if your database is belongs to 2003 and you are using eseutil of Exchange 2000 then you will get -1018 error during offline defrag process.
What are the possible situations when you see it?
If there is a problem with Hard drive then you will find a event id 474 in your Application log which mentions in the description that there could be a problem with your Hard drive. You will see the event id as below:
Date: date
Source: ESE
Time: time
Category:
Type: Error
Event ID: 474
User: N/A
Computer: Servername
Description: Information Store (2240) The database page read from the file "E:\program files\exchsrvr\mdbdata\priv1.edb" at offset 204275712 (0x000000000c2d0000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 303571876 (0x121823a4) and the actual checksum was 303571940 (0x121823e4). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup.
If you see -1018 value it means your hard drive is in trouble and you will not be able to mount the store due to bad hard drive. You need to check since when you are getting this error.
In this case you have only option is replace the bad hard drive and restore the good backup with good log files. Reply the log files with the restored backup and mount the store. You might loose the data if you don't have recent good backup.
You might not be able to mount the database(s), if the database is mounted client might facing a problem of slow connectivity. Most of the clients will not be able to access their attachments, etc.
How does it impact your operations?
If the database(s) is dismounted nobody will be able to access their mails. Database dismounting is nothing but a business impact.
How do you fix it?
You need to replace the Bad Hard drive and restore the recent good backup with good log files, ensuring that you click to clear the Last Backup Set check box in ESM. after restore, run eseutil /mk on log files to check the consistency of the log files and then replay the log files with the database by running a command eseutil /cc
Reply 2)
Apart from dismounting databases, which becomes the extreme case, how else can -1018 impact operation? In other words, what things can’t be done on an Exchange server which is reporting -1018?
Reply 3)
One of the key impact you will notice due to a -1018 error is the inability to conduct online backups. Following is the sequence of events that lead to a -1018 error during an online backup
1) Exchange EDB files (not stm) stores contents in 4 KB pages (8 KB for AD and Exchange 2007)
2) In order to maintain the integrity of the data stored in each page, the system computes a checksum and includes it with the data
3) An online backup operation works by reading each page of the edb file and after verifying the checksum, writes the data to tape (or other media)
4) In case, the checksum at the time of writing does not match at the time of reading during backup, the system will presume that the integrity of the data has been compromised.
5) It will then abort the backup process and write an error in the Application log with -1018
posted by Virgo Websites at
7:01 AM
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home