Sunday, March 11, 2012

errors in sysindexes table

Hello,
I have a database that has errors in sysindexes table. If i run DBCC CHECKDB
('dbname',repair_allow_data_loss), it gives:
DBCC results for 'sysindexes'.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
All the errors are from the same table named ReqCb.
What i've tried:
1. I've created a new table and inserted all the records from ReqCb. All
goes well
2. Drop PK and other indexes on ReqCb. All goes well
3. CHECKDBB again, some errors, some number of errors.
4. DELETE all records.
5. DROP all constraints and foreign keys, all triggers and defaults.
7. CHECKDBB again, some errors, some number of errors.
Error message:
DROP TABLE ReqCb. Error: ODBC error: [Microsoft][ODBC SQL Server
Driver][SQL Server]Page (1:5407), slot 0 for text, ntext, or image node
does
not exist
Can someone help me to find step 8? or 9, or ...
Best regards
Hugo Sousa
PS: I have a backup of the initial DB, so if i did something wrong, i can
revert to the initial situation.A shot in the dark here but have you tried a DBCC DBREINDEX ?
"We are all worms. But I believe that I am a glow-worm."
Winston Churchill
"HugoSousa" wrote:

> Hello,
> I have a database that has errors in sysindexes table. If i run DBCC CHECK
DB
> ('dbname',repair_allow_data_loss), it gives:
> DBCC results for 'sysindexes'.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> All the errors are from the same table named ReqCb.
> What i've tried:
> 1. I've created a new table and inserted all the records from ReqCb. All
> goes well
> 2. Drop PK and other indexes on ReqCb. All goes well
> 3. CHECKDBB again, some errors, some number of errors.
> 4. DELETE all records.
> 5. DROP all constraints and foreign keys, all triggers and defaults.
> 7. CHECKDBB again, some errors, some number of errors.
> Error message:
> DROP TABLE ReqCb. Error: ODBC error: [Microsoft][ODBC SQL Server
> Driver][SQL Server]Page (1:5407), slot 0 for text, ntext, or image nod
e does
> not exist
> Can someone help me to find step 8? or 9, or ...
>
> Best regards
> Hugo Sousa
> PS: I have a backup of the initial DB, so if i did something wrong, i can
> revert to the initial situation.
>
>|||Same error:
Server: Msg 7105, Level 22, State 6, Line 1
Page (1:5407), slot 0 for text, ntext, or image node does not exist.
Connection Broken
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:D96523A1-7759-432C-AAA6-F3BC19CBBBD2@.microsoft.com...
>A shot in the dark here but have you tried a DBCC DBREINDEX ?
> "We are all worms. But I believe that I am a glow-worm."
> Winston Churchill
>
> "HugoSousa" wrote:
>
>|||As the error message indicates, errors in the sysindexes system table are
not repairable. You might try doing an UPDATE STATISTICS with FULLSCAN on
your indexes, since the column in sysindexes that is corrupt is the
statistics BLOB. If that doens't work, tour only option at this point is to
restore from backup.
Thanks,
--
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"HugoSousa" <hugosousa@.removethis.gestexper.pt> wrote in message
news:u2Gggb$IFHA.580@.TK2MSFTNGP15.phx.gbl...
> Same error:
> Server: Msg 7105, Level 22, State 6, Line 1
> Page (1:5407), slot 0 for text, ntext, or image node does not exist.
> Connection Broken
>
> "Peter" <Peter@.discussions.microsoft.com> wrote in message
> news:D96523A1-7759-432C-AAA6-F3BC19CBBBD2@.microsoft.com...
>
>

No comments:

Post a Comment