Allocation Error

I received the following error when I run a DBCC Checkdb

DBCC results for 'mwlLoanApp'.
Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:20434) in object ID 59147256, index ID 118, partition ID 72057594900316160, alloc unit ID 72057594937344000 (type In-row data), but it was not detected in the scan.
Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:18960) in object ID 59147256, index ID 119, partition ID 72057594900250624, alloc unit ID 72057594937278464 (type In-row data), but it was not detected in the scan.
Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:20457) in object ID 59147256, index ID 120, partition ID 72057594900381696, alloc unit ID 72057594937409536 (type In-row data), but it was not detected in the scan.
There are 69384 rows in 7690 pages for object "mwlLoanApp".
CHECKDB found 3 allocation errors and 0 consistency errors in table 'mwlLoanApp' (object ID 59147256).

This is what I did to correct the issue

1)      Backup the database
2)      Export scripts to create all non-clustered indexes on the mwlloanapp table
3)      Put the database in single User Mode
4)      Drop all non-clustered indexes on the mwlloanapp table
5)      run DBCC CHECKDB (Interlinqe3, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS
6)      Recreate non-clustered indexes

After doing this I am still receiving the same errors for the same table.  Any other suggestions?  Thanks
MortgageInvestorsAsked:
Who is Participating?
 
Aaron ShiloConnect With a Mentor Chief Database ArchitectCommented:
hi

basically this means you have an hardware problem (http://msdn.microsoft.com/en-us/library/ms365260(v=SQL.100).aspx)

i would suggest to create a new file group and drop all indexes and move the table to the FG and recreate the indexes.

this should fix it.
0
 
Daniel_PLDB Expert/ArchitectCommented:
Copy that database to some test enviroment and follow intructions provided by Paul Randal here:
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=53072

1) assuming you have the index definitions on hand:
a) drop all non-clustered indexes on the tables with corruption
b) run DBCC CHECKDB (MAGIC, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS
c) recreate all the non-clustered indexes

2) if you don't have the index definitions available:
a) run DBCC CHECKDB (MAGIC, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS
b) run DBCC CHECKDB (MAGIC) WITH NO_INFOMSGS
c) repeat steps a) and b) until no more errors are reported
0
 
MortgageInvestorsAuthor Commented:
It did not resolve my issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.