Errors while running DBCC CheckDb

I get the following errors when DBCC CheckDb is executed
on 'fmcomp003' database :
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1881) with latch type SH.
sysindexes failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
Values are 82 and 0.
DBCC results for 'fmcomp003'.Hi
DBCC CHECKDB has few arguments which you can use in this case
For more details please refer to BOL.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Hi,
I didn't understand the error as well as the severity of
the error. And please tell what is BOL.
Amit Chaudhary
>--Original Message--
>Hi
>DBCC CHECKDB has few arguments which you can use in this
case
>For more details please refer to BOL.
>
>"Amit Chaudhary" <anonymous@.discussions.microsoft.com>
wrote in message
> news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
SH.[vbcol=seagreen]
row[vbcol=seagreen]
>
>.
>|||Amit
Seems your table is corrupted. Do you have a last backup of the database?
Books OnLine comes with SQL Server installation.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2afca01c467e7$5fbe4d70$a401280a@.phx
.gbl...[vbcol=seagreen]
> Hi,
> I didn't understand the error as well as the severity of
> the error. And please tell what is BOL.
> Amit Chaudhary
> case
> wrote in message
> SH.
> row|||BOL is SQL Server documentation (Books On Line)..
Open BOL and search from the message# ( which is the SQL Error number)
8966...
You can also often get good information by simply googling the error number
as well...
To find the table name (from object id 2)
in query analyzer, use the database and
select object_name(2)
Object IDs < 100 are system tables..
IndexID of 0 means it is a table with no clustered index...
You will probably have to restore... You can also open a call to Microsoft
product Support ( PSS) ... I think the call now costs about $249.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||> And please tell what is BOL.
Books OnLine.
http://www.aspfaq.com/2229
http://www.aspfaq.com/
(Reverse address to reply.)|||What is the version of SQL used here?
If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if not
check event viewer for any information on hardware issues on the SQL server
.
--
Satya SKJ
"Amit Chaudhary" wrote:

> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Your sysindexes table has a corruption at the leaf level of the clustered
index. This is not repairable and your only option is to restore from your
last known good backup.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Repair cannot fix this error.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Satya SKJ" <satyaskj@.yahoo.co.uk> wrote in message
news:53F0C4CC-F7AE-4F72-8AE3-256FEB2C169B@.microsoft.com...
> What is the version of SQL used here?
> If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
> Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if
not check event viewer for any information on hardware issues on the SQL
server.[vbcol=seagreen]
> --
> --
> Satya SKJ
>
> "Amit Chaudhary" wrote:
>

Errors while running DBCC CheckDb

I get the following errors when DBCC CheckDb is executed
on 'fmcomp003' database :
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1881) with latch type SH.
sysindexes failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
Values are 82 and 0.
DBCC results for 'fmcomp003'.
Hi
DBCC CHECKDB has few arguments which you can use in this case
For more details please refer to BOL.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||Hi,
I didn't understand the error as well as the severity of
the error. And please tell what is BOL.
Amit Chaudhary
>--Original Message--
>Hi
>DBCC CHECKDB has few arguments which you can use in this
case
>For more details please refer to BOL.
>
>"Amit Chaudhary" <anonymous@.discussions.microsoft.com>
wrote in message[vbcol=seagreen]
>news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
SH.[vbcol=seagreen]
row
>
>.
>
|||Amit
Seems your table is corrupted. Do you have a last backup of the database?
Books OnLine comes with SQL Server installation.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2afca01c467e7$5fbe4d70$a401280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> I didn't understand the error as well as the severity of
> the error. And please tell what is BOL.
> Amit Chaudhary
> case
> wrote in message
> SH.
> row
|||BOL is SQL Server documentation (Books On Line)..
Open BOL and search from the message# ( which is the SQL Error number)
8966...
You can also often get good information by simply googling the error number
as well...
To find the table name (from object id 2)
in query analyzer, use the database and
select object_name(2)
Object IDs < 100 are system tables..
IndexID of 0 means it is a table with no clustered index...
You will probably have to restore... You can also open a call to Microsoft
product Support ( PSS) ... I think the call now costs about $249.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||> And please tell what is BOL.
Books OnLine.
http://www.aspfaq.com/2229
http://www.aspfaq.com/
(Reverse address to reply.)
|||What is the version of SQL used here?
If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if not check event viewer for any information on Hardware issues on the SQL server.
--
Satya SKJ
"Amit Chaudhary" wrote:

> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||Your sysindexes table has a corruption at the leaf level of the clustered
index. This is not repairable and your only option is to restore from your
last known good backup.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||Repair cannot fix this error.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Satya SKJ" <satyaskj@.yahoo.co.uk> wrote in message
news:53F0C4CC-F7AE-4F72-8AE3-256FEB2C169B@.microsoft.com...
> What is the version of SQL used here?
> If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
> Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if
not check event viewer for any information on Hardware issues on the SQL
server.[vbcol=seagreen]
> --
> --
> Satya SKJ
>
> "Amit Chaudhary" wrote:
sql

Errors while running DBCC CheckDb

I get the following errors when DBCC CheckDb is executed
on 'fmcomp003' database :
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1881) with latch type SH.
sysindexes failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
Values are 82 and 0.
DBCC results for 'fmcomp003'.Hi
DBCC CHECKDB has few arguments which you can use in this case
For more details please refer to BOL.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Hi,
I didn't understand the error as well as the severity of
the error. And please tell what is BOL.
Amit Chaudhary
>--Original Message--
>Hi
>DBCC CHECKDB has few arguments which you can use in this
case
>For more details please refer to BOL.
>
>"Amit Chaudhary" <anonymous@.discussions.microsoft.com>
wrote in message
>news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
>> I get the following errors when DBCC CheckDb is executed
>> on 'fmcomp003' database :
>> Server: Msg 8966, Level 16, State 1, Line 1
>> Could not read and latch page (1:1881) with latch type
SH.
>> sysindexes failed.
>> Server: Msg 8944, Level 16, State 1, Line 1
>> Table Corrupt: Object ID 2, index ID 0, page (1:1881),
row
>> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
>> Values are 82 and 0.
>> DBCC results for 'fmcomp003'.
>
>.
>|||Amit
Seems your table is corrupted. Do you have a last backup of the database?
Books OnLine comes with SQL Server installation.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2afca01c467e7$5fbe4d70$a401280a@.phx.gbl...
> Hi,
> I didn't understand the error as well as the severity of
> the error. And please tell what is BOL.
> Amit Chaudhary
> >--Original Message--
> >Hi
> >DBCC CHECKDB has few arguments which you can use in this
> case
> >For more details please refer to BOL.
> >
> >
> >"Amit Chaudhary" <anonymous@.discussions.microsoft.com>
> wrote in message
> >news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> >> I get the following errors when DBCC CheckDb is executed
> >> on 'fmcomp003' database :
> >> Server: Msg 8966, Level 16, State 1, Line 1
> >> Could not read and latch page (1:1881) with latch type
> SH.
> >> sysindexes failed.
> >> Server: Msg 8944, Level 16, State 1, Line 1
> >> Table Corrupt: Object ID 2, index ID 0, page (1:1881),
> row
> >> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> >> Values are 82 and 0.
> >> DBCC results for 'fmcomp003'.
> >>
> >
> >
> >.
> >|||BOL is SQL Server documentation (Books On Line)..
Open BOL and search from the message# ( which is the SQL Error number)
8966...
You can also often get good information by simply googling the error number
as well...
To find the table name (from object id 2)
in query analyzer, use the database and
select object_name(2)
Object IDs < 100 are system tables..
IndexID of 0 means it is a table with no clustered index...
You will probably have to restore... You can also open a call to Microsoft
product Support ( PSS) ... I think the call now costs about $249.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||> And please tell what is BOL.
Books OnLine.
http://www.aspfaq.com/2229
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Your sysindexes table has a corruption at the leaf level of the clustered
index. This is not repairable and your only option is to restore from your
last known good backup.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Repair cannot fix this error.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Satya SKJ" <satyaskj@.yahoo.co.uk> wrote in message
news:53F0C4CC-F7AE-4F72-8AE3-256FEB2C169B@.microsoft.com...
> What is the version of SQL used here?
> If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
> Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if
not check event viewer for any information on Hardware issues on the SQL
server.
> --
> --
> Satya SKJ
>
> "Amit Chaudhary" wrote:
> > I get the following errors when DBCC CheckDb is executed
> > on 'fmcomp003' database :
> > Server: Msg 8966, Level 16, State 1, Line 1
> > Could not read and latch page (1:1881) with latch type SH.
> > sysindexes failed.
> > Server: Msg 8944, Level 16, State 1, Line 1
> > Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> > 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> > Values are 82 and 0.
> > DBCC results for 'fmcomp003'.
> >
> >

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...
>
>

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 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.
>
>
|||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...
>
>

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 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.
>
>|||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:
>> 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.
>>
>>
>|||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...
>>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
>> 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.
>>
>>
>
>

