Error From Maintenance Plan

I am getting the following error in my Maintenance Plan. It looks as
if it is just one table (according to the Object id). My question is
how do I determine which table this is when all I have is this Object
ID?
Mark
[7] Database pcms: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 2576:
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is
pointed to by the previous pointer of IAM page (1:28607) object ID
507864876 index ID 2 but was not detected in the scan.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is
pointed to by the previous pointer of IAM page (1:28607) object ID
507864876 index ID 2 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:96558) object ID
507864876 index ID 9 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:97687) object ID
507864876 index ID 10 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:111104) object ID
507864876 index ID 11 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:117681) object ID
507864876 index ID 12 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:117690) object ID
507864876 index ID 13 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server] The repair
level on the DBCC statement caused this repair to be bypassed.
[Microsoft][ODBC SQL Server Driver][SQL Server] The repair
level on the DBCC statement caused this repair to be bypassed.
[Microsoft][ODBC SQL Server Driver][SQL Server] The repair
level on the DBCC statement caused this repair to be bypassed.
[Microsoft][ODBC SQL Server Driver][SQL Server] The repair
level on the DBCC statement caused this repair to be bypassed.
[Microsoft][ODBC SQL Server Driver][SQL Server] The repair
level on the DBCC statement caused this repair to be bypassed.
[Microsoft][ODBC SQL Server Driver][SQL Server] The repair
level on the DBCC statement caused this repair to be bypassed.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 12
allocation errors and 0 consistency errors in table '(Object ID
507864876)' (object ID 507864876).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 12
allocation errors and 0 consistency errors in database 'pcms'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss
is the minimum repair level for the errors found by DBCC CHECKDB (pcms
repair_fast).
** Execution Time: 0 hrs, 2 mins, 22 secs **Hi Mark,
As all the indexes are non clustered (their indid is greater than 1) you
should be able to solve this issue by rebuilding the indexes on your table.
You can find the name of the table that is affected with
OBJECT_NAME(507864876), and you can then rebuild the indexes with DBCC
DBREINDEX(<table name>). Make a backup of your database first though.
--
Jacco Schalkwijk
SQL Server MVP
"Mark" <markcash@.Hotmail.com> wrote in message
news:57bdc737.0402160616.508ce27f@.posting.google.com...
> I am getting the following error in my Maintenance Plan. It looks as
> if it is just one table (according to the Object id). My question is
> how do I determine which table this is when all I have is this Object
> ID?
> Mark
>
> [7] Database pcms: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 2576:
> [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is
> pointed to by the previous pointer of IAM page (1:28607) object ID
> 507864876 index ID 2 but was not detected in the scan.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is
> pointed to by the previous pointer of IAM page (1:28607) object ID
> 507864876 index ID 2 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:96558) object ID
> 507864876 index ID 9 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:97687) object ID
> 507864876 index ID 10 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:111104) object ID
> 507864876 index ID 11 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:117681) object ID
> 507864876 index ID 12 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:117690) object ID
> 507864876 index ID 13 but was not detected in the scan.
> [Microsoft][ODBC SQL Server Driver][SQL Server] The repair
> level on the DBCC statement caused this repair to be bypassed.
> [Microsoft][ODBC SQL Server Driver][SQL Server] The repair
> level on the DBCC statement caused this repair to be bypassed.
> [Microsoft][ODBC SQL Server Driver][SQL Server] The repair
> level on the DBCC statement caused this repair to be bypassed.
> [Microsoft][ODBC SQL Server Driver][SQL Server] The repair
> level on the DBCC statement caused this repair to be bypassed.
> [Microsoft][ODBC SQL Server Driver][SQL Server] The repair
> level on the DBCC statement caused this repair to be bypassed.
> [Microsoft][ODBC SQL Server Driver][SQL Server] The repair
> level on the DBCC statement caused this repair to be bypassed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 12
> allocation errors and 0 consistency errors in table '(Object ID
> 507864876)' (object ID 507864876).
> [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 12
> allocation errors and 0 consistency errors in database 'pcms'.
> [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss
> is the minimum repair level for the errors found by DBCC CHECKDB (pcms
> repair_fast).
> ** Execution Time: 0 hrs, 2 mins, 22 secs **