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. :)
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 ).
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.
I have been running log shipping for more than a year now and it has been very successful until just recently. For some reason the SQL Agent jobs that backup the database, ship it across the network to a standby server and restore it are failing. On the source server the backup process is running, the log shipping is running however when it tries to restore it on the destination server it fails with the following error:
SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147217900 (80040E14); Provider Error: 3013 (BC5) Error string: RESTORE DATABASE is terminating abnormally. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error: -2147217900 (80040E14); Provider Error: 3270 (CC6) Error string: An internal consistency error occurred. Contact Technical Support for assistance. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error: 0 (0); Provider Error: 3211 (C8B) Error string: 10 percent restored. Error source: Microsoft OLE DB Prov... Process Exit Code 1. The step failed.
If I delete the database on the destination server, re-run the sql agent job that ships the backup job, and re-run the restore job on the destination server the process will succeed without error. This tells me the original backup was fine but something may have been lost during the shipping. Have you ever seen this message before? What does it mean and what should I be looking at to resolve the error?
I have a sql databaseI run dbcc checkdb and get no errorsI go to backup the database in enterprise manager, and it won'trestore because it has internal consistency errorsI can go back to an older version of the databaseI run a particular procedure in our accounting software packageNever do I get errors when running dbcc checkdbSometimes I get the backup and restore problem, sometimes I don'tI am doing this on a test server with about 220 megs of RAMI am trying the dbcc checkdb ('dbname',REPAIR_REBUILD) commandAny other ideas?
Hi all, i have copied out the database backup from development center to my local machine,it is having approx.8GB in size and when i m trying to restote this database backup in SQL Server 2000 it is showing me error. An internal consistency error occurred. Contact Technical Support for assistance. RESTORE DATABASE is terminating abnormally. Plz. anyone can help me..
Server: Msg 3270, Level 16, State 1, Line 1 An internal consistency error occurred. Contact Technical Support for assistance. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally.
I'm getting the following output from dbcc checktable(sysdtssteplog):
Msg 8928, Level 16, State 1, Line 2 Object ID 594101157, index ID 0: Page (1:744) could not be processed. See other errors for details. Msg 8939, Level 16, State 98, Line 2 Table error: Object ID 594101157, index ID 0, page (1:744). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. Msg 8976, Level 16, State 1, Line 2 Table error: Object ID 594101157, index ID 1. Page (1:744) was not seen in the scan although its parent (1:4660) and previous (1:607) refer to it. Check any previous errors. Msg 8978, Level 16, State 1, Line 2 Table error: Object ID 594101157, index ID 1. Page (1:745) is missing a reference from previous page (1:744). Possible chain linkage problem. CHECKTABLE found 0 allocation errors and 4 consistency errors in table 'sysdtssteplog' (object ID 594101157). repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (msdb.dbo.sysdtssteplog ).
Is this a DTS package or log file I can just remove, or can I just somehow remove that data from the table? I ask this because all the DTS packages seem to be running (and logging) fine.
Or will this involve restore and replace? What direction should I go from here?
I have not seen any hardware errors on this machine. Yet.
Hi, In my database, when I try to start sql service, I got following message in event view.
SQL server is sql express version Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86) Mar 23 2007 16:28:52 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
10/09/2007 10:48:47,spid5s,Unknown,Recovery is complete. This is an informational message only. No user action is required. 10/09/2007 10:48:47,spid15s,Unknown,SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:9; actual 0:0). It occurred during a read of page (1:9) in database ID 8 at offset 0x00000000012000 in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmagirisilica_s24.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information<c/> see SQL Server Books Online. 10/09/2007 10:48:47,spid15s,Unknown,Error: 824<c/> Severity: 24<c/> State: 2.
When I try to make dbcc dbcheckdb ... I got this.
Msg 945, Level 14, State 2, Line 1 Database 'magirisilica_s24' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
I am trying to restore a production database backup to a new location on a development workstation, and it fails with "An internal consistency error occurred, Contact Support". When I tried this on a more powerful workstation it ran without a hitch. The db is about 1.5GB, and I think the dev workstation may be running out of resources during the restore. I stopped non-essential services and ran from TSQL, and it still fails. Any suggestions other than getting a better workstation?
I'm getting the following error on our merge contents table in one of our DBs:
Msg 8952, Level 16, State 1, Line 1 Table error: Database 'ks241', index 'MSmerge_contents.nc3MSmerge_contents' (ID 1950682047) (index ID 3). Extra or invalid key for the keys: Msg 8956, Level 16, State 1, Line 1 Index row (1:1893:42) with values (partchangegen = NULL and tablenick = 17665001 and rowguid = AEAE7256-F571-478E-B2B4-D142B47C38C1) points to the data row identified by (). Msg 8952, Level 16, State 1, Line 1 Table error: Database 'ks241', index 'MSmerge_contents.nc3MSmerge_contents' (ID 1950682047) (index ID 3). Extra or invalid key for the keys: Msg 8956, Level 16, State 1, Line 1 Index row (1:1893:66) with values (partchangegen = NULL and tablenick = 17665001 and rowguid = B94F1591-33B0-4625-A269-DB9B8B05BCCE) points to the data row identified by (). CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'MSmerge_contents' (object ID 1950682047). repair_fast is the minimum repair level for the errors found by DBCC CHECKTABLE (ks241.dbo.MSmerge_contents ).
There are no other corruption issues on the server that I can find. I do not believe there are any current hardware issues, though I am not on site.
What would be the best way to resolve this? Is recreating or defrag/rebuild the index an option, here? Or can I just run a repair on this? Since it's a merge table, I'm a little gun shy, having limited experience with replication.
Thanks.
____________________________________________________________________________________ "Believe in those who are seeking the truth. Doubt those who say they have found it." -Andre Gide
Had a recent drive failure on or server. Subsequently Our sql database failed to backup. Ran dbcc checkdb and got the following errors:
Msg 8966, Level 16, State 2, Line 1 Unable to read and latch page (1:241724) with latch type SH. 1(Incorrect function.) failed.
Msg 2533, Level 16, State 1, Line 1 Table error: page (1:241724) allocated to object ID 370100359, index ID 3, partition ID 868679827259392, alloc unit ID 868679827259392 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
every few days i'm getting an error in the application log , eventID 824, saying 'SQL Server detected a logical consistency-based i/o error; incorrect checksum. it then recommends completing a full database consistency check (dbcc checkdb).
i have run the dbcc checkdb ('databasename') and it is returning an error msg of:
Msg 8697, Level 16, State 215, Line 1 An internal error occurred in DBCC which prevented further processing Msg 8921, Level 16, State 1, Line 1 Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors
i have oodles of disk space left. any ideas on where to go from here.
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x1a00d2fd; actual: 0x1a02d2fd). It occurred during a read of page (1:103329) in database ID 11 at offset 0x00000032742000 in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAServer02.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database c (Source: MSSQLServer, Error number: 824) Get help: http://help/824
We have received a backup of a database from an external company for a project that we are taking over. We have attempted to restore the database and it fails giving us the error: "Internal consistency error occurred."
We have run the restore verifyonly command with the results: "The backup set is valid." However, I don't have confidence that the verify is telling the complete story.
It appears that the database is restored and the overall restore is failing on the transaction log file.
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)?
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...
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
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.
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)
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?
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.
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.
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.
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?
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.
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.
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]
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