Errors from DBCC CHECKDB not caught by CATCH

I'm having problems catching errors from DBCC CHECKDB even though the errors
have a severity level above 10. I'm using the "broken" database created by
Paul Randal,
http://blogs.msdn.com/sqlserverstorageengine/archive/2007/04/17/example-corrupt-database-to-play-with.aspx (see the zip file at the end).
Even though a "DBCC CHECKDB (broken)" results in two errors with severity
level 16 the following code will never end up in the CATCH block..
BEGIN TRY
DBCC CHECKDB(broken)
END TRY
BEGIN CATCH
SELECT
ERROR_NUMBER() AS ErrorNumber,
ERROR_SEVERITY() AS ErrorSeverity,
ERROR_STATE() AS ErrorState,
ERROR_PROCEDURE() AS ErrorProcedure,
ERROR_LINE() AS ErrorLine,
ERROR_MESSAGE() AS ErrorMessage;
END CATCH
Does anyone know if this is by design or a bug? I'm using SQL Server 2005
with Service Pack 2.Hi Allan,
I've reported it on connect as a bug.
Use @.@.ERROR instead and don't use BEGIN TRY.
The CATCH is never reached, in fact - if you using BEGIN TRY and DBCC
CHECKDB fails then it stays in the BEGIN block and if you check @.@.ERROR its
actually 0!
Tony.
--
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]
"Allan" <allan@.newsgroups.nospam> wrote in message
news:B2E2D4EC-7F2D-434C-9F0C-AEA328C57188@.microsoft.com...
> I'm having problems catching errors from DBCC CHECKDB even though the
> errors
> have a severity level above 10. I'm using the "broken" database created by
> Paul Randal,
> http://blogs.msdn.com/sqlserverstorageengine/archive/2007/04/17/example-corrupt-database-to-play-with.aspx
> (see the zip file at the end).
> Even though a "DBCC CHECKDB (broken)" results in two errors with severity
> level 16 the following code will never end up in the CATCH block..
> BEGIN TRY
> DBCC CHECKDB(broken)
> END TRY
> BEGIN CATCH
> SELECT
> ERROR_NUMBER() AS ErrorNumber,
> ERROR_SEVERITY() AS ErrorSeverity,
> ERROR_STATE() AS ErrorState,
> ERROR_PROCEDURE() AS ErrorProcedure,
> ERROR_LINE() AS ErrorLine,
> ERROR_MESSAGE() AS ErrorMessage;
> END CATCH
> Does anyone know if this is by design or a bug? I'm using SQL Server 2005
> with Service Pack 2.

Errors from DBCC CHECKDB not caught by CATCH

I'm having problems catching errors from DBCC CHECKDB even though the errors
have a severity level above 10. I'm using the "broken" database created by
Paul Randal,
http://blogs.msdn.com/sqlserverstor...-play-with.aspx (see the zip file at the end).
Even though a "DBCC CHECKDB (broken)" results in two errors with severity
level 16 the following code will never end up in the CATCH block..
BEGIN TRY
DBCC CHECKDB(broken)
END TRY
BEGIN CATCH
SELECT
ERROR_NUMBER() AS ErrorNumber,
ERROR_SEVERITY() AS ErrorSeverity,
ERROR_STATE() AS ErrorState,
ERROR_PROCEDURE() AS ErrorProcedure,
ERROR_LINE() AS ErrorLine,
ERROR_MESSAGE() AS ErrorMessage;
END CATCH
Does anyone know if this is by design or a bug? I'm using SQL Server 2005
with Service Pack 2.Hi Allan,
I've reported it on connect as a bug.
Use @.@.ERROR instead and don't use BEGIN TRY.
The CATCH is never reached, in fact - if you using BEGIN TRY and DBCC
CHECKDB fails then it stays in the BEGIN block and if you check @.@.ERROR its
actually 0!
Tony.
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]
"Allan" <allan@.newsgroups.nospam> wrote in message
news:B2E2D4EC-7F2D-434C-9F0C-AEA328C57188@.microsoft.com...
> I'm having problems catching errors from DBCC CHECKDB even though the
> errors
> have a severity level above 10. I'm using the "broken" database created by
> Paul Randal,
> http://blogs.msdn.com/sqlserverstor...-play-with.aspx
> (see the zip file at the end).
> Even though a "DBCC CHECKDB (broken)" results in two errors with severity
> level 16 the following code will never end up in the CATCH block..
> BEGIN TRY
> DBCC CHECKDB(broken)
> END TRY
> BEGIN CATCH
> SELECT
> ERROR_NUMBER() AS ErrorNumber,
> ERROR_SEVERITY() AS ErrorSeverity,
> ERROR_STATE() AS ErrorState,
> ERROR_PROCEDURE() AS ErrorProcedure,
> ERROR_LINE() AS ErrorLine,
> ERROR_MESSAGE() AS ErrorMessage;
> END CATCH
> Does anyone know if this is by design or a bug? I'm using SQL Server 2005
> with Service Pack 2.

