Missing or invalid key in index

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

Missing or invalid key in index

Author

Topic

oliviermoron
Starting Member

7 Posts

Posted - 2007-03-12 : 10:58:27

Dear all,

We have such problems:
DBCC results for 'TRAMES'.
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:3893993:34) identified by (RID = (1:3893993:34) ) has index values (PO_ID = 80123).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'TRAMES' (ID 1573580644). Missing or invalid key in index 'IX_POID' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:3893993:48) identified by (RID = (1:3893993:48) ) has index values (PO_ID = 80095).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'TRAMES' (ID 1573580644). Missing or invalid key in index 'IX_POID' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:3893993:79) identified by (RID = (1:3893993:79) ) has index values (PO_ID = 80123).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'TRAMES' (ID 1573580644). Missing or invalid key in index 'IX_POID' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:3893993:92) identified by (RID = (1:3893993:92) ) has index values (PO_ID = 80095).
There are 1703901 rows in 18180 pages for object 'TRAMES'.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'TRAMES' (object ID 1573580644).

And really I don't know what can I do to prevent such problems. I know how to fix it with a dbreindex, but it blocks the production during several minutes, and we have to restart the whole plant...

we are using SQL 2000 standard edition 8.00.2039 (with SP4)

Thank you,
regards

Olivier

Kristen
Test

22859 Posts

Posted - 2007-03-12 : 11:16:43

Corruptions to the database are almost always caused by a hardware failure. Suggest you look in the SQL Logs and the Event log to check for any issues.

Sounds like this has happened before??

Kristen

oliviermoron
Starting Member

7 Posts

Posted - 2007-03-12 : 11:50:12

quote:
Originally posted by Kristen

Corruptions to the database are almost always caused by a hardware failure. Suggest you look in the SQL Logs and the Event log to check for any issues.

Sounds like this has happened before??

Kristen

Yes, could be the same problem. As a solution, we are going to change the disk array before summer...
Olivier

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources