MS SQL Server - DB Consistency Errors occurring frequently on random tables

Author

DB Consistency Errors occurring frequently on random tables

Sameer Premji via SQLMonster.com

2005-05-20, 8:23 pm

Hi,

I am using Maintenance Wizard to backup my db's and I utilize one of its
features of checking database inconsistencies just before backing up.

It scheduled as jobs and at 4:00PM the Integrity Check job fired and it
passed. At 4:05pm, Database Backup job started and it failed on one of the
database called Dev.

This is the dump of error: -

====================
====================
===================
Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE 42000]
(Error 22029). The step failed.

[Microsoft][ODBC SQL Server Driver][SQL Server]
Object ID 806345987, index ID 0: Page (1:1647) could not be processed. See
other errors for details.

[Microsoft][ODBC SQL Server Driver][SQL Server]
Table error: Object ID 806345987, index ID 0, page (1:1647), row 17. Test
(ColumnOffsets <= (nextRec - pRec)) failed. Values are 1064 and 58.

[Microsoft][ODBC SQL Server Driver][SQL Server]
CHECKDB found 0 allocation errors and 2 consistency errors in table
'rStk_ComponentRecep
tionTemp' (object ID 806345987).
====================
====================
===================

It is weird because between 4:00PM and 4:05PM, something must have hapenned
to render the "Dev" as incosistent. This has been hapenning since yesterday
on random tables without any pattern.

Inside my Maintenance Plan, under Integrity Tab --> selected 'Check
database integrity' --> selected 'Exclude Indexes' --> selected 'Perform
these checks before backing up ...'

Moreover, the rest of the databases got backed up fine.

What is causing the inconsistency ?

How can I go about repairing it ?

Thanks,

Sameer.

--
Message posted via http://www.webservertalk.com

Tibor Karaszi

2005-05-21, 3:23 am

1. Run DBCC CHECKDB from QA using WITH NO_INFOMSGS.
2. Search the updated Books Online for the error numbers you have, there are specific
recommendations for each type of corruption there. More info at:

http://www.karaszi.com/SQLServer/ i...t
_db.asp

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/

"Sameer Premji via webservertalk.com" <forum@nospam.webservertalk.com> wrote in message
news:f9eee595f5d0409
18bad56754cf751bf@we
bservertalk.com...
> Hi,
>
> I am using Maintenance Wizard to backup my db's and I utilize one of its
> features of checking database inconsistencies just before backing up.
>
> It scheduled as jobs and at 4:00PM the Integrity Check job fired and it
> passed. At 4:05pm, Database Backup job started and it failed on one of the
> database called Dev.
>
> This is the dump of error: -
>
> ====================
====================
===================
> Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE 42000]
> (Error 22029). The step failed.
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]
> Object ID 806345987, index ID 0: Page (1:1647) could not be processed. See
> other errors for details.
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]
> Table error: Object ID 806345987, index ID 0, page (1:1647), row 17. Test
> (ColumnOffsets <= (nextRec - pRec)) failed. Values are 1064 and 58.
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]
> CHECKDB found 0 allocation errors and 2 consistency errors in table
> 'rStk_ComponentRecep
tionTemp' (object ID 806345987).
> ====================
====================
===================
>
>
> It is weird because between 4:00PM and 4:05PM, something must have hapenned
> to render the "Dev" as incosistent. This has been hapenning since yesterday
> on random tables without any pattern.
>
> Inside my Maintenance Plan, under Integrity Tab --> selected 'Check
> database integrity' --> selected 'Exclude Indexes' --> selected 'Perform
> these checks before backing up ...'
>
> Moreover, the rest of the databases got backed up fine.
>
> What is causing the inconsistency ?
>
> How can I go about repairing it ?
>
> Thanks,
>
> Sameer.
>
> --
> Message posted via http://www.webservertalk.com

Sponsored Links