Errors during DBCC How do I correct them

I've run a DBCC checkDB against my database and received the following
errors. I'm sure to go about correct them. Can someone give me help. My
errors are below:
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191165440 owned by data record
identified by RID = (1:124:6) id = 646293362 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191230976 owned by data record
identified by RID = (1:124:7) id = 646293362 and indid = 3.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191296512 owned by data record
identified by RID = (1:124:8) id = 646293362 and indid = 4.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191362048 owned by data record
identified by RID = (1:124:9) id = 646293362 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191427584 owned by data record
identified by RID = (1:124:10) id = 646293362 and indid = 6.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191493120 owned by data record
identified by RID = (1:124:11) id = 646293362 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14433976320 owned by data record
identified by RID = (1:148112:16) id = 1908201848 and indid = 10.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 3, text ID 14433976320 does not match its reference from
page (1:124), slot 6.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or
image node page (1:3703084), slot 3, text ID 14433976320 is pointed to by
page (1:124), slot 6 and by page (1:3703084), slot 4.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 5, text ID 14191230976 is referenced by page (1:124), slot
7, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 6, text ID 14191296512 is referenced by page (1:124), slot
8, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 7, text ID 14191362048 is referenced by page (1:124), slot
9, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 8, text ID 14191427584 is referenced by page (1:124), slot
10, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 9, text ID 14191493120 is referenced by page (1:124), slot
11, but was not seen in the scan.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:4559824), slot 0, text ID 14190772224 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:4559826), slot 1, text ID 14191427584 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:4559829), slot 0, text ID 14191296512 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:4559829), slot 1, text ID 14191362048 is not referenced.
DBCC results for 'Claims'.
ThanksSearch in Books Online for the error numbers returned. There are specific re
commendations in Books
Online for each error. Also see: http://www.karaszi.com/SQLServer/in.../>
pect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Larry Bird" <LarryBird@.discussions.microsoft.com> wrote in message
news:51E5391F-4354-4E01-B77B-3D1AED2CBC7E@.microsoft.com...
> I've run a DBCC checkDB against my database and received the following
> errors. I'm sure to go about correct them. Can someone give me help. My
> errors are below:
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191165440 owned by data record
> identified by RID = (1:124:6) id = 646293362 and indid = 2.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191230976 owned by data record
> identified by RID = (1:124:7) id = 646293362 and indid = 3.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191296512 owned by data record
> identified by RID = (1:124:8) id = 646293362 and indid = 4.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191362048 owned by data record
> identified by RID = (1:124:9) id = 646293362 and indid = 5.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191427584 owned by data record
> identified by RID = (1:124:10) id = 646293362 and indid = 6.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191493120 owned by data record
> identified by RID = (1:124:11) id = 646293362 and indid = 7.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14433976320 owned by data record
> identified by RID = (1:148112:16) id = 1908201848 and indid = 10.
> Server: Msg 8961, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 3, text ID 14433976320 does not match its reference from
> page (1:124), slot 6.
> Server: Msg 8974, Level 16, State 1, Line 1
> Text node referenced by more than one node. Object ID 2, text, ntext, or
> image node page (1:3703084), slot 3, text ID 14433976320 is pointed to by
> page (1:124), slot 6 and by page (1:3703084), slot 4.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 5, text ID 14191230976 is referenced by page (1:124), sl
ot
> 7, but was not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 6, text ID 14191296512 is referenced by page (1:124), sl
ot
> 8, but was not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 7, text ID 14191362048 is referenced by page (1:124), sl
ot
> 9, but was not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 8, text ID 14191427584 is referenced by page (1:124), sl
ot
> 10, but was not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 9, text ID 14191493120 is referenced by page (1:124), sl
ot
> 11, but was not seen in the scan.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:4559824), slot 0, text ID 14190772224 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:4559826), slot 1, text ID 14191427584 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:4559829), slot 0, text ID 14191296512 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:4559829), slot 1, text ID 14191362048 is not referenced.
> DBCC results for 'Claims'.
>
> Thanks
>

