Consistency Issues During/after Disk Rebuild
Apr 9, 2008
We had one of the disks in our array fail yesterday morning. The rebuild process using the hot spare went into effect as one would expect. My question is: during this rebuild process, could additional errors be introduced into the database? I'm asking because the current production db has more errors than the restored database from last night.
Msg 8928, Level 16, State 1, Line 3
Object ID 210099789, index ID 255: Page (1:128895) could not be processed. See other errors for details.
Msg 8939, Level 16, State 106, Line 3
Table error: Object ID 210099789, index ID 255, page (1:128895). Test (m_freeCnt == freeCnt) failed. Values are 0 and 8094.
Msg 8939, Level 16, State 108, Line 3
Table error: Object ID 210099789, index ID 255, page (1:128895). Test (emptySlotCnt == 0) failed. Values are 1 and 0.
Msg 8928, Level 16, State 1, Line 3
Object ID 210099789, index ID 255: Page (1:469839) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 3
Table error: Object ID 210099789, index ID 255, page (1:469839). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Msg 8928, Level 16, State 1, Line 3
Object ID 210099789, index ID 255: Page (1:469935) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 3
Table error: Object ID 210099789, index ID 255, page (1:469935). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Msg 8928, Level 16, State 1, Line 3
Object ID 210099789, index ID 255: Page (1:491535) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 3
Table error: Object ID 210099789, index ID 255, page (1:491535). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Msg 8928, Level 16, State 1, Line 3
Object ID 210099789, index ID 255: Page (1:680703) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 3
Table error: Object ID 210099789, index ID 255, page (1:680703). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Msg 8928, Level 16, State 1, Line 3
Object ID 210099789, index ID 255: Page (1:762783) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 3
Table error: Object ID 210099789, index ID 255, page (1:762783). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
CHECKDB found 0 allocation errors and 13 consistency errors in table 'session_state' (object ID 210099789).
Msg 8928, Level 16, State 1, Line 3
Object ID 234028165, index ID 0: Page (1:14175) could not be processed. See other errors for details.
Msg 8944, Level 16, State 17, Line 3
Table error: Object ID 234028165, index ID 0, page (1:14175), row 0. Test (columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed. Values are 326 and 300.
Msg 8928, Level 16, State 1, Line 3
Object ID 234028165, index ID 0: Page (1:155583) could not be processed. See other errors for details.
Msg 8944, Level 16, State 12, Line 3
Table error: Object ID 234028165, index ID 0, page (1:155583), row 1. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 3840 and 388.
Msg 8928, Level 16, State 1, Line 3
Object ID 234028165, index ID 0: Page (1:179199) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 3
Table error: Object ID 234028165, index ID 0, page (1:179199). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Msg 8928, Level 16, State 1, Line 3
Object ID 234028165, index ID 0: Page (1:237663) could not be processed. See other errors for details.
Msg 8944, Level 16, State 12, Line 3
Table error: Object ID 234028165, index ID 0, page (1:237663), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 91 and 26.
Msg 8928, Level 16, State 1, Line 3
Object ID 234028165, index ID 0: Page (1:1060304) could not be processed. See other errors for details.
Msg 8944, Level 16, State 12, Line 3
Table error: Object ID 234028165, index ID 0, page (1:1060304), row 1. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 61455 and 397.
Msg 8928, Level 16, State 1, Line 3
Object ID 234028165, index ID 0: Page (1:1392799) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 3
Table error: Object ID 234028165, index ID 0, page (1:1392799). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
CHECKDB found 0 allocation errors and 12 consistency errors in table 'clientCampaignActivityAll' (object ID 234028165).
View 4 Replies
ADVERTISEMENT
Jul 9, 2015
I am using SQL Server 2008 (RTM) Standard Edition.
In my environment, one of my Database size is 75 gb and I have to create a plan for index rebuild using maintenance plan.But when we rebuild indexes, it requires some space on data and log files of database.how can we calculate disk space requirement for index rebuild process ?
View 4 Replies
View Related
Sep 15, 2015
I'm trying to determine how much space I would need for my data drive and log file drive to do index rebuild. I have a database which is 100gb, it is in simple recovery mode. let me know what to have a look at to determine how much space.
View 7 Replies
View Related
Dec 28, 2006
hello,all
I am new to Sql 2000,I installed sql 2000 database in C disk,but Now I found my C disk space is smaller than before,So I want to move my databse(include data and structure) from C Disk to D Disk(its space is very large) .
is it possible to do it ?
if its can be done ,do I need to change my asp.net program source code (exp: chaneg my crystal report connectstring ) ?
thanks in advanced!
View 1 Replies
View Related
Sep 10, 2007
If I return the Average, Minimum, and Maximum values for the counter Physical Disk: Avg. Disk Queue Length, and those values are 10, 0, 87 respectively, which value do I use to compute the Avg. Disk Queue Length for a 4 disk array(RAID 10): Average, Minimum, or Maximum? The disk(lun) is on a SAN.
View 1 Replies
View Related
Nov 13, 2007
-- Initialize Control Mechanism
DECLARE@Drive TINYINT,
@SQL VARCHAR(100)
SET@Drive = 97
-- Setup Staging Area
DECLARE@Drives TABLE
(
Drive CHAR(1),
Info VARCHAR(80)
)
WHILE @Drive <= 122
BEGIN
SET@SQL = 'EXEC XP_CMDSHELL ''fsutil volume diskfree ' + CHAR(@Drive) + ':'''
INSERT@Drives
(
Info
)
EXEC(@SQL)
UPDATE@Drives
SETDrive = CHAR(@Drive)
WHEREDrive IS NULL
SET@Drive = @Drive + 1
END
-- Show the expected output
SELECTDrive,
SUM(CASE WHEN Info LIKE 'Total # of bytes : %' THEN CAST(REPLACE(SUBSTRING(Info, 32, 48), CHAR(13), '') AS BIGINT) ELSE CAST(0 AS BIGINT) END) AS TotalBytes,
SUM(CASE WHEN Info LIKE 'Total # of free bytes : %' THEN CAST(REPLACE(SUBSTRING(Info, 32, 48), CHAR(13), '') AS BIGINT) ELSE CAST(0 AS BIGINT) END) AS FreeBytes,
SUM(CASE WHEN Info LIKE 'Total # of avail free bytes : %' THEN CAST(REPLACE(SUBSTRING(Info, 32, 48), CHAR(13), '') AS BIGINT) ELSE CAST(0 AS BIGINT) END) AS AvailFreeBytes
FROM(
SELECTDrive,
Info
FROM@Drives
WHEREInfo LIKE 'Total # of %'
) AS d
GROUP BYDrive
ORDER BYDrive
E 12°55'05.25"
N 56°04'39.16"
View 16 Replies
View Related
Nov 15, 2006
Hello,
I am trying to setup a test cluster and am having an issue. When I try to create the resource of a physical disk it takes both the drive e: and drive q: and doesn't seperate them into two physical disks as resources. This means when I try to associate the quorum disk it links the to physcial disk resource of drive e and q. Then when I try to install SQL2k5 I get the warning about installing SQL on the quorum disk. Am I missing something? Is there a way to seperate e and q onto two physical disk resources so I can specifically associate the quorum to q and the sql to e or should I be setting the quorum disk to a majority node set? Thanks in advance.
John
View 4 Replies
View Related
Feb 20, 2001
Hello,
this is my configuration :
1) 3 disks in RAID5 that hold the SQL data
2) 1 disk in RAID0 that holds the only paging file.
What will happen to the SQL data (DB) when the disk that holds the paging file crashes?
Kindest regards,
Luc.
View 1 Replies
View Related
Jun 25, 2015
I have a requirement to only rebuild the Clustered Indexes in the table ignoring the non clustered indexes as those are taken care of by the Clustered indexes.
In order to do that, I have taken the records based on the fragmentation %.
But unable to come up with a logic to only consider rebuilding the clustered indexes in the table.
create table #fragmentation
(
FragIndexId BigInt Identity(1,1),
--IDENTITY(int, 1, 1) AS FragIndexId,
DBNAME nvarchar(4000),
TableName nvarchar(4000),
[Code] ....
View 5 Replies
View Related
May 7, 2004
Hi all,
Ok here goes,
I have a three tier system using SQL server 2000, we are currently experiencing IO bottle necks on our SCSI Raid 10 array, which holds the Data and the logs in separate partitions.
So my options as I understand it are:
Get Enterprise edition
or
Get another physical raid 10 array and separate the logs and data i.e. data on one array and logs on the other array.
I would like to try the latter but I am totally unsure how much difference this will make or whether it will make any difference at all.
Does anyone know how much performance increase I will get from using two arrays as opposed to one?
Any other advice on this scenario would be greatly appreciated.
Thanks
View 4 Replies
View Related
Apr 6, 2006
Asad writes "I have a report that is generated each day that tells me some what of status of DB.
For the first time in the report I see an item as follows:
DB Consistency = 2 followed by the table name.
Can someone please provide info on this.
Thanks."
View 2 Replies
View Related
Jun 1, 2001
Hi,
Over the last few weeks we've been having problems with a particular table in our live OLTP database - dbcc checkdb has been reporting consistency errors.
Initially i took the db offline and fixed the errors using checkdb and replacing the deleted records from a backup of the table. After some investigation it appeared that the errors were being caused when the unique clustered index on the table was rebuilt during weekend maintenance. After a lot of testing i was sure this was the case - so i just deleted the index (the table is small and was over-indexed anyway) and the errors stopped occurring. I didn't understand why the errors had occurred in the first place, and i wasn't convinced that the index was the real problem, but the errors had gone - so that was ok for the short term.
A few things still bugged me:
1. For audit purposes we maintain a copy of the table in question (populated via triggers on the live table) and this showed up consistency errors too. This led me to suspect the problem was with the data itself or the structure of the table - unfortunately there's nothing remarkable about this small, rarely updated table at all (apart from the fact that it's vital for our business!).
2. Any database built from backups of the live db consistently report errors now despite the fact that the backups were made after the problem was resolved and when dbcc checkdb reported NO errors (I maintain a number of test and olap databases in this way). What's happening here? (My guess is that the backup and restore process involves rebuilding indexes, rearranging data, etc. and this is resurrecting the problem) I couldn't help feeling that despite having apparently fixed the errors they were still lurking out there somewhere....
3. At no point did the data in the table appear to be corrupt in any way from the user perspective. This provokes two questions - is dbcc checkdb reliable at both reporting and fixing errors, and how serious are consistency errors?
After removing the suspect index everything was fine for a few weeks until this morning - when errors were again reported on the same table. After hours spent testing and playing around with this (dropping indexes, dropping or truncating the table and re-populating from ascii files, etc.) i've now hit a brick wall. I still suspect the problem is related to the data itself or the structure of the table but can't get any further.....so..
Has anyone come up against a similar problem?
Any suggestions for the next course of action?
Can anyone point me to documentation on checkdb or consistency errors (other than what's in BOL or the MS knowledge base)?
thanks,
d.
View 5 Replies
View Related
Apr 15, 2008
I ran DBCC CHECKDB ('DBNAME', repair_rebuild)and I got a whole bunch of errors and would like to know how to fix.
Any help would be appreciated.
here is part of the error message
Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1
Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1
View 6 Replies
View Related
Aug 1, 2005
Sorry as the last Topic thread was closed...
I just had the same problem. I put the DB in single_user mode then ran a DBCC CheckTable with Repair and then had 80 consis errors. A DBCC CheckTable with Repiar_Rebuild didn't fix it either. A DBCC Reindex of the Table cleared all errors without data loss and another CHeckTable was clean as well. Any ideas?
Below are the results of a DBCC CHeckTable.
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:2) identified by (RID = (4:8:2) WorkOrder = 5339343 and Instruction = '0053100230106 ' and order_seq = 3 and Node = 1) has index values (WorkOrder = 5339343 and Instruction = '0053100230106 ' and order_seq = 3 and ImageID = '0053100230106' and WorkOrder = 5339343 and Instruction = '0053100230106 ' and order_seq = 3 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:3) identified by (RID = (4:8:3) WorkOrder = 5339863 and Instruction = '0053010240041 ' and order_seq = 1 and Node = 1) has index values (WorkOrder = 5339863 and Instruction = '0053010240041 ' and order_seq = 1 and ImageID = '0053010240041' and WorkOrder = 5339863 and Instruction = '0053010240041 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:4) identified by (RID = (4:8:4) WorkOrder = 5339992 and Instruction = '0053021340004 ' and order_seq = 1 and Node = 1) has index values (WorkOrder = 5339992 and Instruction = '0053021340004 ' and order_seq = 1 and ImageID = '0053021340004' and WorkOrder = 5339992 and Instruction = '0053021340004 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:5) identified by (RID = (4:8:5) WorkOrder = 5339992 and Instruction = '0053021340005 ' and order_seq = 2 and Node = 1) has index values (WorkOrder = 5339992 and Instruction = '0053021340005 ' and order_seq = 2 and ImageID = '0053021340005' and WorkOrder = 5339992 and Instruction = '0053021340005 ' and order_seq = 2 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:6) identified by (RID = (4:8:6) WorkOrder = 5339993 and Instruction = '0053021340011 ' and order_seq = 1 and Node = 1) has index values (WorkOrder = 5339993 and Instruction = '0053021340011 ' and order_seq = 1 and ImageID = '0053021340011' and WorkOrder = 5339993 and Instruction = '0053021340011 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:7) identified by (RID = (4:8:7) WorkOrder = 5339994 and Instruction = '0053022740041 ' and order_seq = 1 and Node = 1) has index values (WorkOrder = 5339994 and Instruction = '0053022740041 ' and order_seq = 1 and ImageID = '0053022740041' and WorkOrder = 5339994 and Instruction = '0053022740041 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:8) identified by (RID = (4:8:8) WorkOrder = 5339994 and Instruction = '0053022740052 ' and order_seq = 2 and Node = 1) has index values (WorkOrder = 5339994 and Instruction = '0053022740052 ' and order_seq = 2 and ImageID = '0053022740052' and WorkOrder = 5339994 and Instruction = '0053022740052 ' and order_seq = 2 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:9) identified by (RID = (4:8:9) WorkOrder = 5339996 and Instruction = '0053021340034 ' and order_seq = 1 and Node = 1) has index values (WorkOrder = 5339996 and Instruction = '0053021340034 ' and order_seq = 1 and ImageID = '0053021340034' and WorkOrder = 5339996 and Instruction = '0053021340034 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:10) identified by (RID = (4:8:10) WorkOrder = 5339996 and Instruction = '0053021340034 ' and order_seq = 101 and Node = 1) has index values (WorkOrder = 5339996 and Instruction = '0053021340034 ' and order_seq = 101 and ImageID = '0053021340034' and WorkOrder = 5339996 and Instruction = '0053021340034 ' and order_seq = 101 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:11) identified by (RID = (4:8:11) WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 2 and Node = 1) has index values (WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 2 and ImageID = '0053021340044' and WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 2 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:12) identified by (RID = (4:8:12) WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 3 and Node = 1) has index values (WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 3 and ImageID = '0053021340044' and WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 3 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:13) identified by (RID = (4:8:13) WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 102 and Node = 1) has index values (WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 102 and ImageID = '0053021340044' and WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 102 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:14) identified by (RID = (4:8:14) WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 103 and Node = 1) has index values (WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 103 and ImageID = '0053021340044' and WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 103 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:0) identified by (RID = (4:8:0) WorkOrder = 5339343 and Instruction = '0053100230106 ' and order_seq = 1 and Node = 1) has index values (ImageID = '0053100230106' and WorkOrder = 5339343 and Instruction = '0053100230106 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:1) identified by (RID = (4:8:1) WorkOrder = 5339343 and Instruction = '0053100230106 ' and order_seq = 2 and Node = 1) has index values (ImageID = '0053100230106' and WorkOrder = 5339343 and Instruction = '0053100230106 ' and order_seq = 2 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:2) identified by (RID = (4:8:2) WorkOrder = 5339343 and Instruction = '0053100230106 ' and order_seq = 3 and Node = 1) has index values (ImageID = '0053100230106' and WorkOrder = 5339343 and Instruction = '0053100230106 ' and order_seq = 3 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:3) identified by (RID = (4:8:3) WorkOrder = 5339863 and Instruction = '0053010240041 ' and order_seq = 1 and Node = 1) has index values (ImageID = '0053010240041' and WorkOrder = 5339863 and Instruction = '0053010240041 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:4) identified by (RID = (4:8:4) WorkOrder = 5339992 and Instruction = '0053021340004 ' and order_seq = 1 and Node = 1) has index values (ImageID = '0053021340004' and WorkOrder = 5339992 and Instruction = '0053021340004 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:5) identified by (RID = (4:8:5) WorkOrder = 5339992 and Instruction = '0053021340005 ' and order_seq = 2 and Node = 1) has index values (ImageID = '0053021340005' and WorkOrder = 5339992 and Instruction = '0053021340005 ' and order_seq = 2 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:6) identified by (RID = (4:8:6) WorkOrder = 5339993 and Instruction = '0053021340011 ' and order_seq = 1 and Node = 1) has index values (ImageID = '0053021340011' and WorkOrder = 5339993 and Instruction = '0053021340011 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:7) identified by (RID = (4:8:7) WorkOrder = 5339994 and Instruction = '0053022740041 ' and order_seq = 1 and Node = 1) has index values (ImageID = '0053022740041' and WorkOrder = 5339994 and Instruction = '0053022740041 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:8) identified by (RID = (4:8:8) WorkOrder = 5339994 and Instruction = '0053022740052 ' and order_seq = 2 and Node = 1) has index values (ImageID = '0053022740052' and WorkOrder = 5339994 and Instruction = '0053022740052 ' and order_seq = 2 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:9) identified by (RID = (4:8:9) WorkOrder = 5339996 and Instruction = '0053021340034 ' and order_seq = 1 and Node = 1) has index values (ImageID = '0053021340034' and WorkOrder = 5339996 and Instruction = '0053021340034 ' and order_seq = 1 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:10) identified by (RID = (4:8:10) WorkOrder = 5339996 and Instruction = '0053021340034 ' and order_seq = 101 and Node = 1) has index values (ImageID = '0053021340034' and WorkOrder = 5339996 and Instruction = '0053021340034 ' and order_seq = 101 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:11) identified by (RID = (4:8:11) WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 2 and Node = 1) has index values (ImageID = '0053021340044' and WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 2 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:12) identified by (RID = (4:8:12) WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 3 and Node = 1) has index values (ImageID = '0053021340044' and WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 3 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:13) identified by (RID = (4:8:13) WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 102 and Node = 1) has index values (ImageID = '0053021340044' and WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 102 and Node = 1).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Order_Item_Images' (ID 829962033). Missing or invalid key in index 'IX_Order_Item_Images_1' (ID 3) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (4:8:14) identified by (RID = (4:8:14) WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 103 and Node = 1) has index values (ImageID = '0053021340044' and WorkOrder = 5339996 and Instruction = '0053021340044 ' and order_seq = 103 and Node = 1).
DBCC results for 'Order_Item_Images'.
There are 9816281 rows in 221056 pages for object 'Order_Item_Images'.
CHECKTABLE found 0 allocation errors and 28 consistency errors in table 'Order_Item_Images' (object ID 829962033).
repair_fast is the minimum repair level for the errors found by DBCC CHECKTABLE (PIP.dbo.Order_Item_Images ).
Thanks DeWayne McCallie DBA
Olan Mills, Inc.
Chattanooga TN...
View 8 Replies
View Related
Aug 22, 2005
Hi
I have execute a script on my SQL Db (script to create indexes and views) and got the following error
Server: Msg 823, Level 24, State 2, Line 1
I/O error (bad page ID) detected during read at offset 0x000000232fe000 in file 'D:...filename.mdf'
ODBC: Msg 0, Level 16, STate 1
Communication link failure
DBCC CHECKDB returned
Database '' consistency errors in sysobjects, syscolumns, or systtypes prevent further CHECKDB processing..........
dbcc checktable ('syscolumns') returned
Server: Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID 0, page ID (1:86382). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID 0, page ID (1:86383). The PageId in the page header = (0:0).
Server: Msg 8928, Level 16, State 1, Line 2
Object ID 3, index ID 0: Page (1:86382) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 2
Object ID 3, index ID 0: Page (1:86383) could not be processed. See other errors for details.
CHECKTABLE found 0 allocation errors and 2 consistency errors not associated with any single object.
DBCC results for 'syscolumns'.
There are 2059 rows in 133 pages for object 'syscolumns'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'syscolumns' (object ID 3).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (databasename.dbo.syscolumns ).
Please help to solve this issue
Thanks & regards,
Eldho
View 9 Replies
View Related
Oct 10, 2005
Hiya,
Our weekly DBCC picked up a consistency error on a table (see end of post). After the dbcc's, all the indexes were rebuilt and this seems to of cured the problem. I`m however concerned that its occured and want to understand the problem better and am looking for any general advice.
The last time i had this type of error it use to occur every few weeks and turned out to related to KB834628.
I`m running SQL 2000 SP3, build 911 on Windows 2003 RTM active active cluster. 7gb ram dual proc with PAE in boot.ini and AWE enabled for SQL.
ALso i've now set dbcc's to run daily. All help appreciated! Ta
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 322360463, index ID 0: Page (1:544817) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 322360463, index ID 0, page (1:544817), row 17. Test (columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed. Values are 30821 and 324.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in table 'S_WFR_STP_ARG' (object ID 3
View 4 Replies
View Related
Nov 22, 2005
Hi all, long time reader, first time poster, budding dba passionate about SQL Server.
I received the following Consistency errors:
4] Database IMM481_Nidderdale_Visitor: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8970: [Microsoft][ODBC SQL Server Driver][SQL Server]Row error: Object ID 573245097, index ID 0, page ID (1:170), row ID 0. Column 'p_created_date' was created NOT NULL, but is NULL in the row.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 573245097. The text, ntext, or image node at page (1:102), slot 1, text ID 1122172928 is not referenced.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 573245097. The text, ntext, or image node at page (1:102), slot 2, text ID 1122238464 is not referenced.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 3 consistency errors in table 'page_data' (object ID 573245097).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 3 consistency errors in database 'IMM481_Nidderdale_Visitor'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (IMM481_Nidderdale_Visitor ).
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Row error: Object ID 573245097, index ID 0, page ID (1:170), row ID 0. Column 'p_created_date' was created NOT NULL, but is NULL in the row.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 573245097. The text, ntext, or image node at page (1:102), slot 1, text ID 1122172928 is not referenced.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 573245097. The text, ntext, or image node at page (1:102), slot 2, text ID 1122238464 is not referenced.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 3 consistency errors in table 'page_data' (object ID 573245097).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 3 consistency errors in database 'IMM481_Nidderdale_Visitor'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (IMM481_Nidderdale_Visitor ).
** Execution Time: 0 hrs, 0 mins, 1 secs **
I'm trying to see the extent of the problem by running:
Begin Tran TranStart
DBCC CheckDB ('IMM481_Nidderdale_Visitor', Repair_Allow_Data_Loss)
However, SQL Server is bitching about the db not being in Single User Mode. I've refreshed the process info to only find the sa using the db.
What have I missed?
Many thanks,
Drew
(You will get sick of this name)
View 11 Replies
View Related
Jan 12, 2006
I need some help with some consistency errors.
Today I recieved this alert from the SQL Server:
Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x00002245b90000 in file 'D:MSSQLDataPortal.mdf'.
Running dbcc checkdb with ALL_ERRORMSGS, NO_INFOMSGS yield the following:
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 35900555264 owned by data record identified by RID = (1:10804409:35) add_user = 'AMiller' and correspond_id = 53750.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 343740186624 owned by data record identified by RID = (1:10804652:14) add_user = 'AShallah' and correspond_id = 1457578.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 293307285504 owned by data record identified by RID = (1:10806770:23) add_user = 'CCruzon' and correspond_id = 1341479.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 335802204160 owned by data record identified by RID = (1:10807332:20) add_user = 'CLopez' and correspond_id = 1439003.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 335808167936 owned by data record identified by RID = (1:10807332:21) add_user = 'CLopez' and correspond_id = 1439019.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 249395871744 owned by data record identified by RID = (1:10807530:25) add_user = 'CrJohnson' and correspond_id = 1210177.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 335808233472 owned by data record identified by RID = (1:10808745:16) add_user = 'DKlett' and correspond_id = 1439020.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 335810330624 owned by data record identified by RID = (1:10808745:17) add_user = 'DKlett' and correspond_id = 1439026.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 335810658304 owned by data record identified by RID = (1:10808745:18) add_user = 'DKlett' and correspond_id = 1439028.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 335812231168 owned by data record identified by RID = (1:10809251:13) add_user = 'DNealy' and correspond_id = 1439030.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 335816359936 owned by data record identified by RID = (1:10809251:14) add_user = 'DNealy' and correspond_id = 1439041.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 342354165760 owned by data record identified by RID = (1:10816733:32) add_user = 'Jhawkins' and correspond_id = 1452702.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 342359015424 owned by data record identified by RID = (1:10818038:3) add_user = 'JTheis' and correspond_id = 1452722.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 333403914240 owned by data record identified by RID = (1:10818166:12) add_user = 'JThongdy' and correspond_id = 1431000.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 301036273664 owned by data record identified by RID = (1:10819716:19) add_user = 'KHaines' and correspond_id = 1359551.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 218653261824 owned by data record identified by RID = (1:10822560:19) add_user = 'MPena' and correspond_id = 1163647.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 342353838080 owned by data record identified by RID = (1:10822879:0) add_user = 'MWiley' and correspond_id = 1452698.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 342353969152 owned by data record identified by RID = (1:10822879:1) add_user = 'MWiley' and correspond_id = 1452699.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 542624976: Errors found in text ID 333405749248 owned by data record identified by RID = (1:10832505:23) add_user = 'PGutierrez' and correspond_id = 1431011.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 542624976, index ID 255: Page (1:885006) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 542624976, index ID 255, page (1:885006). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 0, text ID 35900555264 is referenced by page (1:885004), slot 0, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 1, text ID 333403914240 is referenced by page (1:10818166), slot 12, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 2, text ID 333405749248 is referenced by page (1:10832505), slot 23, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 3, text ID 335802204160 is referenced by page (1:10807332), slot 20, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 4, text ID 335808167936 is referenced by page (1:10807332), slot 21, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 5, text ID 335808233472 is referenced by page (1:10808745), slot 16, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 6, text ID 335810330624 is referenced by page (1:10808745), slot 17, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 7, text ID 335810658304 is referenced by page (1:10808745), slot 18, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 8, text ID 335812231168 is referenced by page (1:10809251), slot 13, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 9, text ID 335816359936 is referenced by page (1:10809251), slot 14, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 10, text ID 342353838080 is referenced by page (1:17300344), slot 0, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 11, text ID 342353838080 is referenced by page (1:10822879), slot 0, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 12, text ID 342353969152 is referenced by page (1:10822879), slot 1, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 13, text ID 342354165760 is referenced by page (1:10816733), slot 32, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 14, text ID 342359015424 is referenced by page (1:10818038), slot 3, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 15, text ID 343740186624 is referenced by page (1:19351761), slot 0, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:885006), slot 16, text ID 343740186624 is referenced by page (1:10804652), slot 14, but was not seen in the scan.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 542624976, index ID 255: Page (1:8398158) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 542624976, index ID 255, page (1:8398158), row 0. Test (offsetNull >= BASEOFFSET) failed. Values are 0 and 4.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:8398158), slot 0, text ID 301036273664 is referenced by page (1:8398150), slot 0, but was not seen in the scan.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 542624976, index ID 255: Page (1:9154510) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 542624976, index ID 255, page (1:9154510), row 0. Test (!(hdr->r_tagA & (VERSION_MASK | RECTAG_RESV_A | RECTAG_RESV_B))) failed. Values are 255 and 193.
Server: Msg 8944, Level 16, State 4, Line 1
Table error: Object ID 542624976, index ID 255, page (1:9154510), row 0. Test (GetRecType (pRec) >= 0 && GetRecType (pRec) <= LAST_REC_TYPE) failed. Values are 14 and 12.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 542624976, index ID 255, page (1:9154510), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 65535 and 7838.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:9154510), slot 0, text ID 218653261824 is referenced by page (1:9154493), slot 0, but was not seen in the scan.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 542624976, index ID 255: Page (1:10444815) could not be processed. See other errors for details.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:10444815), slot 0, text ID 249395871744 is referenced by page (1:10444775), slot 0, but was not seen in the scan.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 542624976, index ID 255, page ID (1:15257220). The PageId in the page header = (1:15257228).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 542624976, index ID 255: Page (1:15257220) could not be processed. See other errors for details.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:15257220), slot 0, text ID 293307285504 is referenced by page (1:15089406), slot 0, but was not seen in the scan.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 542624976, index ID 255, page ID (1:15257221). The PageId in the page header = (1:15257229).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 542624976, index ID 255: Page (1:15257221) could not be processed. See other errors for details.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:15257221), slot 0, text ID 293307285504 is referenced by page (1:15089406), slot 0, but was not seen in the scan.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 542624976, index ID 255, page ID (1:15257222). The PageId in the page header = (1:15257230).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 542624976, index ID 255: Page (1:15257222) could not be processed. See other errors for details.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:15257222), slot 0, text ID 293307285504 is referenced by page (1:15089406), slot 0, but was not seen in the scan.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 542624976, index ID 255, page ID (1:15257223). The PageId in the page header = (1:15257231).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 542624976, index ID 255: Page (1:15257223) could not be processed. See other errors for details.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:15257223), slot 0, text ID 293307285504 is referenced by page (1:15089406), slot 0, but was not seen in the scan.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17030749), slot 0, text ID 335802204160 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17030760), slot 0, text ID 335808167936 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17053063), slot 0, text ID 335808233472 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17053071), slot 0, text ID 335810330624 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17053079), slot 0, text ID 335810658304 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17064698), slot 0, text ID 335812231168 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17064707), slot 0, text ID 335816359936 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17294071), slot 0, text ID 342359015424 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17295780), slot 0, text ID 342354165760 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17300344), slot 0, text ID 342353838080 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:17300352), slot 0, text ID 342353969152 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:19351761), slot 0, text ID 343740186624 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:19675671), slot 0, text ID 333403914240 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 542624976. The text, ntext, or image node at page (1:19676212), slot 0, text ID 333405749248 is not referenced.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 552493147: Errors found in text ID 263269974016 owned by data record identified by RID = (1:9422783:33).
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 552493147: Errors found in text ID 263272202240 owned by data record identified by RID = (1:9422783:34).
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 552493147: Errors found in text ID 263278231552 owned by data record identified by RID = (1:9422783:35).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 552493147, index ID 255: Page (1:11912175) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 552493147, index ID 255, page (1:11912175). Test (sorted [i].offset <= m_freeData) failed. Slot 1, offset 0xff00 is invalid.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 552493147. The text, ntext, or image node at page (1:11912175), slot 0, text ID 263269974016 is referenced by page (1:11912174), slot 5, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 552493147. The text, ntext, or image node at page (1:11912175), slot 1, text ID 263272202240 is referenced by page (1:11912174), slot 6, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 552493147. The text, ntext, or image node at page (1:11912175), slot 2, text ID 263278231552 is referenced by page (1:11912174), slot 7, but was not seen in the scan.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 942626401, index ID 10: Page (1:21868423) could not be processed. See other errors for details.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 942626401, index ID 10. Page (1:21868423) was not seen in the scan although its parent (1:21864202) and previous (1:21868422) refer to it. Check any previous errors.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 942626401, index ID 10, page (1:21868423), row 368. Test (((UNALIGNED DataRecHdr*) m_pRec)->r_tagB == 0) failed. Values are 21 and 0.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 942626401, index ID 10. Page (1:21870760) is missing a reference from previous page (1:21868423). Possible chain linkage problem.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1310679767, index ID 0, page ID (1:17968584). The PageId in the page header = (1:17968528).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1310679767, index ID 0: Page (1:17968584) could not be processed. See other errors for details.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1310679767, index ID 0, page ID (1:17968585). The PageId in the page header = (1:17968529).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1310679767, index ID 0: Page (1:17968585) could not be processed. See other errors for details.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1310679767, index ID 0, page ID (1:17968586). The PageId in the page header = (1:17968530).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1310679767, index ID 0: Page (1:17968586) could not be processed. See other errors for details.
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1310679767, index ID 0, page ID (1:17968587). The PageId in the page header = (1:17968531).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1310679767, index ID 0: Page (1:17968587) could not be processed. See other errors for details.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1310679767, index ID 1. Page (1:17968584) was not seen in the scan although its parent (1:17955256) and previous (1:17967263) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1310679767, index ID 1. Index node page (1:17955256), slot 225 refers to child page (1:17968585) and previous child (1:17968584), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1310679767, index ID 1. Index node page (1:17955256), slot 226 refers to child page (1:17968586) and previous child (1:17968585), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1310679767, index ID 1. Index node page (1:17955256), slot 227 refers to child page (1:17968587) and previous child (1:17968586), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1310679767, index ID 1. Page (1:17968588) is missing a reference from previous page (1:17968587). Possible chain linkage problem.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1546018973, index ID 255, page (1:10444815), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 7709 and 2220.
CHECKDB found 0 allocation errors and 74 consistency errors in table 'correspond' (object ID 542624976).
CHECKDB found 0 allocation errors and 8 consistency errors in table 'raaaeport_run' (object ID 552493147).
CHECKDB found 0 allocation errors and 4 consistency errors in table 'coverage' (object ID 942626401).
CHECKDB found 0 allocation errors and 13 consistency errors in table 'payment_detail' (object ID 1310679767).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 1546018973)' (object ID 1546018973).
CHECKDB found 0 allocation errors and 100 consistency errors in database 'Portal'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Portal ).
This Portal database is 180GB with 75% of that being blob data.
The only new software change to the SQL server is the addition of Redgate SQL Backup 2 weeks ago. No hardware has been added or modified. However, the server was bounced this past Sunday when it became unresponsive.
When I ran DBCC checkdb a few hours ago, there were only 44 consistency errors. Now that there are 100 is troubling.
Any ideas on how to resolve these consistency errors?
Thanks,
Ray
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
View 3 Replies
View Related
Jul 18, 2006
OS & SQL Version:
SELECT @@VERSION
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
It's a working database. It's set up to make a backup every night at 4:15 AM when the load is minimal. When making a backup it should run DBCC CHECKDB without any repair option on. One day i got a notification that backup didn't completed. I checked the errorlogs for the day between last successful backup and the next one failed. Logs are clean.
Here is the result of "DBCC CHECKDB WITH NO_INFOMSGS, ALL_ERRORMSGS":
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'Sessions' (ID 398624463). Missing or invalid key in index 'PK_Sessions' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:7420:37) identified by (RID = (1:7420:37) ) has index values (SessionId = 3539435).
CHECKDB found 0 allocation errors and 1 consistency errors in table 'Sessions' (object ID 398624463).
CHECKDB found 0 allocation errors and 1 consistency errors in database 'Accounting'.
repair_fast is the minimum repair level for the errors found by DBCC CHECKDB (Accounting ).
Not sure if sp_helpindex results are necessary, but may be it will help:
IX_Sessions_LoginTimenonclustered located on PRIMARYLoginTime
IX_Sessions_NasIpnonclustered located on PRIMARYNasIp
IX_Sessions_NasSessionIdnonclustered located on PRIMARYNasSessionId
IX_Sessions_Usernonclustered located on PRIMARYUserId
PK_Sessionsnonclustered, unique, primary key located on PRIMARYSessionId
Sessions0nonclustered located on PRIMARYLoginTime, BytesIn
REPAIR_FAST does not help. The error isn't cleared.
I have two questions about that issue.
1) How i can dig into that problem? For example i would like to simply look at the row causing problems, but i just don't know how to select rows referencing them by RID. Is it piossible? Actually i don't quite understand what DBCC output means. :(
2) Second question is of course how to correct that problem. :)
Of course i can restore from backup, but i'd like to know if there are other ways? Maybe without loosing all the information which was entered during the day? I can afford loosing several rows from that table, but loosing all info entered is not very good solution. No, i don't need backup strategy involving several DB backup during the day. :) Just don't want to reenter all the info, but it can be done if there are no other ways. :)
View 12 Replies
View Related
Dec 18, 2006
we were doing migration from sql 2K to sql 2005. we used the backup/restore method. after i restored the sql sk db to 2005, i ran checkdb and there were consistency errors. The error was as follows:
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=1241979701,referenced_minor_id=4) of row (class=0,object_id=467024945,column_id=0,referenced_major_id=1241979701,referenced_minor_id=4) in sys.sql_dependencies does not have a matching row (object_id=1241979701,column_id=4) in sys.columns.
Please help. Not sure what the fix is. If i run checkdb on sql 2k, there are no consistency errors. could this be due to hardware issue or is there something that needs to be done before migration?
View 1 Replies
View Related
Nov 13, 2007
over the weekend SQL returned errors on all 3 integrity checks which run each night at 8 pm through the normal maintenance plan. Pretty much the same each night. 2 consistency errors on a particular table. Today I ran a manual DBCC Checkdb on the database and it returned 0 consistency errors.
What should I believe. SQL said 0 were repaired during the maintenance plans, which is normal because it is not set to auto repair.
Thanks for any help,
Jeff
View 3 Replies
View Related
Mar 5, 2007
What is the mechanism used by select statements to return point in time data?
I have a test setup - table t1 has 1000000 rows. A query (call q1) that selects all the rows (in NOLOCK mode and process them) takes 10 minutes. At the same time another process inserts another 1000000 rows into the same table t1. As expected, client that issued query q1 sees just 1000000 rows.
My understanding is that NOLOCK does not hold any locks. So, how did SQL Server know that it should not return the rows that are inserted after I issued the query q1? Some explanation or link to some whitepapers would be helpful.
Thanks
View 7 Replies
View Related
Jan 2, 2002
Hi,
I found the databases are performance is very poor and I was told to repair the database after running consistency checker.
I presume to repair the database, it needs to be started in single user mode.
We got many databases in the dataserver being used on 24/7 basis. Could any please suggest any efficient method/way of repairing database objects(table) minimising the downtime.
Also please tell me how to start individual database in singe used mode.
Thanks in advance
John Jayaseelan
View 1 Replies
View Related
Feb 16, 1999
When my Backup Exec runs a Consistency check on tempdb I keep getting this error:
Allocation Discrepancy: Page is allocated but not linked; check the following pages and ids: a `location pg#=512 extent id=560 logical pg#=560 object id on extent=-1168007832 (ob `ect name = -1168007832) indid on extent=1.
What does this mean exactly, and what do I need to do?
Thanks if you can help.
Andrew
View 3 Replies
View Related
Apr 5, 2008
sql server 2000 .. harddrive problems resolved but now several of my datatbases have consistency errors.. lots of them.
best way to repair????????? need to get this resolved asap
View 3 Replies
View Related
Jul 6, 2005
Vimal Kanth writes "I am using SQL Server 2000 and one of my databases has loads of consistency errors. When i try to query a particular record from a table it displays an error message similar to this
Could not find the index entry for RID '168927001232500300' in index page (1:95510), index ID 0, database 'Tristar'.
Then, i executed the DBCC CHECKDB command after going through some documentation. The results of which were something like this
Table error: Database 'Tristar', index 'DMS_VOUCHER.index_1739153241' (ID 1739153241) (index ID 2). Extra or invalid key for the keys:
Index row (1:11229:144) with values (ROWGUID = 22814645-5B2B-4B4E-A1D8-9B49DF7C8CEF`¢0; and DEALER_ID = 10121 and BRANCH_ID = 1.242260474E-307 and VOUCHER_ID = 9507) points to the data row identified by ().
Then, i executed the DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS command. I lost around 3000 records when i excuted this
I dont want any data loss as this is very critical.Can you please help me overcome this problem? Thanks in advance.
Regards
Vimal Kanth"
View 20 Replies
View Related
Sep 9, 2005
Hello Everyone, have somo consistency errors. Database hosted on a cluster with disk raid 5. SQL Server 2000 SP4.
I run:
dbcc checkdb (laf, NOINDEX) WITH NO_INFOMSGS, ALL_ERRORMSGS
and get this result:
Object ID 2: Errors found in text ID 5748948992 owned by data record identified by RID = (1:66410:1) id = 945438442 and indid = 2.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:7658), slot 6, text ID 5748949504 does not match its reference from page (1:66410), slot 1.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:21382), slot 0, text ID 5748948992 does not match its reference from page (1:7658), slot 6.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sysindexes' (object ID 2).
CHECKDB found 0 allocation errors and 3 consistency errors in database 'LAF'.
Then I run:
select object_name('945438442') and get: 'laf_ca_proceso_tm33'
Then I run:
dbcc dbreindex ('laf_ca_proceso_tm33')
and get:
Server: Msg 7105, Level 22, State 6, Line 1
Page (1:7658), slot 6 for text, ntext, or image node does not exist.
Connection Broken
How should I solve the problem?
Thanks a lot.
View 6 Replies
View Related
Nov 21, 2005
I have a database that has a consistency error. When I run a DBCC CHECKDB WITH NO_INFOMSGS, ALL_ERRORMSGS I get the following.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 72205074432 owned by data record identified by RID = (1:1944:23) id = 1216723387 and indid = 6.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:62963), slot 49, text ID 72188297216 does not match its reference from page (1:1944), slot 23.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'sysindexes' (object ID 2).
CHECKDB found 0 allocation errors and 2 consistency errors in database 'JDE_PDBANDIT_TEST'.
If I run a DBCC CHECKDB ('JDE_PDBANDIT_TEST', REPAIR_ALLOW_DATA_LOSS)I get the following
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 72205074432 owned by data record identified by RID = (1:1944:23) id = 1216723387 and indid = 6.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:62963), slot 49, text ID 72188297216 does not match its reference from page (1:1944), slot 23.
DBCC results for 'JDE_PDBANDIT_TEST'.
DBCC results for 'sysobjects'.
There are 4707 rows in 64 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
There are 6811 rows in 477 pages for object 'sysindexes'.
Can anyone provide any other avenues to try and resolve this issue.
View 2 Replies
View Related
Dec 12, 2005
I would need help to debug the following allocation errors on DBCC:
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:958608) object ID 16 index ID 0 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:985853) object ID 16 index ID 2 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:958600) object ID 16 index ID 255 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1067763) object ID 17 index ID 0 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1120026) object ID 17 index ID 2 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1154482) object ID 17 index ID 3 but was not detected in the scan. [SQLSTATE 42000]
Msg 2536, Sev 16: DBCC results for 'SalesHistoryDB'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysobjects'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 289 rows in 7 pages for object 'sysobjects'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysindexes'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 277 rows in 19 pages for object 'sysindexes'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'syscolumns'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1809 rows in 43 pages for object 'syscolumns'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'systypes'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 28 rows in 1 pages for object 'systypes'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'syscomments'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 301 rows in 101 pages for object 'syscomments'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysfiles1'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'syspermissions'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 311 rows in 3 pages for object 'syspermissions'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysusers'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 28 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysproperties'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 199 rows in 6 pages for object 'sysproperties'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysdepends'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1768 rows in 11 pages for object 'sysdepends'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysreferences'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE 01000]
Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 16)' (object ID 16). [SQLSTATE 01000]
Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 17)' (object ID 17). [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 0 rows in 1 pages for object 'sysfulltextcatalogs'. [SQLSTATE 01000]
DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE 01000]
DBCC results for 'sysfilegroups'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE 01000]
DBCC results for 'IgnoreSalesRep'. [SQLSTATE 01000]
There are 406 rows in 2 pages for object 'IgnoreSalesRep'. [SQLSTATE 01000]
DBCC results for 'invnsrc'. [SQLSTATE 01000]
There are 6101966 rows in 15067 pages for object 'invnsrc'. [SQLSTATE 01000]
DBCC results for 'INVO_ERRS'. [SQLSTATE 01000]
There are 333 rows in 12 pages for object 'INVO_ERRS'. [SQLSTATE 01000]
DBCC results for 'INVO_ERRS_old'. [SQLSTATE 01000]
There are 152 rows in 3 pages for object 'INVO_ERRS_old'. [SQLSTATE 01000]
DBCC results for 'INVO_HIST'. [SQLSTATE 01000]
There are 55159551 rows in 937501 pages for object 'INVO_HIST'. [SQLSTATE 01000]
DBCC results for 'INVO_HIST_SMALL'. [SQLSTATE 01000]
There are 1124659 rows in 21220 pages for object 'INVO_HIST_SMALL'. [SQLSTATE 01000]
DBCC results for 'InvoiceHistory'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'InvoiceHistory'. [SQLSTATE 01000]
DBCC results for 'QUAR_INVO_HIST'. [SQLSTATE 01000]
There are 1430739 rows in 5379 pages for object 'QUAR_INVO_HIST'. [SQLSTATE 01000]
DBCC results for 'MARKETING_REPORTS'. [SQLSTATE 01000]
There are 36371 rows in 151 pages for object 'MARKETING_REPORTS'. [SQLSTATE 01000]
DBCC results for 'MKP90'. [SQLSTATE 01000]
There are 36030746 rows in 205890 pages for object 'MKP90'. [SQLSTATE 01000]
DBCC results for 'MR_CLASS_MANU'. [SQLSTATE 01000]
There are 12159 rows in 46 pages for object 'MR_CLASS_MANU'. [SQLSTATE 01000]
DBCC results for 'MR_GROUP_MANU'. [SQLSTATE 01000]
There are 16889 rows in 66 pages for object 'MR_GROUP_MANU'. [SQLSTATE 01000]
DBCC results for 'MR_MANU_CLASS'. [SQLSTATE 01000]
There are 4876 rows in 19 pages for object 'MR_MANU_CLASS'. [SQLSTATE 01000]
DBCC results for 'MR_MANU_GROUP'. [SQLSTATE 01000]
There are 15565 rows in 61 pages for object 'MR_MANU_GROUP'. [SQLSTATE 01000]
DBCC results for 'PseudoLeaders'. [SQLSTATE 01000]
There are 79 rows in 2 pages for object 'PseudoLeaders'. [SQLSTATE 01000]
DBCC results for 'InvoiceHeader'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'InvoiceHeader'. [SQLSTATE 01000]
DBCC results for 'FedTeamGoals'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'FedTeamGoals'. [SQLSTATE 01000]
DBCC results for 'SALES_MODIFIER'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'SALES_MODIFIER'. [SQLSTATE 01000]
DBCC results for 'FedTeamPlayers'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'FedTeamPlayers'. [SQLSTATE 01000]
DBCC results for 'CGTempWMS'. [SQLSTATE 01000]
There are 25 rows in 1 pages for object 'CGTempWMS'. [SQLSTATE 01000]
DBCC results for 'srcinvn'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'srcinvn'. [SQLSTATE 01000]
DBCC results for 'TEMP_ExtranetData'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'TEMP_ExtranetData'. [SQLSTATE 01000]
DBCC results for 'EMP10'. [SQLSTATE 01000]
There are 113373 rows in 1471 pages for object 'EMP10'. [SQLSTATE 01000]
DBCC results for 'EMP10_UNIQUE'. [SQLSTATE 01000]
There are 18947 rows in 245 pages for object 'EMP10_UNIQUE'. [SQLSTATE 01000]
DBCC results for 'ITEM_SALES_306090'. [SQLSTATE 01000]
There are 310629 rows in 929 pages for object 'ITEM_SALES_306090'. [SQLSTATE 01000]
DBCC results for 'temp_SalesSummaryData'. [SQLSTATE 01000]
There are 45781 rows in 751 pages for object 'temp_SalesSummaryData'. [SQLSTATE 01000]
DBCC results for 'Rob_DeletedFromCustomerPricingMatrix20031107'. [SQLSTATE 01000]
There are 1469 rows in 6 pages for object 'Rob_DeletedFromCustomerPricingMatrix20031107'. [SQLSTATE 01000]
DBCC results for 'COMMISSION_ADJ'. [SQLSTATE 01000]
There are 1645553 rows in 37801 pages for object 'COMMISSION_ADJ'. [SQLSTATE 01000]
DBCC results for 'SalesSummaryData'. [SQLSTATE 01000]
There are 2288331 rows in 36372 pages for object 'SalesSummaryData'. [SQLSTATE 01000]
DBCC results for 'CDW_CODB'. [SQLSTATE 01000]
There are 2 rows in 1 pages for object 'CDW_CODB'. [SQLSTATE 01000]
DBCC results for 'dtproperties'. [SQLSTATE 01000]
There are 14 rows in 1 pages for object 'dtproperties'. [SQLSTATE 01000]
DBCC results for 'Temp_SalesData_new'. [SQLSTATE 01000]
There are 7275 rows in 94 pages for object 'Temp_SalesData_new'. [SQLSTATE 01000]
DBCC results for 'MKP97'. [SQLSTATE 01000]
There are 818535 rows in 6628 pages for object 'MKP97'. [SQLSTATE 01000]
DBCC results for 'MARKETING_REPORTS_Saved'. [SQLSTATE 01000]
There are 28431 rows in 113 pages for object 'MARKETING_REPORTS_Saved'. [SQLSTATE 01000]
DBCC results for 'Commission_Adjustment'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'Commission_Adjustment'. [SQLSTATE 01000]
DBCC results for 'F1730A'. [SQLSTATE 01000]
There are 1124104 rows in 16059 pages for object 'F1730A'. [SQLSTATE 01000]
DBCC results for 'OEP80U'. [SQLSTATE 01000]
There are 1357451 rows in 11634 pages for object 'OEP80U'. [SQLSTATE 01000]
DBCC results for 'OE40LN'. [SQLSTATE 01000]
There are 1281910 rows in 10155 pages for object 'OE40LN'. [SQLSTATE 01000]
DBCC results for 'sysarticles'. [SQLSTATE 01000]
There are 2 rows in 1 pages for object 'sysarticles'. [SQLSTATE 01000]
DBCC results for 'sysschemaarticles'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'sysschemaarticles'. [SQLSTATE 01000]
DBCC results for 'syspublications'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'syspublications'. [SQLSTATE 01000]
DBCC results for 'CommissionGoalsRange'. [SQLSTATE 01000]
There are 12 rows in 1 pages for object 'CommissionGoalsRange'. [SQLSTATE 01000]
DBCC results for 'LOSGoals'. [SQLSTATE 01000]
There are 107 rows in 1 pages for object 'LOSGoals'. [SQLSTATE 01000]
DBCC results for 'OrderInstallInfo'. [SQLSTATE 01000]
There are 318699 rows in 1241 pages for object 'OrderInstallInfo'. [SQLSTATE 01000]
DBCC results for 'syssubscriptions'. [SQLSTATE 01000]
There are 4 rows in 1 pages for object 'syssubscriptions'. [SQLSTATE 01000]
DBCC results for 'sysarticleupdates'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'sysarticleupdates'. [SQLSTATE 01000]
DBCC results for 'MSpub_identity_range'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'MSpub_identity_range'. [SQLSTATE 01000]
DBCC results for 'systranschemas'. [SQLSTATE 01000]
Msg 2576, Sev 16: IAM page (1:1170538) is pointed to by the previous pointer of IAM page (1:1170540) object ID 1583344705 index ID 0 but was not detected in the scan. [SQLSTATE 42000]
Msg 8947, Sev 16: Table error: Multiple IAM pages for object ID 1583344705, index ID 0 contain allocations for the same interval. IAM pages (1:1170540) and (1:2502333). [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (1:2502332) is pointed to by the previous pointer of IAM page (1:2502333) object ID 1583344705 index ID 0 but was not detected in the scan. [SQLSTATE 42000]
Msg 2593, Sev 16: There are 0 rows in 0 pages for object 'systranschemas'. [SQLSTATE 01000]
Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 1583344705)' (object ID 1583344705). [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'DummyTrans'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 0 rows in 0 pages for object 'DummyTrans'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'InvoiceDownloadCheck'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 9 rows in 1 pages for object 'InvoiceDownloadCheck'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'ORDER_HIST_MUNICH'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 0 rows in 0 pages for object 'ORDER_HIST_MUNICH'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'ACTIONS'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 3864063 rows in 43417 pages for object 'ACTIONS'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'CALLVOLUME_REQ'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 24 rows in 1 pages for object 'CALLVOLUME_REQ'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'COMMISH_GOALS'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 273 rows in 2 pages for object 'COMMISH_GOALS'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'CM210X'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1826290 rows in 97778 pages for object 'CM210X'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'CM30'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 96 rows in 1 pages for object 'CM30'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'CM31'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 32 rows in 1 pages for object 'CM31'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'COMMISSION_ADJ_INDEX'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1 rows in 1 pages for object 'COMMISSION_ADJ_INDEX'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'COMMISSION_DAILY'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1659173 rows in 17841 pages for object 'COMMISSION_DAILY'. [SQLSTATE 01000]
DBCC results for 'COMMISSION_EMP'. [SQLSTATE 01000]
There are 12080 rows in 58 pages for object 'COMMISSION_EMP'. [SQLSTATE 01000]
DBCC results for 'CUST_INVO_SUMMARY'. [SQLSTATE 01000]
There are 9512732 rows in 65156 pages for object 'CUST_INVO_SUMMARY'. [SQLSTATE 01000]
DBCC results for 'DAILY_PHONE'. [SQLSTATE 01000]
There are 1918105 rows in 20566 pages for object 'DAILY_PHONE'. [SQLSTATE 01000]
DBCC results for 'Dates2Run'. [SQLSTATE 01000]
There are 31 rows in 1 pages for object 'Dates2Run'. [SQLSTATE 01000]
DBCC results for 'DAILY_PHONE_ERRORS'. [SQLSTATE 01000]
There are 1701 rows in 18 pages for object 'DAILY_PHONE_ERRORS'. [SQLSTATE 01000]
CHECKDB found 9 allocation errors and 0 consistency errors in database 'SalesHistoryDB'. [SQLSTATE 01000]
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (SalesHistoryDB ). [SQLSTATE 01000]
DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
View 6 Replies
View Related
Dec 12, 2005
Lou writes "Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:958608) object ID 16 index ID 0 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:985853) object ID 16 index ID 2 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:958600) object ID 16 index ID 255 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1067763) object ID 17 index ID 0 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1120026) object ID 17 index ID 2 but was not detected in the scan. [SQLSTATE 42000]
Msg 2576, Sev 16: IAM page (0:0) is pointed to by the previous pointer of IAM page (1:1154482) object ID 17 index ID 3 but was not detected in the scan. [SQLSTATE 42000]
Msg 2536, Sev 16: DBCC results for 'SalesHistoryDB'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysobjects'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 289 rows in 7 pages for object 'sysobjects'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysindexes'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 277 rows in 19 pages for object 'sysindexes'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'syscolumns'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1809 rows in 43 pages for object 'syscolumns'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'systypes'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 28 rows in 1 pages for object 'systypes'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'syscomments'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 301 rows in 101 pages for object 'syscomments'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysfiles1'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'syspermissions'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 311 rows in 3 pages for object 'syspermissions'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysusers'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 28 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysproperties'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 199 rows in 6 pages for object 'sysproperties'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysdepends'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 1768 rows in 11 pages for object 'sysdepends'. [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysreferences'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE 01000]
Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 16)' (object ID 16). [SQLSTATE 01000]
Msg 8990, Sev 16: CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 17)' (object ID 17). [SQLSTATE 01000]
Msg 2536, Sev 16: DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000]
Msg 2593, Sev 16: There are 0 rows in 1 pages for object 'sysfulltextcatalogs'. [SQLSTATE 01000]
DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE 01000]
DBCC results for 'sysfilegroups'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE 01000]
DBCC results for 'IgnoreSalesRep'. [SQLSTATE 01000]
There are 406 rows in 2 pages for object 'IgnoreSalesRep'. [SQLSTATE 01000]
DBCC results for 'invnsrc'. [SQLSTATE 01000]
There are 6101966 rows in 15067 pages for object 'invnsrc'. [SQLSTATE 01000]
DBCC results for 'INVO_ERRS'. [SQLSTATE 01000]
There are 333 rows in 12 pages for object 'INVO
View 4 Replies
View Related
Feb 15, 2006
Hi all,
Would appreciate your words of wisdom on the errors below. It's SQL Server 2000 SP3 on Windows 2000. We had hardware problems on one of the disks in the array the data files are on, which precipitated a number of errors in the Application Event log:
Event ID 17052,MSSQLSERVER,Error: 823, Severity: 24, State: 2 I/O error (torn page) detected during read at offset 0x000002ed448000 in file 'E:SQLDATA2XDB_Data.MDF'.
Running DBCC CHECKDB resulted in the following:
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1901458048, index ID 0: Page (1:1534500) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1901458048, index ID 0, page (1:1534500). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
DBCC results for 'XDB'.
DBCC results for 'sysobjects'.
There are 328 rows in 18 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 843 rows in 56 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 4018 rows in 98 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
<snip lots more successful checks>
DBCC results for 'tblXMLListsRecords'.
There are 3302391 rows in 79187 pages for object 'tblXMLListsRecords'.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'tblXMLListsRecords' (object ID 1901458048).
DBCC results for 'tblPhotosFolder'.
There are 6121 rows in 228 pages for object 'tblPhotosFolder'.
DBCC results for 'tblImageUpload'.
There are 5 rows in 1 pages for object 'tblImageUpload'.
DBCC results for 'tblLogs'.
There are 2049298 rows in 50892 pages for object 'tblLogs'.
CHECKDB found 0 allocation errors and 2 consistency errors in database 'XDB'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (XDB ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
So the questions are - what does the first error mean (the table error)? And does a report of 2 consistency errors in tblXMLListRecords mean that we will lose two records? We have a backup but it would mean losing today's work if we went back to it - admittedly not much, but I'd like to be able to make an informed choice as to whether repairing the database or restoring it would be favourite. Any thoughts gratefully received!
I've also taken a backup of the corrupted database, restored it to another server and run
DBCC CHECKDB ('XDB',REPAIR_ALLOW_DATA_LOSS) with the following results. So now I'm thinking restoring from backup is probably best after all - correct?
DBCC results for 'XDB'.
DBCC results for 'sysobjects'.
There are 329 rows in 18 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 843 rows in 56 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 4018 rows in 95 pages for object 'syscolumns'.
<snip successful checks>
DBCC results for 'tblMenus'.
There are 0 rows in 1 pages for object 'tblMenus'.
DBCC results for 'tblImageProcessingFilenames'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1901458048, index ID 0: Page (1:1534500) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1901458048, index ID 0, page (1:1534500). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1901458048, index ID 1. Page (1:1180423) is missing a reference from previous page (1:1534500). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1901458048, index ID 1. Page (1:1534500) was not seen in the scan although its parent (1:1243134) and previous (1:1232752) refer to it. Check any previous errors.
There are 687 rows in 188 pages for object 'tblImageProcessingFilenames'.
DBCC results for 'tblData15C69B09E60A4DC5B19D8C8BD69E6C15'.
There are 842 rows in 23 pages for object 'tblData15C69B09E60A4DC5B19D8C8BD69E6C15'.
DBCC results for 'tblDataLinksChild15C69B09E60A4DC5B19D8C8BD69E6C15'.
There are 848 rows in 24 pages for object 'tblDataLinksChild15C69B09E60A4DC5B19D8C8BD69E6C15'.
DBCC results for 'tblUpdateFields'.
There are 1 rows in 3 pages for object 'tblUpdateFields'.
DBCC results for 'tblData1FDBC8FBD862435E8AD7C648F37F6D3A'.
There are 5 rows in 1 pages for object 'tblData1FDBC8FBD862435E8AD7C648F37F6D3A'.
DBCC results for 'tblDataLinksChild1FDBC8FBD862435E8AD7C648F37F6D3A'.
There are 5 rows in 1 pages for object 'tblDataLinksChild1FDBC8FBD862435E8AD7C648F37F6D3A'.
DBCC results for 'tblXML031029'.
There are 83683 rows in 3331 pages for object 'tblXML031029'.
DBCC results for 'tblXMLListsRecords'.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
Repair: Page (1:1534500) has been deallocated from object ID 1901458048, index ID 0.
Clustered index successfully restored for object 'dbo.tblXMLListsRecords' in database 'XDB'.
There are 3302279 rows in 79187 pages for object 'tblXMLListsRecords'.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'tblXMLListsRecords' (object ID 1901458048).
CHECKDB fixed 0 allocation errors and 4 consistency errors in table 'tblXMLListsRecords' (object ID 1901458048).
DBCC results for 'tblPhotosFolder'.
There are 6109 rows in 224 pages for object 'tblPhotosFolder'.
DBCC results for 'tblImageUpload'.
There are 5 rows in 1 pages for object 'tblImageUpload'.
DBCC results for 'tblLogs'.
There are 2048554 rows in 50870 pages for object 'tblLogs'.
CHECKDB found 0 allocation errors and 4 consistency errors in database 'XDB'.
CHECKDB fixed 0 allocation errors and 4 consistency errors in database 'XDB'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Please let me know if there is anything else I should post - many thanks in advance.
View 2 Replies
View Related
Apr 27, 2006
Can anyone please tell me why I recieved these errors when running dbcc check db. Thank god it was a user created "test" table in a production database and I was able to just drop the table and rerun dbcc with no errors, but this is the second time this has happened in the last month(I just started this job the week of the first error)- and we ended up having to restore to the last good backup.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652192), slot 3, text ID 225434796032 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652192), slot 4, text ID 225434861568 is not referenced.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1543676547, index ID 255: Page (1:652193) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1543676547, index ID 255, page (1:652193). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 0, text ID 225434730496 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 1, text ID 225434927104 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 2, text ID 225434992640 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 3, text ID 225435058176 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 4, text ID 225435123712 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 5, text ID 225435189248 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 6, text ID 225435254784 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652194), slot 7, text ID 225435320320 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652195), slot 0, text ID 225435385856 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652195), slot 1, text ID 225435451392 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652195), slot 2, text ID 225435516928 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652195), slot 3, text ID 225435582464 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1543676547. The text, ntext, or image node at page (1:652195), slot 4, text ID 225435648000 is not referenced.
DBCC results for 'BILL_PRT_DETAIL'.
There are 909154 rows in 101409 pages for object 'BILL_PRT_DETAIL'.
DBCC results for 'BILLG_ERR_MSGS'.
There are 971 rows in 52 pages for object 'BILLG_ERR_MSGS'.
DBCC results for 'WORK_COMPCY_LEVEL'.
There are 0 rows in 0 pages for object 'WORK_COMPCY_LEVEL'.
DBCC results for 'BILL_PRT_HEADER'.
There are 196396 rows in 24550 pages for object 'BILL_PRT_HEADER'.
DBCC results for 'WORK_COMPCY_TYPE'.
There are 0 rows in 0 pages for object 'WORK_COMPCY_TYPE'.
DBCC results for 'BILL_PRT_MSGS'.
There are 0 rows in 0 pages for object 'BILL_PRT_MSGS'.
DBCC results for 'MTR_TMP_DTA_SEL'.
There are 0 rows in 0 pages for object 'MTR_TMP_DTA_SEL'.
DBCC results for 'WORK_IN_PROGRESS'.
There are 1 rows in 1 pages for object 'WORK_IN_PROGRESS'.
DBCC results for 'BILL_PYMT'.
There are 750053 rows in 19951 pages for object 'BILL_PYMT'.
DBCC results for 'NOTES'.
There are 26812 rows in 457 pages for object 'NOTES'.
DBCC results for 'WORK_ORDER_MASTER'.
There are 0 rows in 0 pages for object 'WORK_ORDER_MASTER'.
DBCC results for 'BUD_BILLG_AMT'.
There are 0 rows in 0 pages for object 'BUD_BILLG_AMT'.
DBCC results for 'NOTES_RELSHP'.
There are 22428 rows in 252 pages for object 'NOTES_RELSHP'.
DBCC results for 'WO_ACT_STAT'.
There are 0 rows in 0 pages for object 'WO_ACT_STAT'.
DBCC results for 'BUD_BILLG_CNSM_HST'.
There are 0 rows in 0 pages for object 'BUD_BILLG_CNSM_HST'.
DBCC results for 'NXT_NBR'.
There are 7 rows in 1 pages for object 'NXT_NBR'.
DBCC results for 'WO_ADDTNL_INFO'.
There are 0 rows in 0 pages for object 'WO_ADDTNL_INFO'.
DBCC results for 'BUD_BILLG_HST'.
There are 0 rows in 0 pages for object 'BUD_BILLG_HST'.
DBCC results for 'PARENT_HST'.
There are 0 rows in 0 pages for object 'PARENT_HST'.
DBCC results for 'WO_APPVL_ROUTING'.
There are 0 rows in 0 pages for object 'WO_APPVL_ROUTING'.
DBCC results for 'BUD_BILLG_WTHR_HST'.
There are 0 rows in 0 pages for object 'BUD_BILLG_WTHR_HST'.
DBCC results for 'PHY_ADDR'.
There are 70776 rows in 7905 pages for object 'PHY_ADDR'.
DBCC results for 'WO_BEHAVIOR_RULE'.
There are 0 rows in 0 pages for object 'WO_BEHAVIOR_RULE'.
DBCC results for 'BUD_BILLG_WTHR_SEV'.
There are 0 rows in 0 pages for object 'BUD_BILLG_WTHR_SEV'.
DBCC results for 'POSTAL_TOWN_CD'.
There are 29539 rows in 569 pages for object 'POSTAL_TOWN_CD'.
DBCC results for 'WO_COMPONENTS'.
There are 0 rows in 0 pages for object 'WO_COMPONENTS'.
DBCC results for 'BUS_UNT'.
There are 1310 rows in 25 pages for object 'BUS_UNT'.
DBCC results for 'cash match'.
There are 738871 rows in 6720 pages for object 'cash match'.
DBCC results for 'POSTED_HISTORY'.
There are 1230436 rows in 26768 pages for object 'POSTED_HISTORY'.
DBCC results for 'WO_CONSTANTS'.
There are 0 rows in 0 pages for object 'WO_CONSTANTS'.
DBCC results for 'BUS_UNT_MSTR'.
There are 0 rows in 0 pages for object 'BUS_UNT_MSTR'.
DBCC results for 'Cashmatch7_30'.
There are 727509 rows in 6619 pages for object 'Cashmatch7_30'.
DBCC results for 'PROFILE_CAT'.
There are 0 rows in 0 pages for object 'PROFILE_CAT'.
DBCC results for 'WO_EDIT_RULE'.
There are 0 rows in 0 pages for object 'WO_EDIT_RULE'.
DBCC results for 'CNSMPTN_SVC_CONTN'.
There are 36776 rows in 928 pages for object 'CNSMPTN_SVC_CONTN'.
DBCC results for 'Trace_cash_match'.
There are 815011 rows in 7412 pages for object 'Trace_cash_match'.
DBCC results for 'PROOF_BILL_PRT_DTL'.
There are 0 rows in 0 pages for object 'PROOF_BILL_PRT_DTL'.
DBCC results for 'WO_MASTER_FILE'.
There are 0 rows in 0 pages for object 'WO_MASTER_FILE'.
DBCC results for 'cash match 8-24'.
There are 815011 rows in 7414 pages for object 'cash match 8-24'.
CHECKDB found 0 allocation errors and 17 consistency errors in table 'cash match 8-24' (object ID 1543676547).
DBCC results for 'PROOF_BILL_PRT_HDR'.
There are 0 rows in 0 pages for object 'PROOF_BILL_PRT_HDR'.
DBCC results for 'CNVRGT_BILLG_DTL'.
There are 0 rows in 0 pages for object 'CNVRGT_BILLG_DTL'.
DBCC results for 'WO_RTG_APPVL_MSTR'.
There are 0 rows in 0 pages for object 'WO_RTG_APPVL_MSTR'.
DBCC results for 'PYMT_TERMS'.
There are 2 rows in 1 pages for object 'PYMT_TERMS'.
DBCC results for 'CNVRGT_BILLG_HDR'.
There are 0 rows in 0 pages for object 'CNVRGT_BILLG_HDR'.
DBCC results for 'WO_STAT'.
There are 0 rows in 0 pages for object 'WO_STAT'.
DBCC results for 'Cash Matching Process'.
There are 836838 rows in 7612 pages for object 'Cash Matching Process'.
DBCC results for 'RD_CYCLE'.
There are 55 rows in 1 pages for object 'RD_CYCLE'.
DBCC results for 'WO_STAT_RULES'.
There are 0 rows in 0 pages for object 'WO_STAT_RULES'.
DBCC results for 'REASON_CD'.
There are 0 rows in 0 pages for object 'REASON_CD'.
DBCC results for 'WO_TYP'.
There are 0 rows in 0 pages for object 'WO_TYP'.
DBCC results for 'COLCT_RULES'.
There are 30 rows in 1 pages for object 'COLCT_RULES'.
DBCC results for 'RECEIPTS_BTCH'.
There are 2109 rows in 44 pages for object 'RECEIPTS_BTCH'.
DBCC results for 'nightly107'.
There are 344086 rows in 3225 pages for object 'nightly107'.
DBCC results for 'WO_TYP_ACT_STAT'.
There are 0 rows in 0 pages for object 'WO_TYP_ACT_STAT'.
DBCC results for 'COMPONENT_MASTER'.
There are 0 rows in 0 pages for object 'COMPONENT_MASTER'.
DBCC results for 'RECEIPTS_I_FILE'.
There are 51698 rows in 3244 pages for object 'RECEIPTS_I_FILE'.
DBCC results for 'NightCash10-12'.
There are 64657 rows in 592 pages for object 'NightCash10-12'.
DBCC results for 'WRK_CENTER_WRK_SCH'.
There are 0 rows in 0 pages for object 'WRK_CENTER_WRK_SCH'.
DBCC results for 'CONS_SVC_CONN_CD'.
There are 1524 rows in 20 pages for object 'CONS_SVC_CONN_CD'.
DBCC results for 'RECEIPT_ITM'.
There are 151581 rows in 6334 pages for object 'RECEIPT_ITM'.
DBCC results for 'Utiligy Cash Match Trace'.
There are 321627 rows in 2928 pages for object 'Utiligy Cash Match Trace'.
DBCC results for 'WRTOFF_GL_CLASS_CD'.
There are 0 rows in 0 pages for object 'WRTOFF_GL_CLASS_CD'.
DBCC results for 'CONTACT_INFO'.
There are 1 rows in 1 pages for object 'CONTACT_INFO'.
DBCC results for 'REFUND_HISTORY'.
There are 906 rows in 24 pages for object 'REFUND_HISTORY'.
DBCC results for 'RECEIPTS_I_FILE2'.
There are 48343 rows in 3022 pages for object 'RECEIPTS_I_FILE2'.
DBCC results for 'CUST_ADDR_REL'.
There are 70611 rows in 2258 pages for object 'CUST_ADDR_REL'.
DBCC results for 'REPORT_TYPE'.
There are 42 rows in 1 pages for object 'REPORT_TYPE'.
DBCC results for 'CUST_CNTRCT_RELSHP'.
There are 0 rows in 0 pages for object 'CUST_CNTRCT_RELSHP'.
DBCC results for 'REQ_READ_SCH'.
There are 1 rows in 1 pages for object 'REQ_READ_SCH'.
DBCC results for 'RESOURCE_ASGNDS'.
There are 0 rows in 0 pages for object 'RESOURCE_ASGNDS'.
DBCC results for 'CUST_INFO'.
There are 36779 rows in 2480 pages for object 'CUST_INFO'.
DBCC results for 'RESOURCE_MASTER'.
There are 0 rows in 0 pages for object 'RESOURCE_MASTER'.
DBCC results for 'RESOURCE_WORK_SCH'.
There are 0 rows in 0 pages for object 'RESOURCE_WORK_SCH'.
DBCC results for 'CUST_PYMT_ACCT'.
There are 0 rows in 0 pages for object 'CUST_PYMT_ACCT'.
DBCC results for 'ROUTE'.
There are 95 rows in 2 pages for object 'ROUTE'.
DBCC results for 'ADDR'.
There are 70767 rows in 861 pages for object 'ADDR'.
DBCC results for 'CUST_STMT_HST'.
There are 0 rows in 0 pages for object 'CUST_STMT_HST'.
DBCC results for 'ROUTE_RD_CYCLE'.
There are 0 rows in 0 pages for object 'ROUTE_RD_CYCLE'.
DBCC results for 'AGING_DAYS_TBL'.
There are 5 rows in 1 pages for object 'AGING_DAYS_TBL'.
DBCC results for 'CUST_SVC_RELSHP'.
There are 73551 rows in 1415 pages for object 'CUST_SVC_RELSHP'.
DBCC results for 'RPT_TYPE_CRITERIA'.
There are 116 rows in 2 pages for object 'RPT_TYPE_CRITERIA'.
DBCC results for 'AMX_MSG_LG'.
There are 0 rows in 0 pages for object 'AMX_MSG_LG'.
DBCC results for 'RPT_VERSION'.
There are 32 rows in 1 pages for object 'RPT_VERSION'.
DBCC results for 'DED_MTR_CONSUM'.
There are 0 rows in 0 pages for object 'DED_MTR_CONSUM'.
DBCC results for 'ASGND_BILL_CAT_CD'.
There are 0 rows in 0 pages for object 'ASGND_BILL_CAT_CD'.
DBCC results for 'RPT_VRSN_CRITERIA'.
There are 15 rows in 1 pages for object 'RPT_VRSN_CRITERIA'.
DBCC results for 'DED_MTR_POS'.
There are 0 rows in 0 pages for object 'DED_MTR_POS'.
DBCC results for 'ASGND_CUST_CAT_CD'.
There are 0 rows in 0 pages for object 'ASGND_CUST_CAT_CD'.
DBCC results for 'SCH_POOL'.
There are 0 rows in 0 pages for object 'SCH_POOL'.
DBCC results for 'DED_MTR_RDING_HIST'.
There are 0 rows in 0 pages for object 'DED_MTR_RDING_HIST'.
CHECKDB found 0 allocation errors and 17 consistency errors in database 'UtiligyPD'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (UtiligyPD ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Thanks!
Anita
View 5 Replies
View Related
Jul 21, 2006
Rick writes "I have a SQL 2000 - SP4 database that is working and get backed up daily. I am trying to restore any of the backups from this database from the past 4 months. All of them get an error when restoring.
"A possible database consistency problem has been detected on the database 'db_name'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on the datbase 'db_name'"
I need 700 records from one of the tables from that backup.
Is there any possible way to recover data from those backups?
Thanks!"
View 1 Replies
View Related
