Index Error from Database Integrity Job

Listed below is an error that I received from my SQL Server 2000 database
maintenance plan from the database integrity check job.
After receiving this error, I applied the following parameters to rebuild
all of the table indexes.
I received the same error after rebuilding the table indexes from the
parameter listed below.
DBCC DBREINDEX (MarketDeals, '', 0)
Please help me resolve this error.
Thanks,
Error Messages:
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to
by the previous pointer of IAM page (1:8596228) object ID 781961862 index ID
3 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to
by the previous pointer of IAM page (1:8596444) object ID 781961862 index ID
4 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 2 allocation
errors and 0 consistency errors in table 'MarketDeals'
You seem to have a corruption in your database.
If you are lucky, you can just drop the corrupted index and then find out why this happened in the
first place (HW errors probably, so you need to fix that).
Warm up the tape machines, since this might mean that you need to do a restore. First, run DBCC
CHECKDB using the NO_INFOMSGS option to get error numbers back that you can search for in Books
Online. Then search for those error numbers. Make sure that you have the most recent update of Books
Online as it contains specific recommendations for each corruption-type of error number. Also, see:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:E79AFF38-33A0-474B-A82D-F3FE62353ECC@.microsoft.com...
> Listed below is an error that I received from my SQL Server 2000 database
> maintenance plan from the database integrity check job.
> After receiving this error, I applied the following parameters to rebuild
> all of the table indexes.
> I received the same error after rebuilding the table indexes from the
> parameter listed below.
> DBCC DBREINDEX (MarketDeals, '', 0)
> Please help me resolve this error.
> Thanks,
>
> Error Messages:
> [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to
> by the previous pointer of IAM page (1:8596228) object ID 781961862 index ID
> 3 but was not detected in the scan.
> [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to
> by the previous pointer of IAM page (1:8596444) object ID 781961862 index ID
> 4 but was not detected in the scan.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 2 allocation
> errors and 0 consistency errors in table 'MarketDeals'
|||Joe
I suspect your database gets corrupted
Run DBCC CHECKDB to repair the data
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:E79AFF38-33A0-474B-A82D-F3FE62353ECC@.microsoft.com...
> Listed below is an error that I received from my SQL Server 2000 database
> maintenance plan from the database integrity check job.
> After receiving this error, I applied the following parameters to rebuild
> all of the table indexes.
> I received the same error after rebuilding the table indexes from the
> parameter listed below.
> DBCC DBREINDEX (MarketDeals, '', 0)
> Please help me resolve this error.
> Thanks,
>
> Error Messages:
> [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed
to
> by the previous pointer of IAM page (1:8596228) object ID 781961862 index
ID
> 3 but was not detected in the scan.
> [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed
to
> by the previous pointer of IAM page (1:8596444) object ID 781961862 index
ID
> 4 but was not detected in the scan.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 2 allocation
> errors and 0 consistency errors in table 'MarketDeals'
|||You shouldn't ever run repair to correct corruptions without first working
out why the corruption occured and preferably restoring from a backup.
Repair fixes the database structures but will most likely break any
application logic inherent in the data stored in the database (as it may
have to delete records or pages to restore consistency).
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:#pykSmLUFHA.2172@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Joe
> I suspect your database gets corrupted
> Run DBCC CHECKDB to repair the data
>
> "Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
> news:E79AFF38-33A0-474B-A82D-F3FE62353ECC@.microsoft.com...
database[vbcol=seagreen]
rebuild[vbcol=seagreen]
> to
index[vbcol=seagreen]
> ID
> to
index[vbcol=seagreen]
> ID
allocation
>
|||Paul
Yes, I agree that the OP should investigate why it has happened but this
commnad provides three methods of repair. My mistake was that I did not
mention to what repair to be more useful
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:eeWU%23IPUFHA.544@.TK2MSFTNGP15.phx.gbl...
> You shouldn't ever run repair to correct corruptions without first working
> out why the corruption occured and preferably restoring from a backup.
> Repair fixes the database structures but will most likely break any
> application logic inherent in the data stored in the database (as it may
> have to delete records or pages to restore consistency).
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:#pykSmLUFHA.2172@.tk2msftngp13.phx.gbl...
> database
> rebuild
pointed[vbcol=seagreen]
> index
pointed
> index
> allocation
>