Errors during DBCC How do I correct them

I've run a DBCC checkDB against my database and received the following
errors. I'm sure to go about correct them. Can someone give me help. My
errors are below:
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191165440 owned by data record
identified by RID = (1:124:6) id = 646293362 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191230976 owned by data record
identified by RID = (1:124:7) id = 646293362 and indid = 3.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191296512 owned by data record
identified by RID = (1:124:8) id = 646293362 and indid = 4.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191362048 owned by data record
identified by RID = (1:124:9) id = 646293362 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191427584 owned by data record
identified by RID = (1:124:10) id = 646293362 and indid = 6.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14191493120 owned by data record
identified by RID = (1:124:11) id = 646293362 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 14433976320 owned by data record
identified by RID = (1:148112:16) id = 1908201848 and indid = 10.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 3, text ID 14433976320 does not match its reference from
page (1:124), slot 6.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or
image node page (1:3703084), slot 3, text ID 14433976320 is pointed to by
page (1:124), slot 6 and by page (1:3703084), slot 4.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 5, text ID 14191230976 is referenced by page (1:124), slot
7, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 6, text ID 14191296512 is referenced by page (1:124), slot
8, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 7, text ID 14191362048 is referenced by page (1:124), slot
9, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 8, text ID 14191427584 is referenced by page (1:124), slot
10, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:3703084), slot 9, text ID 14191493120 is referenced by page (1:124), slot
11, but was not seen in the scan.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:4559824), slot 0, text ID 14190772224 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:4559826), slot 1, text ID 14191427584 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:4559829), slot 0, text ID 14191296512 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page
(1:4559829), slot 1, text ID 14191362048 is not referenced.
DBCC results for 'Claims'.
ThanksDear,
Check he tables id and run dbcc showcontig on that paticulat table to
get the full information about the error.
U can repair the database but before u run repair check it witl dbcc
showcontig.
Also run dbcc checktable --checks intregity of a specified constraint.
Run DBCC Checkalloc --checks the consistancy of disk space allocation
structures for particular database.
U can also resolve this problem by reindexing the tables.
or rum DBCC CHECKDB(Repair_fast,repair_rebuild,repair_allow_data_loss)
before u run this command change the database mode to single user.
from
Doller|||Search in Books Online for the error numbers returned. There are specific recommendations in Books
Online for each error. Also see: http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Larry Bird" <LarryBird@.discussions.microsoft.com> wrote in message
news:51E5391F-4354-4E01-B77B-3D1AED2CBC7E@.microsoft.com...
> I've run a DBCC checkDB against my database and received the following
> errors. I'm sure to go about correct them. Can someone give me help. My
> errors are below:
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191165440 owned by data record
> identified by RID = (1:124:6) id = 646293362 and indid = 2.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191230976 owned by data record
> identified by RID = (1:124:7) id = 646293362 and indid = 3.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191296512 owned by data record
> identified by RID = (1:124:8) id = 646293362 and indid = 4.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191362048 owned by data record
> identified by RID = (1:124:9) id = 646293362 and indid = 5.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191427584 owned by data record
> identified by RID = (1:124:10) id = 646293362 and indid = 6.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14191493120 owned by data record
> identified by RID = (1:124:11) id = 646293362 and indid = 7.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 14433976320 owned by data record
> identified by RID = (1:148112:16) id = 1908201848 and indid = 10.
> Server: Msg 8961, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 3, text ID 14433976320 does not match its reference from
> page (1:124), slot 6.
> Server: Msg 8974, Level 16, State 1, Line 1
> Text node referenced by more than one node. Object ID 2, text, ntext, or
> image node page (1:3703084), slot 3, text ID 14433976320 is pointed to by
> page (1:124), slot 6 and by page (1:3703084), slot 4.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 5, text ID 14191230976 is referenced by page (1:124), slot
> 7, but was not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 6, text ID 14191296512 is referenced by page (1:124), slot
> 8, but was not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 7, text ID 14191362048 is referenced by page (1:124), slot
> 9, but was not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 8, text ID 14191427584 is referenced by page (1:124), slot
> 10, but was not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:3703084), slot 9, text ID 14191493120 is referenced by page (1:124), slot
> 11, but was not seen in the scan.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:4559824), slot 0, text ID 14190772224 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:4559826), slot 1, text ID 14191427584 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:4559829), slot 0, text ID 14191296512 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:4559829), slot 1, text ID 14191362048 is not referenced.
> DBCC results for 'Claims'.
>
> Thanks
>

