DBCC CheckDB error

We run nightly jobs on all of our SQL Servers (over 70) which run
DBCC CHECKDB ('<db_name>') with ALL_ERRORMSGS. Frequently we get the
following errors:
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of
IAM page (1:4216) object ID 16 index ID 0 but was not detected in the scan.
[SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of
IAM page (1:4218) object ID 16 index ID 2 but was not detected in the scan.
[SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of
IAM page (1:7811) object ID 17 index ID 0 but was not detected in the scan.
[SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of
IAM page (1:7819) object ID 17 index ID 2 but was not detected in the scan.
[SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of
IAM page (1:7821) object ID 17 index ID 3 but was not detected in the scan.
[SQLSTATE 42000]
These errors happen on different servers/databases. When I try to fix these
errors with DBCC CHECKDB and any of the repair options it reports that it is
not running at the correct repair level to fix the errors. Also when you
look in the database there is no object with an id of 16 or 17.
Can anyone help with this?
This is happening on SQL Server 2K with SP3 and SP4.
Thank you.These two tables are replication tables:
SYSARTICLES = 16, SYSPUBLICATIONS = 17,
The errors say that the metadata entries for the tables and their indexes do
not exist in sysindexes. Have you had an replication problems? Did someone
manually remove the entries from sysindexes?
Thanks
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Len Gustafson" <LenGustafson@.discussions.microsoft.com> wrote in message
news:BAABD7AB-294C-4D01-85CA-3CC3312434A5@.microsoft.com...
> We run nightly jobs on all of our SQL Servers (over 70) which run
> DBCC CHECKDB ('<db_name>') with ALL_ERRORMSGS. Frequently we get the
> following errors:
> Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of
> IAM page (1:4216) object ID 16 index ID 0 but was not detected in the
> scan.
> [SQLSTATE 42000]
> Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of
> IAM page (1:4218) object ID 16 index ID 2 but was not detected in the
> scan.
> [SQLSTATE 42000]
> Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of
> IAM page (1:7811) object ID 17 index ID 0 but was not detected in the
> scan.
> [SQLSTATE 42000]
> Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of
> IAM page (1:7819) object ID 17 index ID 2 but was not detected in the
> scan.
> [SQLSTATE 42000]
> Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of
> IAM page (1:7821) object ID 17 index ID 3 but was not detected in the
> scan.
> [SQLSTATE 42000]
> These errors happen on different servers/databases. When I try to fix
> these
> errors with DBCC CHECKDB and any of the repair options it reports that it
> is
> not running at the correct repair level to fix the errors. Also when you
> look in the database there is no object with an id of 16 or 17.
> Can anyone help with this?
> This is happening on SQL Server 2K with SP3 and SP4.
> Thank you.
>|||Paul,
Thank you for your response.
We have not had any replication problems and we did not manually remove the
entries from sysindexes. Do you know of a way we could prevent this from
happening in the future?
I did want to correct something i wrote in the original post, DBCC CheckDB
does fix these errors if you run it in the REPAIR_ALLOW_DATA_LOSS mode but
not in the others.
Thanks,
Len Gustafson
"Paul S Randal [MS]" wrote:

> These two tables are replication tables:
> SYSARTICLES = 16, SYSPUBLICATIONS = 17,
> The errors say that the metadata entries for the tables and their indexes
do
> not exist in sysindexes. Have you had an replication problems? Did someone
> manually remove the entries from sysindexes?
> Thanks
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Len Gustafson" <LenGustafson@.discussions.microsoft.com> wrote in message
> news:BAABD7AB-294C-4D01-85CA-3CC3312434A5@.microsoft.com...
>
>|||I don't know why this happened so can't suggest a way to stop it happening.
You should call Product Support to help you (http://support.microsoft.com).
Thanks
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Len Gustafson" <LenGustafson@.discussions.microsoft.com> wrote in message
news:631CD829-06C3-4A1C-ADF9-60799AE08077@.microsoft.com...[vbcol=seagreen]
> Paul,
> Thank you for your response.
> We have not had any replication problems and we did not manually remove
> the
> entries from sysindexes. Do you know of a way we could prevent this from
> happening in the future?
> I did want to correct something i wrote in the original post, DBCC CheckDB
> does fix these errors if you run it in the REPAIR_ALLOW_DATA_LOSS mode but
> not in the others.
>
> Thanks,
> Len Gustafson
>
> "Paul S Randal [MS]" wrote:
>|||Paul,
Thank you for your help.
Len Gustafson
"Paul S Randal [MS]" wrote:

> I don't know why this happened so can't suggest a way to stop it happening
.
> You should call Product Support to help you (http://support.microsoft.com)
.
> Thanks
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Len Gustafson" <LenGustafson@.discussions.microsoft.com> wrote in message
> news:631CD829-06C3-4A1C-ADF9-60799AE08077@.microsoft.com...
>
>