DBCC Error

Anyone seen this before? What causes it? How do I fix it?
Thanks!!
Richard
DBCC results for 'ivTransitItems'.
Msg 2537, Level 16, State 24, Line 5
Table error: object ID 295528682, index ID 0, partition ID 19367767703552,
alloc unit ID 19367767703552 (type In-row data), page (1:22320), row 0. The
record check (valid record length) failed. The values are 112 and 108.
Msg 8929, Level 16, State 1, Line 5
Object ID 295528682, index ID 0, partition ID 19367767703552, alloc unit ID
19367767703552 (type In-row data): Errors found in off-row data with ID
3755409408 owned by data record identified by RID = (1:22320:0)
Msg 2537, Level 16, State 24, Line 5Hi,
Can you try doing these:-
1. Do a DBCC DBREINDEX and after that run a DBCC CHECKTABLE and see if error
persists
2. If error Persists then do a DBCC CHECKTABLE with REPAIR_REBUILD
3. If you still have error then take a backup of database and then execute
DBCC CHECKDB WITH REPAIR_ALLOW_DATA_LOSS
To use the repair optiion database must be set to single user mode.
Thanks
Hari
SQL Server MVP
"Richard Douglass" wrote:

> Anyone seen this before? What causes it? How do I fix it?
> Thanks!!
> Richard
>
> DBCC results for 'ivTransitItems'.
> Msg 2537, Level 16, State 24, Line 5
> Table error: object ID 295528682, index ID 0, partition ID 19367767703552,
> alloc unit ID 19367767703552 (type In-row data), page (1:22320), row 0. Th
e
> record check (valid record length) failed. The values are 112 and 108.
> Msg 8929, Level 16, State 1, Line 5
> Object ID 295528682, index ID 0, partition ID 19367767703552, alloc unit I
D
> 19367767703552 (type In-row data): Errors found in off-row data with ID
> 3755409408 owned by data record identified by RID = (1:22320:0)
> Msg 2537, Level 16, State 24, Line 5
>
>|||Actually, before you do any of these, if you have a backup you should
restore from backup. This is much safer than running the DBCC commands you
list below (especially the third one), as those can result in dataloss
which could make your database totally inconsistent.
Thanks,
Marcel.
On Wed, 13 Sep 2006 16:11:01 -0700, Hari Prasad wrote:
[vbcol=seagreen]
> Hi,
> Can you try doing these:-
> 1. Do a DBCC DBREINDEX and after that run a DBCC CHECKTABLE and see if err
or
> persists
> 2. If error Persists then do a DBCC CHECKTABLE with REPAIR_REBUILD
> 3. If you still have error then take a backup of database and then execute
> DBCC CHECKDB WITH REPAIR_ALLOW_DATA_LOSS
> To use the repair optiion database must be set to single user mode.
> Thanks
> Hari
> SQL Server MVP
> "Richard Douglass" wrote:
>