Errors 8908, 8951, 8952, 8956

A database has presented the above errors. I have run DBCC CHECKDB, which r
evealed the affected table, then re-ran with REPAIR_REBUILD and the index co
rruption was corrected. Several days passed and the same errors appeared on
a different table. REPAIR
_REBUILD corrected the corruption again.
My questions:
What could be causing this?
Is it hardware related, like RAM or disk I/O?
Could it be application related?
How can I determine the cause and prevent future corruption?
Thanks a million!Yes, you very likely have a bad disk or IO controller. Data does not appear
to be written to the disks in a reliable fashion.
Make sure any SQL hardware is on the Windows hardware Compatibility List
(HCL). HCL certified gear with signed drivers should not exhibit this
behavior.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Tim Ermlich" <termlich(***take this out***)@.allenbrook.com> wrote in
message news:CAA5B69B-5B7C-43FF-834D-23546F0BE27F@.microsoft.com...
> A database has presented the above errors. I have run DBCC CHECKDB, which
revealed the affected table, then re-ran with REPAIR_REBUILD and the index
corruption was corrected. Several days passed and the same errors appeared
on a different table. REPAIR_REBUILD corrected the corruption again.
> My questions:
> What could be causing this?
> Is it hardware related, like RAM or disk I/O?
> Could it be application related?
> How can I determine the cause and prevent future corruption?
> Thanks a million!

Errori SQL

Salve a tutti,
io ho un problema di questo genere:
eseguendo il comando DBCC CHECKDB('DATABASE') il motore sql mi restituisce
questi tipi di allarmi:

Server: messaggio 8909, livello 16, stato 1, riga 1 Errore di tabella: ID di
oggetto 1093578934, ID di indice 0, ID di pagina (1:7). L'ID di pagina
nell'intestazione di pagina (1:23063).

Per l'oggetto 'TABELLA1' sono disponibili 238679 righe in 3144 pagine.
CHECKDB ha rilevato 1 errori di allocazione e 0 errori di consistenza nella
tabella 'TABELLA1' (ID di oggetto 1093578934).

CHECKDB ha rilevato 1 errori di allocazione e 0 errori di consistenza nel
database 'DATABASE'. Esecuzione DBCC completata. Se sono stati visualizzati
messaggi di errore DBCC, rivolgersi all'amministratore di sistema.

Chi mi riesce a dare una spiegazione ?

Grazie a tutti

SalutiFr4nc3sc0 (nontidicolamia@.email.no) writes:
> Salve a tutti,
> io ho un problema di questo genere:
> eseguendo il comando DBCC CHECKDB('DATABASE') il motore sql mi restituisce
> questi tipi di allarmi:
> Server: messaggio 8909, livello 16, stato 1, riga 1 Errore di tabella:
> ID di oggetto 1093578934, ID di indice 0, ID di pagina (1:7). L'ID di
> pagina nell'intestazione di pagina (1:23063).
> Per l'oggetto 'TABELLA1' sono disponibili 238679 righe in 3144 pagine.
> CHECKDB ha rilevato 1 errori di allocazione e 0 errori di consistenza
> nella tabella 'TABELLA1' (ID di oggetto 1093578934).
> CHECKDB ha rilevato 1 errori di allocazione e 0 errori di consistenza
> nel database 'DATABASE'. Esecuzione DBCC completata. Se sono stati
> visualizzati messaggi di errore DBCC, rivolgersi all'amministratore di
> sistema.

Cerca per 8909 in SQL Server Books Online. C' un articulo con informazione
di questo messagio. In somma: multo probable che c' un problema con il
hardware.

(Search for 8909 in SQL Server Books Online. There is an article with
information about this error. In summary: it is very likely that you
have a hardware problem.)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"Erland Sommarskog" <esquel@.sommarskog.se> ha scritto nel messaggio
news:Xns95A8CD98912AYazorman@.127.0.0.1...
> Fr4nc3sc0 (nontidicolamia@.email.no) writes:
> Cerca per 8909 in SQL Server Books Online. C' un articulo con
informazione
> di questo messagio. In somma: multo probable che c' un problema con il
> hardware.

Grazie per la risposta. Anche io avevo pensato ad un problema hardware.

A presto, ciao
fs