Hi,
I used DBCC CHECKTABLE ('xorig_pan') WITH ALL_ERRORMSGS
and I had the following response "Serveur : Msg 7965, Niveau 16, =C9tat 2, Ligne 1
Table corrupt: Could not check object ID 704601494, index ID 0 due to invalid allocation (IAM) page(s).
Serveur : Msg 8968, Niveau 16, =C9tat 1, Ligne 1
Table Corrupt: IAM page (1:223) (object ID 704601494, index ID 0) is out of the range of this database.
DBCC results for 'xorig_pan'.
There are 0 rows in 0 pages for object 'xorig_pan'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'xorig_pan' (object ID 704601494).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE ( dbo.xorig_pan )."
What can I do? I try to apply a DBCC CHECKTABLE ('xorig_pan' , REPAIR_ALLOW_DATA_LOSS) WITH ALL_ERRORMSGS but I need to be in a single user mode. How can I switch SQL Server in a single user mode ?
Thank you for your helpHi.
Clik on the right button of the mouse in your DATABASE,
select properties after select options .In the options you have a option the restric access choose SINGLE USER.
OR
By T-SQL
EXEC sp_dboption 'DATABASE_NAME', 'single user', 'TRUE'
>--Original Message--
>Hi,
>I used DBCC CHECKTABLE ('xorig_pan') WITH ALL_ERRORMSGS
>and I had the following response >"Serveur : Msg 7965, Niveau 16, =C9tat 2, Ligne 1
>Table corrupt: Could not check object ID 704601494, index >ID 0 due to invalid allocation (IAM) page(s).
>Serveur : Msg 8968, Niveau 16, =C9tat 1, Ligne 1
>Table Corrupt: IAM page (1:223) (object ID 704601494, >index ID 0) is out of the range of this database.
>DBCC results for 'xorig_pan'.
>There are 0 rows in 0 pages for object 'xorig_pan'.
>CHECKTABLE found 0 allocation errors and 2 consistency >errors in table 'xorig_pan' (object ID 704601494).
>repair_allow_data_loss is the minimum repair level for the >errors found by DBCC CHECKTABLE ( dbo.xorig_pan )."
>What can I do? I try to apply a DBCC CHECKTABLE >('xorig_pan' , REPAIR_ALLOW_DATA_LOSS) WITH >ALL_ERRORMSGS but I need to be in a single user mode. >How can I switch SQL Server in a single user mode ?
>Thank you for your help
>.
>|||Here are the general recommendations for handling a suspect or corrupt
database:
0. Ensure you have a backup strategy that you can use to recover from
hardware failures (including corruption). I recommend performing both
database and log backup in most situations.
1. If you can run DBCC CHECKDB against the database: Search Books Online and
KB for the error numbers that CHECKDB gives you. There might be specific
info for that type of error.
2. Find out why this happened. Check eventlog, do HW diagnostics etc.;
search Books Online and KB for those errors. You don't want this to happen
again! If the database is suspect, the file might have been in use by for
instance an anti-virus program and restarting SQL Server might be all that
is needed - but you still want to read logs etc to find out what happened.
3. If there is a hardware problem, ensure the faulty hardware is replaced.
4. Backup the log. This assumes that log backup schedule is in place, of
course. If the database is suspect, then the NO_TRUNCATE option for the
RESTORE command must be used. Also, you might want to do a file backup of
the mdf and ldf files, for extra safety.
5. Restore is the best thing to do now. If you managed to backup log as per
step 4, then you will most probably have zero dataloss. You should restore
the latest clean database backup and the subsequent log backups including
the one taken in above step.
If the database isn't suspect, then DBCC with a REPAIR option might be a
secondary option but this will often result in loss of data. Additional
solutions, depending on the errors, may be to manually rebuild non-clustered
indexes, manually drop and reload a table if the data is static, and so on.
If the database is suspect, a secondary option can be to try to "un-suspect"
the database using sp_resetstatus. Read about it (books online, KB, google
etc). It might help but if the database is too damaged, it might just pop
back to suspect again. There's also something called "emergency mode" which
is a "panic" status you can set in order to try to get data out of a damaged
database. I think the name of that option speaks for itself. Again search
the net for info.
If you feel uncertain with above steps, I recommend letting MS hand-hold you
through the steps appropriate for your particular situation.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"LEMARIE" <sylvain.lemarie@.solymatic.com> wrote in message
news:023b01c3aa95$d47b3840$a001280a@.phx.gbl...
Hi,
I used DBCC CHECKTABLE ('xorig_pan') WITH ALL_ERRORMSGS
and I had the following response
"Serveur : Msg 7965, Niveau 16, État 2, Ligne 1
Table corrupt: Could not check object ID 704601494, index
ID 0 due to invalid allocation (IAM) page(s).
Serveur : Msg 8968, Niveau 16, État 1, Ligne 1
Table Corrupt: IAM page (1:223) (object ID 704601494,
index ID 0) is out of the range of this database.
DBCC results for 'xorig_pan'.
There are 0 rows in 0 pages for object 'xorig_pan'.
CHECKTABLE found 0 allocation errors and 2 consistency
errors in table 'xorig_pan' (object ID 704601494).
repair_allow_data_loss is the minimum repair level for the
errors found by DBCC CHECKTABLE ( dbo.xorig_pan )."
What can I do? I try to apply a DBCC CHECKTABLE
('xorig_pan' , REPAIR_ALLOW_DATA_LOSS) WITH
ALL_ERRORMSGS but I need to be in a single user mode.
How can I switch SQL Server in a single user mode ?
Thank you for your help|||Hi sylvain:
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
In addition to Jorge and Tibor's information, I provide some for your
referene.
As we know, the 7965 and 8968 errors indicate the allocation or
inconsistency errors on your database. Did you have the recent backup for
this database? Restoring the backup file is the most efficiency methods to
recover the database.
If not, please try the following steps to recover the database. However, we
cannot guarantee that there is no data loss for your database.
1.Backup your current database to avoid the risk during our troubleshooting
process
2.Set the database with single user mode.
There are two ways. I list both of them for your reference.
In the SQL Enterprise Manager, right click the problematic database and
click properties. Click the options tab. Check the ¡®Restrict Access¡¯
checkbox and choose ¡®Single user¡¯
Or
In the SQL query analyzer execute T-SQL statement ¡°EXEC sp_dboption
'DATABASE_NAME', 'single user', 'TRUE'¡°.
Note:
a. Please replace the ¡°'DATABASE_NAME¡± with the actual database name
b. Make sure that no other user is connected with this database before you
perform the operations above.
3.In SQL Query analyzer, execute the ¡®dbcc checkdb with
repair_allow_data_loss¡¯
Note:
Please replace the ¡°'DATABASE_NAME¡± with the actual database name
If the steps above do not work, please post the following information in
order to let us have a concrete idea regarding this issue.
1.The application log and the system log
2.The SQLdiag output
To collect the SQLDiag.txt, open a Command Prompt, and change the current
directory to wherever the SQL binaries are (for example: C:\Program
Files\Microsoft SQL Server\MSSQL\Binn) and execute 'SQLDIAG.EXE'.
Have a good weekend
Sincerely Yours
Wei,Baisong
| Content-Class: urn:content-classes:message
| From: "LEMARIE" <sylvain.lemarie@.solymatic.com>
| Sender: "LEMARIE" <sylvain.lemarie@.solymatic.com>
| Subject: DBCC Checktable Error
| Date: Fri, 14 Nov 2003 01:58:18 -0800
| Lines: 22
| Message-ID: <023b01c3aa95$d47b3840$a001280a@.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: quoted-printable
| X-Newsreader: Microsoft CDO for Windows 2000
| Thread-Index: AcOqldR4uc6m479DRzCXnSdw0qYkGg==| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Newsgroups: microsoft.public.sqlserver.server
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:316502
| NNTP-Posting-Host: TK2MSFTNGXA08 10.40.1.160
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hi,
| I used DBCC CHECKTABLE ('xorig_pan') WITH ALL_ERRORMSGS
| and I had the following response
| "Serveur : Msg 7965, Niveau 16, État 2, Ligne 1
| Table corrupt: Could not check object ID 704601494, index
| ID 0 due to invalid allocation (IAM) page(s).
| Serveur : Msg 8968, Niveau 16, État 1, Ligne 1
| Table Corrupt: IAM page (1:223) (object ID 704601494,
| index ID 0) is out of the range of this database.
| DBCC results for 'xorig_pan'.
| There are 0 rows in 0 pages for object 'xorig_pan'.
| CHECKTABLE found 0 allocation errors and 2 consistency
| errors in table 'xorig_pan' (object ID 704601494).
| repair_allow_data_loss is the minimum repair level for the
| errors found by DBCC CHECKTABLE ( dbo.xorig_pan )."
| What can I do? I try to apply a DBCC CHECKTABLE
| ('xorig_pan' , REPAIR_ALLOW_DATA_LOSS) WITH
| ALL_ERRORMSGS but I need to be in a single user mode.
| How can I switch SQL Server in a single user mode ?
| Thank you for your help
|
Showing posts with label all_errormsgs. Show all posts
Showing posts with label all_errormsgs. Show all posts
Friday, February 24, 2012
Friday, February 17, 2012
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...
>
>
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...
>
>
Tuesday, February 14, 2012
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...
> > 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.
> >
>
>|||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...
> 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...
>> > 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 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...
> > 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...
> >> > 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.
> >> >
> >>
> >>
> >>
>
>
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...
> > 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.
> >
>
>|||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...
> 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...
>> > 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 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...
> > 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...
> >> > 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.
> >> >
> >>
> >>
> >>
>
>
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...
>
>
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...
>
>
DBCC CHECKDB (database) WITH ALL_ERRORMSGS
Yesterday, I received approximately 200 error messages from the T-SQL DBCC
CHECKDB(database) WITH ALL_ERRORMSGS command.
Listed below are some of the output errors that I received.
Please let me know the best way to resolve these errors.
Thank You,
DBCC results for 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:80654) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:80654). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:81930) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:81930). Test
(m_freeCnt == freeCnt) failed. Values are 207 and 239.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:75016) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:75016). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81936) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81936). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81938) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81938). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:83168) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:83168). Test
(m_freeCnt == freeCnt) failed. Values are 219 and 251.
There are 254060 rows in 6235 pages for object 'USER_ATTR'.
CHECKDB found 0 allocation errors and 8 consistency errors in table
'USER_ATTR' (object ID 826486023).
DBCC results for 'ATTRIBUTE_SUMMARY'.
Server: Msg 8939, Level 16, State 106, Line 1
Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
in the scan although its parent (1:15408) and previous (1:76422) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
reference from previous page (1:80730). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1975730141, index ID 4: Page (1:79858) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
in the scan although its parent (1:81368) and previous (1:74375) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
reference from previous page (1:79858). Possible chain linkage problem.
There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
CHECKDB found 0 allocation errors and 12 consistency errors in table
'ATTRIBUTE_SUMMARY' (You might want to review this
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=738137&SiteID=1
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:57321F20-58C5-4BA8-9EA4-2222531294F9@.microsoft.com...
> Yesterday, I received approximately 200 error messages from the T-SQL DBCC
> CHECKDB(database) WITH ALL_ERRORMSGS command.
> Listed below are some of the output errors that I received.
> Please let me know the best way to resolve these errors.
> Thank You,
>
> DBCC results for 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:80654) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:80654). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:81930) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:81930). Test
> (m_freeCnt == freeCnt) failed. Values are 207 and 239.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:75016) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:75016). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81936) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81936). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81938) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81938). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:83168) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:83168). Test
> (m_freeCnt == freeCnt) failed. Values are 219 and 251.
> There are 254060 rows in 6235 pages for object 'USER_ATTR'.
> CHECKDB found 0 allocation errors and 8 consistency errors in table
> 'USER_ATTR' (object ID 826486023).
>
> DBCC results for 'ATTRIBUTE_SUMMARY'.
> Server: Msg 8939, Level 16, State 106, Line 1
> Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
> in the scan although its parent (1:15408) and previous (1:76422) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
> reference from previous page (1:80730). Possible chain linkage problem.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1975730141, index ID 4: Page (1:79858) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
> in the scan although its parent (1:81368) and previous (1:74375) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
> reference from previous page (1:79858). Possible chain linkage problem.
> There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
> CHECKDB found 0 allocation errors and 12 consistency errors in table
> 'ATTRIBUTE_SUMMARY' (
CHECKDB(database) WITH ALL_ERRORMSGS command.
Listed below are some of the output errors that I received.
Please let me know the best way to resolve these errors.
Thank You,
DBCC results for 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:80654) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:80654). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:81930) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:81930). Test
(m_freeCnt == freeCnt) failed. Values are 207 and 239.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:75016) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:75016). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81936) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81936). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81938) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81938). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:83168) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:83168). Test
(m_freeCnt == freeCnt) failed. Values are 219 and 251.
There are 254060 rows in 6235 pages for object 'USER_ATTR'.
CHECKDB found 0 allocation errors and 8 consistency errors in table
'USER_ATTR' (object ID 826486023).
DBCC results for 'ATTRIBUTE_SUMMARY'.
Server: Msg 8939, Level 16, State 106, Line 1
Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
in the scan although its parent (1:15408) and previous (1:76422) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
reference from previous page (1:80730). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1975730141, index ID 4: Page (1:79858) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
in the scan although its parent (1:81368) and previous (1:74375) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
reference from previous page (1:79858). Possible chain linkage problem.
There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
CHECKDB found 0 allocation errors and 12 consistency errors in table
'ATTRIBUTE_SUMMARY' (You might want to review this
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=738137&SiteID=1
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:57321F20-58C5-4BA8-9EA4-2222531294F9@.microsoft.com...
> Yesterday, I received approximately 200 error messages from the T-SQL DBCC
> CHECKDB(database) WITH ALL_ERRORMSGS command.
> Listed below are some of the output errors that I received.
> Please let me know the best way to resolve these errors.
> Thank You,
>
> DBCC results for 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:80654) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:80654). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:81930) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:81930). Test
> (m_freeCnt == freeCnt) failed. Values are 207 and 239.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:75016) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:75016). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81936) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81936). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81938) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81938). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:83168) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:83168). Test
> (m_freeCnt == freeCnt) failed. Values are 219 and 251.
> There are 254060 rows in 6235 pages for object 'USER_ATTR'.
> CHECKDB found 0 allocation errors and 8 consistency errors in table
> 'USER_ATTR' (object ID 826486023).
>
> DBCC results for 'ATTRIBUTE_SUMMARY'.
> Server: Msg 8939, Level 16, State 106, Line 1
> Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
> in the scan although its parent (1:15408) and previous (1:76422) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
> reference from previous page (1:80730). Possible chain linkage problem.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1975730141, index ID 4: Page (1:79858) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
> in the scan although its parent (1:81368) and previous (1:74375) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
> reference from previous page (1:79858). Possible chain linkage problem.
> There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
> CHECKDB found 0 allocation errors and 12 consistency errors in table
> 'ATTRIBUTE_SUMMARY' (
DBCC CHECKDB (database) WITH ALL_ERRORMSGS
Yesterday, I received approximately 200 error messages from the T-SQL DBCC
CHECKDB(database) WITH ALL_ERRORMSGS command.
Listed below are some of the output errors that I received.
Please let me know the best way to resolve these errors.
Thank You,
DBCC results for 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:80654) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:80654). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:81930) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:81930). Test
(m_freeCnt == freeCnt) failed. Values are 207 and 239.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:75016) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:75016). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81936) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81936). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81938) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81938). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:83168) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:83168). Test
(m_freeCnt == freeCnt) failed. Values are 219 and 251.
There are 254060 rows in 6235 pages for object 'USER_ATTR'.
CHECKDB found 0 allocation errors and 8 consistency errors in table
'USER_ATTR' (object ID 826486023).
DBCC results for 'ATTRIBUTE_SUMMARY'.
Server: Msg 8939, Level 16, State 106, Line 1
Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
in the scan although its parent (1:15408) and previous (1:76422) refer to it
.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
reference from previous page (1:80730). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1975730141, index ID 4: Page (1:79858) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
in the scan although its parent (1:81368) and previous (1:74375) refer to it
.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
reference from previous page (1:79858). Possible chain linkage problem.
There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
CHECKDB found 0 allocation errors and 12 consistency errors in table
'ATTRIBUTE_SUMMARY' (You might want to review this
http://forums.microsoft.com/MSDN/Sh...738137&SiteID=1
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:57321F20-58C5-4BA8-9EA4-2222531294F9@.microsoft.com...
> Yesterday, I received approximately 200 error messages from the T-SQL DBCC
> CHECKDB(database) WITH ALL_ERRORMSGS command.
> Listed below are some of the output errors that I received.
> Please let me know the best way to resolve these errors.
> Thank You,
>
> DBCC results for 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:80654) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:80654). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:81930) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:81930). Test
> (m_freeCnt == freeCnt) failed. Values are 207 and 239.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:75016) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:75016). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81936) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81936). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81938) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81938). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:83168) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:83168). Test
> (m_freeCnt == freeCnt) failed. Values are 219 and 251.
> There are 254060 rows in 6235 pages for object 'USER_ATTR'.
> CHECKDB found 0 allocation errors and 8 consistency errors in table
> 'USER_ATTR' (object ID 826486023).
>
> DBCC results for 'ATTRIBUTE_SUMMARY'.
> Server: Msg 8939, Level 16, State 106, Line 1
> Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
> in the scan although its parent (1:15408) and previous (1:76422) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
> reference from previous page (1:80730). Possible chain linkage problem.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1975730141, index ID 4: Page (1:79858) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
> in the scan although its parent (1:81368) and previous (1:74375) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
> reference from previous page (1:79858). Possible chain linkage problem.
> There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
> CHECKDB found 0 allocation errors and 12 consistency errors in table
> 'ATTRIBUTE_SUMMARY' (
CHECKDB(database) WITH ALL_ERRORMSGS command.
Listed below are some of the output errors that I received.
Please let me know the best way to resolve these errors.
Thank You,
DBCC results for 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:80654) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:80654). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:81930) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:81930). Test
(m_freeCnt == freeCnt) failed. Values are 207 and 239.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:75016) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:75016). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81936) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81936). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81938) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81938). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:83168) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:83168). Test
(m_freeCnt == freeCnt) failed. Values are 219 and 251.
There are 254060 rows in 6235 pages for object 'USER_ATTR'.
CHECKDB found 0 allocation errors and 8 consistency errors in table
'USER_ATTR' (object ID 826486023).
DBCC results for 'ATTRIBUTE_SUMMARY'.
Server: Msg 8939, Level 16, State 106, Line 1
Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
in the scan although its parent (1:15408) and previous (1:76422) refer to it
.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
reference from previous page (1:80730). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1975730141, index ID 4: Page (1:79858) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
in the scan although its parent (1:81368) and previous (1:74375) refer to it
.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
reference from previous page (1:79858). Possible chain linkage problem.
There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
CHECKDB found 0 allocation errors and 12 consistency errors in table
'ATTRIBUTE_SUMMARY' (You might want to review this
http://forums.microsoft.com/MSDN/Sh...738137&SiteID=1
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:57321F20-58C5-4BA8-9EA4-2222531294F9@.microsoft.com...
> Yesterday, I received approximately 200 error messages from the T-SQL DBCC
> CHECKDB(database) WITH ALL_ERRORMSGS command.
> Listed below are some of the output errors that I received.
> Please let me know the best way to resolve these errors.
> Thank You,
>
> DBCC results for 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:80654) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:80654). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:81930) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:81930). Test
> (m_freeCnt == freeCnt) failed. Values are 207 and 239.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:75016) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:75016). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81936) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81936). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81938) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81938). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:83168) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:83168). Test
> (m_freeCnt == freeCnt) failed. Values are 219 and 251.
> There are 254060 rows in 6235 pages for object 'USER_ATTR'.
> CHECKDB found 0 allocation errors and 8 consistency errors in table
> 'USER_ATTR' (object ID 826486023).
>
> DBCC results for 'ATTRIBUTE_SUMMARY'.
> Server: Msg 8939, Level 16, State 106, Line 1
> Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
> in the scan although its parent (1:15408) and previous (1:76422) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
> reference from previous page (1:80730). Possible chain linkage problem.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1975730141, index ID 4: Page (1:79858) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
> in the scan although its parent (1:81368) and previous (1:74375) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
> reference from previous page (1:79858). Possible chain linkage problem.
> There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
> CHECKDB found 0 allocation errors and 12 consistency errors in table
> 'ATTRIBUTE_SUMMARY' (
DBCC CHECKDB (database) WITH ALL_ERRORMSGS
Yesterday, I received approximately 200 error messages from the T-SQL DBCC
CHECKDB(database) WITH ALL_ERRORMSGS command.
Listed below are some of the output errors that I received.
Please let me know the best way to resolve these errors.
Thank You,
DBCC results for 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:80654) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:80654). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:81930) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:81930). Test
(m_freeCnt == freeCnt) failed. Values are 207 and 239.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:75016) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:75016). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81936) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81936). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81938) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81938). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:83168) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:83168). Test
(m_freeCnt == freeCnt) failed. Values are 219 and 251.
There are 254060 rows in 6235 pages for object 'USER_ATTR'.
CHECKDB found 0 allocation errors and 8 consistency errors in table
'USER_ATTR' (object ID 826486023).
DBCC results for 'ATTRIBUTE_SUMMARY'.
Server: Msg 8939, Level 16, State 106, Line 1
Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
in the scan although its parent (1:15408) and previous (1:76422) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
reference from previous page (1:80730). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1975730141, index ID 4: Page (1:79858) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
in the scan although its parent (1:81368) and previous (1:74375) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
reference from previous page (1:79858). Possible chain linkage problem.
There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
CHECKDB found 0 allocation errors and 12 consistency errors in table
'ATTRIBUTE_SUMMARY' (
You might want to review this
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=738137&SiteID=1
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:57321F20-58C5-4BA8-9EA4-2222531294F9@.microsoft.com...
> Yesterday, I received approximately 200 error messages from the T-SQL DBCC
> CHECKDB(database) WITH ALL_ERRORMSGS command.
> Listed below are some of the output errors that I received.
> Please let me know the best way to resolve these errors.
> Thank You,
>
> DBCC results for 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:80654) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:80654). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:81930) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:81930). Test
> (m_freeCnt == freeCnt) failed. Values are 207 and 239.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:75016) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:75016). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81936) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81936). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81938) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81938). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:83168) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:83168). Test
> (m_freeCnt == freeCnt) failed. Values are 219 and 251.
> There are 254060 rows in 6235 pages for object 'USER_ATTR'.
> CHECKDB found 0 allocation errors and 8 consistency errors in table
> 'USER_ATTR' (object ID 826486023).
>
> DBCC results for 'ATTRIBUTE_SUMMARY'.
> Server: Msg 8939, Level 16, State 106, Line 1
> Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
> in the scan although its parent (1:15408) and previous (1:76422) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
> reference from previous page (1:80730). Possible chain linkage problem.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1975730141, index ID 4: Page (1:79858) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
> in the scan although its parent (1:81368) and previous (1:74375) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
> reference from previous page (1:79858). Possible chain linkage problem.
> There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
> CHECKDB found 0 allocation errors and 12 consistency errors in table
> 'ATTRIBUTE_SUMMARY' (
CHECKDB(database) WITH ALL_ERRORMSGS command.
Listed below are some of the output errors that I received.
Please let me know the best way to resolve these errors.
Thank You,
DBCC results for 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:80654) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:80654). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:81930) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:81930). Test
(m_freeCnt == freeCnt) failed. Values are 207 and 239.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:75016) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:75016). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81936) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81936). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81938) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81938). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:83168) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:83168). Test
(m_freeCnt == freeCnt) failed. Values are 219 and 251.
There are 254060 rows in 6235 pages for object 'USER_ATTR'.
CHECKDB found 0 allocation errors and 8 consistency errors in table
'USER_ATTR' (object ID 826486023).
DBCC results for 'ATTRIBUTE_SUMMARY'.
Server: Msg 8939, Level 16, State 106, Line 1
Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
in the scan although its parent (1:15408) and previous (1:76422) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
reference from previous page (1:80730). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1975730141, index ID 4: Page (1:79858) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
in the scan although its parent (1:81368) and previous (1:74375) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
reference from previous page (1:79858). Possible chain linkage problem.
There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
CHECKDB found 0 allocation errors and 12 consistency errors in table
'ATTRIBUTE_SUMMARY' (
You might want to review this
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=738137&SiteID=1
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:57321F20-58C5-4BA8-9EA4-2222531294F9@.microsoft.com...
> Yesterday, I received approximately 200 error messages from the T-SQL DBCC
> CHECKDB(database) WITH ALL_ERRORMSGS command.
> Listed below are some of the output errors that I received.
> Please let me know the best way to resolve these errors.
> Thank You,
>
> DBCC results for 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:80654) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:80654). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:81930) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:81930). Test
> (m_freeCnt == freeCnt) failed. Values are 207 and 239.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:75016) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:75016). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81936) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81936). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81938) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81938). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:83168) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:83168). Test
> (m_freeCnt == freeCnt) failed. Values are 219 and 251.
> There are 254060 rows in 6235 pages for object 'USER_ATTR'.
> CHECKDB found 0 allocation errors and 8 consistency errors in table
> 'USER_ATTR' (object ID 826486023).
>
> DBCC results for 'ATTRIBUTE_SUMMARY'.
> Server: Msg 8939, Level 16, State 106, Line 1
> Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
> in the scan although its parent (1:15408) and previous (1:76422) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
> reference from previous page (1:80730). Possible chain linkage problem.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1975730141, index ID 4: Page (1:79858) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
> in the scan although its parent (1:81368) and previous (1:74375) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
> reference from previous page (1:79858). Possible chain linkage problem.
> There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
> CHECKDB found 0 allocation errors and 12 consistency errors in table
> 'ATTRIBUTE_SUMMARY' (
DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS...
Friends,
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to ru
n
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backu
ps
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be check
ed
> too? Is there anything else we should be concerned about? (Other than lo
st
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to ru
n
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backu
ps
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be check
ed
> too? Is there anything else we should be concerned about? (Other than lo
st
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS...
Friends,
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to run
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backups
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be checked
> too? Is there anything else we should be concerned about? (Other than lost
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to run
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backups
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be checked
> too? Is there anything else we should be concerned about? (Other than lost
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS...
Friends,
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.
Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to run
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backups
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be checked
> too? Is there anything else we should be concerned about? (Other than lost
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.
Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to run
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backups
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be checked
> too? Is there anything else we should be concerned about? (Other than lost
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
Subscribe to:
Posts (Atom)