DBCC CHECKDB

Hello NG,
I need some assistance in the subject "repairing".
I always thought,
DBCC CHECKDB (' dbname ', REPAIR_ALLOW_DATA_LOSS)
would be the worst, which one could do to an SQL server data base.
But our installation (8.00.760 = SQL2000 with SP3 on W2000Server)
refuses accomplishing the repair even with a maximum loss and
answers:
[ 4 ] Data base XenoxDB: Data and
Indexverkn?pfung?berpr?fen... [ Microsoft SQL DMO (ODBC SQLState:
42000) ] Error 8929: [ Microsoft][ODBC SQL server Driver][SQL
Server]Objekt ID 2: Error in text ID 195789324288 found, their owner
data record RID = (1:1317:3) ID = 861506398 and indid = 1 is. [
Microsoft][ODBC SQL server Driver][SQL Server]Tabellenfehler: Object
ID 2. The text -, ntext or image knots on side (1:5999), Slot 0, text
ID 195789324288 does not tune with its reference from side (1:10742),
Slot 10?berein. [ Microsoft][ODBC SQL server Driver][SQL
Server]Tabellenfehler: Object ID 2. The text -, ntext or image knots
on side (1:10742), Slot 10, text ID 58350370816 does not tune with its
reference from side (1:1317), Slot 3?berein. [ Microsoft][ODBC SQL
server Driver][SQL server ] the RH Pa IR stage in the DBCC instruction
caused that this elimination of errors became to?bergangen. [
Microsoft][ODBC SQL server Driver][SQL server ] the RH Pa IR stage in
the DBCC instruction caused that this elimination of errors became
to?bergangen. [ Microsoft][ODBC SQL server Driver][SQL server ] the RH
Pa IR stage in the DBCC instruction caused that this elimination of
errors became to?bergangen. [ Microsoft][ODBC SQL server Driver][SQL
Server]CHECKDB found 0 reservation errors and 3 consistency error in
the sysindexes table (object ID 2). [ Microsoft][ODBC SQL server
Driver][SQL Server]CHECKDB found 0 reservation errors and 3
consistency error in the XenoxDB data base.
The following errors arose:
[ Microsoft][ODBC SQL server Driver][SQL Server]Objekt ID 2: Error in
text ID 195789324288 found, their owner data record RID = (1:1317:3)
ID = 861506398 and indid = 1 is. [ Microsoft][ODBC SQL server
Driver][SQL Server]Tabellenfehler: Object ID 2. The text -, ntext or
image knots on side (1:5999), Slot 0, text ID 195789324288 does not
tune with its reference from side (1:10742), Slot 10?berein. [
Microsoft][ODBC SQL server Driver][SQL Server]Tabellenfehler: Object
ID 2. The text -, ntext or image knots on side (1:10742), Slot 10,
text ID 58350370816 does not tune with its reference from side
(1:1317), Slot 3?berein. [ Microsoft][ODBC SQL server Driver][SQL
server ] the RH Pa IR stage in the DBCC instruction caused that this
elimination of errors became to?bergangen. [ Microsoft][ODBC SQL
server Driver][SQL server ] the RH Pa IR stage in the DBCC instruction
caused that this elimination of errors became to?bergangen. [
Microsoft][ODBC SQL server Driver][SQL server ] the RH Pa IR stage in
the DBCC instruction caused that this elimination of errors became
to?bergangen. [ Microsoft][ODBC SQL server Driver][SQL Server]CHECKDB
found 0 reservation errors and 3 consistency error in the sysindexes
table (object ID 2). [ Microsoft][ODBC SQL server Driver][SQL
Server]CHECKDB found 0 reservation errors and 3 consistency error in
the XenoxDB data base. ** Ausf?hrungsdauer: 0 Std, 0 min, 3 sec. **
Someone an idea, how to repair the index nevertheless - perhaps
also on detours?
Best Regards
Thomas
Thomas,
I assume that you went through the process describe in the Books Online for
error 8929. At the end, after checking hardware, restoring a good backup,
and running DBCC with the appropriate repair option, it says:
"If running DBCC CHECKDB with one of the repair clauses does not correct the
problem, contact your primary support provider."
Russell Fields
"Thomas Prost" <thomas.prost@.rwth-aachen.de> wrote in message
news:4124ADCB.4080006@.rwth-aachen.de...
> Hello NG,
> I need some assistance in the subject "repairing".
> I always thought,
> --
> DBCC CHECKDB (' dbname ', REPAIR_ALLOW_DATA_LOSS)
> --
> would be the worst, which one could do to an SQL server data base.
> But our installation (8.00.760 = SQL2000 with SP3 on W2000Server)
> refuses accomplishing the repair even with a maximum loss and
> answers:
> --
> [ 4 ] Data base XenoxDB: Data and
> Indexverkn?pfung?berpr?fen... [ Microsoft SQL DMO (ODBC SQLState:
> 42000) ] Error 8929: [ Microsoft][ODBC SQL server Driver][SQL
> Server]Objekt ID 2: Error in text ID 195789324288 found, their owner
> data record RID = (1:1317:3) ID = 861506398 and indid = 1 is. [
> Microsoft][ODBC SQL server Driver][SQL Server]Tabellenfehler: Object
> ID 2. The text -, ntext or image knots on side (1:5999), Slot 0, text
> ID 195789324288 does not tune with its reference from side (1:10742),
> Slot 10?berein. [ Microsoft][ODBC SQL server Driver][SQL
> Server]Tabellenfehler: Object ID 2. The text -, ntext or image knots
> on side (1:10742), Slot 10, text ID 58350370816 does not tune with its
> reference from side (1:1317), Slot 3?berein. [ Microsoft][ODBC SQL
> server Driver][SQL server ] the RH Pa IR stage in the DBCC instruction
> caused that this elimination of errors became to?bergangen. [
> Microsoft][ODBC SQL server Driver][SQL server ] the RH Pa IR stage in
> the DBCC instruction caused that this elimination of errors became
> to?bergangen. [ Microsoft][ODBC SQL server Driver][SQL server ] the RH
> Pa IR stage in the DBCC instruction caused that this elimination of
> errors became to?bergangen. [ Microsoft][ODBC SQL server Driver][SQL
> Server]CHECKDB found 0 reservation errors and 3 consistency error in
> the sysindexes table (object ID 2). [ Microsoft][ODBC SQL server
> Driver][SQL Server]CHECKDB found 0 reservation errors and 3
> consistency error in the XenoxDB data base.
> The following errors arose:
> [ Microsoft][ODBC SQL server Driver][SQL Server]Objekt ID 2: Error in
> text ID 195789324288 found, their owner data record RID = (1:1317:3)
> ID = 861506398 and indid = 1 is. [ Microsoft][ODBC SQL server
> Driver][SQL Server]Tabellenfehler: Object ID 2. The text -, ntext or
> image knots on side (1:5999), Slot 0, text ID 195789324288 does not
> tune with its reference from side (1:10742), Slot 10?berein. [
> Microsoft][ODBC SQL server Driver][SQL Server]Tabellenfehler: Object
> ID 2. The text -, ntext or image knots on side (1:10742), Slot 10,
> text ID 58350370816 does not tune with its reference from side
> (1:1317), Slot 3?berein. [ Microsoft][ODBC SQL server Driver][SQL
> server ] the RH Pa IR stage in the DBCC instruction caused that this
> elimination of errors became to?bergangen. [ Microsoft][ODBC SQL
> server Driver][SQL server ] the RH Pa IR stage in the DBCC instruction
> caused that this elimination of errors became to?bergangen. [
> Microsoft][ODBC SQL server Driver][SQL server ] the RH Pa IR stage in
> the DBCC instruction caused that this elimination of errors became
> to?bergangen. [ Microsoft][ODBC SQL server Driver][SQL Server]CHECKDB
> found 0 reservation errors and 3 consistency error in the sysindexes
> table (object ID 2). [ Microsoft][ODBC SQL server Driver][SQL
> Server]CHECKDB found 0 reservation errors and 3 consistency error in
> the XenoxDB data base. ** Ausf?hrungsdauer: 0 Std, 0 min, 3 sec. **
> Someone an idea, how to repair the index nevertheless - perhaps
> also on detours?
> Best Regards
> Thomas
>
|||Russel,
I would have been the happiest man alive, if Id found any of that
books, you mention.
I didnt find any suggestions, how to get rid of errror 8929 :-(
I checked hardware, but the restore of a good backup would cause the
same data loss, that checkdb threatens with.
So, the contact your provider-option seemed to be the "last resort" -
but the answers of MS Germany didnt help us at all :-((
Best Regards
Thomas
Russell Fields schrieb:

>Thomas,
>I assume that you went through the process describe in the Books Online for
>error 8929. At the end, after checking hardware, restoring a good backup,
>and running DBCC with the appropriate repair option, it says:
>"If running DBCC CHECKDB with one of the repair clauses does not correct the
>problem, contact your primary support provider."
>Russell Fields
>"Thomas Prost" <thomas.prost@.rwth-aachen.de> wrote in message
>news:4124ADCB.4080006@.rwth-aachen.de...
>
>
>
|||Have you tried running checkdb several times in succession? There are some
error combinations that the SQL Server 2000 repair isn't able to fix on the
first attempt (as other errors prvent the fix from running). I don't see
anything in the output you've posted that would suggest checkdb would have a
problem repairing these. Can you post the output from repair?
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Thomas Prost" <thomas.prost@.rwth-aachen.de> wrote in message
news:4124BADD.4040502@.rwth-aachen.de...[vbcol=seagreen]
> Russel,
> I would have been the happiest man alive, if Id found any of that
> books, you mention.
> I didnt find any suggestions, how to get rid of errror 8929 :-(
> I checked hardware, but the restore of a good backup would cause the
> same data loss, that checkdb threatens with.
> So, the contact your provider-option seemed to be the "last resort" -
> but the answers of MS Germany didnt help us at all :-((
> Best Regards
> Thomas
>
> Russell Fields schrieb:
for[vbcol=seagreen]
backup,[vbcol=seagreen]
the
>
|||Paul S Randal [MS] schrieb:
> Have you tried running checkdb several times in succession? There are some
> error combinations that the SQL Server 2000 repair isn't able to fix on the
> first attempt (as other errors prvent the fix from running). I don't see
> anything in the output you've posted that would suggest checkdb would have a
> problem repairing these. Can you post the output from repair?
> Regards.
>
Paul,
hope youre still watching, so you can see what our SQL Server did
to me. I dont know, how many times I ran the procedures in
succussion :-(
Best Regards
Thomas
FYI:
--CHECKDB without repair--
Server: Nachr.-Nr. 8929, Schweregrad 16, Status 1, Zeile 3
Objekt-ID 2: Fehler in Text-ID 195789324288 gefunden, deren
Besitzer Datensatz RID = (1:1317:3) id = 861506398 and indid = 1 ist.
Server: Nachr.-Nr. 8961, Schweregrad 16, Status 1, Zeile 3
Tabellenfehler: Objekt-ID 2. Der text-, ntext- oder image-Knoten
auf Seite (1:5999), Slot 0, Text-ID 195789324288 stimmt nicht mit
seinem Verweis von Seite (1:10742), Slot 10 berein.
Server: Nachr.-Nr. 8961, Schweregrad 16, Status 1, Zeile 3
Tabellenfehler: Objekt-ID 2. Der text-, ntext- oder image-Knoten
auf Seite (1:10742), Slot 10, Text-ID 58350370816 stimmt nicht mit
seinem Verweis von Seite (1:1317), Slot 3 berein.
DBCC-Ergebnis fr 'XenoxDB'.
DBCC-Ergebnis fr 'sysobjects'.
Es sind 3908 Zeilen in 71 Seiten fr das sysobjects-Objekt vorhanden.
DBCC-Ergebnis fr 'sysindexes'.
Es sind 4919 Zeilen in 276 Seiten fr das sysindexes-Objekt vorhanden.
CHECKDB hat 0 Reservierungsfehler und 3 Konsistenzfehler in der
sysindexes-Tabelle gefunden (Objekt-ID 2).
DBCC-Ergebnis fr 'syscolumns'.
Es sind 8733 Zeilen in 192 Seiten fr das syscolumns-Objekt vorhanden.
DBCC-Ergebnis fr 'systypes'.
Es sind 26 Zeilen in 1 Seiten fr das systypes-Objekt vorhanden.
DBCC-Ergebnis fr 'syscomments'.
Es sind 2828 Zeilen in 63 Seiten fr das syscomments-Objekt vorhanden.
----and so on ...
--CHECKDB repair_allow_data_loss--
Server: Nachr.-Nr. 8929, Schweregrad 16, Status 1, Zeile 3
Objekt-ID 2: Fehler in Text-ID 195789324288 gefunden, deren
Besitzer Datensatz RID = (1:1317:3) id = 861506398 and indid = 1 ist.
Server: Nachr.-Nr. 8961, Schweregrad 16, Status 1, Zeile 3
Tabellenfehler: Objekt-ID 2. Der text-, ntext- oder image-Knoten
auf Seite (1:5999), Slot 0, Text-ID 195789324288 stimmt nicht mit
seinem Verweis von Seite (1:10742), Slot 10 berein.
Server: Nachr.-Nr. 8961, Schweregrad 16, Status 1, Zeile 3
Tabellenfehler: Objekt-ID 2. Der text-, ntext- oder image-Knoten
auf Seite (1:10742), Slot 10, Text-ID 58350370816 stimmt nicht mit
seinem Verweis von Seite (1:1317), Slot 3 berein.
DBCC-Ergebnis fr 'XenoxDB'.
DBCC-Ergebnis fr 'sysobjects'.
Es sind 3908 Zeilen in 71 Seiten fr das sysobjects-Objekt vorhanden.
DBCC-Ergebnis fr 'sysindexes'.
Die REPAIR-Stufe in der DBCC-Anweisung hat bewirkt, dass
diese Fehlerbehebung bergangen wurde.
Die REPAIR-Stufe in der DBCC-Anweisung hat bewirkt, dass
diese Fehlerbehebung bergangen wurde.
Die REPAIR-Stufe in der DBCC-Anweisung hat bewirkt, dass
diese Fehlerbehebung bergangen wurde.
Es sind 4919 Zeilen in 276 Seiten fr das sysindexes-Objekt vorhanden.
CHECKDB hat 0 Reservierungsfehler und 3 Konsistenzfehler in der
sysindexes-Tabelle gefunden (Objekt-ID 2).
DBCC-Ergebnis fr 'syscolumns'.
Es sind 8733 Zeilen in 192 Seiten fr das syscolumns-Objekt vorhanden.
DBCC-Ergebnis fr 'systypes'.
--Rest is similar to above output !
|||Ah - the errors are in sysindexes so that may be stopping from repairing
them. You're going to need to call Product Support to help you as we can't
do this through Usenet.
Thanks and regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Thomas Prost" <thomas.prost@.rwth-aachen.de> wrote in message
news:41347038.8040909@.rwth-aachen.de...[vbcol=seagreen]
> Paul S Randal [MS] schrieb:
some[vbcol=seagreen]
the[vbcol=seagreen]
have a
> Paul,
> hope youre still watching, so you can see what our SQL Server did
> to me. I dont know, how many times I ran the procedures in
> succussion :-(
> Best Regards
> Thomas
>
> FYI:
> --CHECKDB without repair--
> Server: Nachr.-Nr. 8929, Schweregrad 16, Status 1, Zeile 3
> Objekt-ID 2: Fehler in Text-ID 195789324288 gefunden, deren
> Besitzer Datensatz RID = (1:1317:3) id = 861506398 and indid = 1 ist.
> Server: Nachr.-Nr. 8961, Schweregrad 16, Status 1, Zeile 3
> Tabellenfehler: Objekt-ID 2. Der text-, ntext- oder image-Knoten
> auf Seite (1:5999), Slot 0, Text-ID 195789324288 stimmt nicht mit
> seinem Verweis von Seite (1:10742), Slot 10 berein.
> Server: Nachr.-Nr. 8961, Schweregrad 16, Status 1, Zeile 3
> Tabellenfehler: Objekt-ID 2. Der text-, ntext- oder image-Knoten
> auf Seite (1:10742), Slot 10, Text-ID 58350370816 stimmt nicht mit
> seinem Verweis von Seite (1:1317), Slot 3 berein.
> DBCC-Ergebnis fr 'XenoxDB'.
> DBCC-Ergebnis fr 'sysobjects'.
> Es sind 3908 Zeilen in 71 Seiten fr das sysobjects-Objekt vorhanden.
> DBCC-Ergebnis fr 'sysindexes'.
> Es sind 4919 Zeilen in 276 Seiten fr das sysindexes-Objekt vorhanden.
> CHECKDB hat 0 Reservierungsfehler und 3 Konsistenzfehler in der
> sysindexes-Tabelle gefunden (Objekt-ID 2).
> DBCC-Ergebnis fr 'syscolumns'.
> Es sind 8733 Zeilen in 192 Seiten fr das syscolumns-Objekt vorhanden.
> DBCC-Ergebnis fr 'systypes'.
> Es sind 26 Zeilen in 1 Seiten fr das systypes-Objekt vorhanden.
> DBCC-Ergebnis fr 'syscomments'.
> Es sind 2828 Zeilen in 63 Seiten fr das syscomments-Objekt vorhanden.
> ----and so on ...
>
> --CHECKDB repair_allow_data_loss--
> Server: Nachr.-Nr. 8929, Schweregrad 16, Status 1, Zeile 3
> Objekt-ID 2: Fehler in Text-ID 195789324288 gefunden, deren
> Besitzer Datensatz RID = (1:1317:3) id = 861506398 and indid = 1 ist.
> Server: Nachr.-Nr. 8961, Schweregrad 16, Status 1, Zeile 3
> Tabellenfehler: Objekt-ID 2. Der text-, ntext- oder image-Knoten
> auf Seite (1:5999), Slot 0, Text-ID 195789324288 stimmt nicht mit
> seinem Verweis von Seite (1:10742), Slot 10 berein.
> Server: Nachr.-Nr. 8961, Schweregrad 16, Status 1, Zeile 3
> Tabellenfehler: Objekt-ID 2. Der text-, ntext- oder image-Knoten
> auf Seite (1:10742), Slot 10, Text-ID 58350370816 stimmt nicht mit
> seinem Verweis von Seite (1:1317), Slot 3 berein.
> DBCC-Ergebnis fr 'XenoxDB'.
> DBCC-Ergebnis fr 'sysobjects'.
> Es sind 3908 Zeilen in 71 Seiten fr das sysobjects-Objekt vorhanden.
> DBCC-Ergebnis fr 'sysindexes'.
> Die REPAIR-Stufe in der DBCC-Anweisung hat bewirkt, dass
> diese Fehlerbehebung bergangen wurde.
> Die REPAIR-Stufe in der DBCC-Anweisung hat bewirkt, dass
> diese Fehlerbehebung bergangen wurde.
> Die REPAIR-Stufe in der DBCC-Anweisung hat bewirkt, dass
> diese Fehlerbehebung bergangen wurde.
> Es sind 4919 Zeilen in 276 Seiten fr das sysindexes-Objekt vorhanden.
> CHECKDB hat 0 Reservierungsfehler und 3 Konsistenzfehler in der
> sysindexes-Tabelle gefunden (Objekt-ID 2).
> DBCC-Ergebnis fr 'syscolumns'.
> Es sind 8733 Zeilen in 192 Seiten fr das syscolumns-Objekt vorhanden.
> DBCC-Ergebnis fr 'systypes'.
> --Rest is similar to above output !
>