Dec 2, 2005
I actually ran this on a reporting copy of my DB (restored once a week). I would guess the errors are present in the main copy as well. I fear running the check during production hours as it takes 2.5 hours and the system (4 processor) is under a lot of load for almost the entire day and much of the night.
So I've got errors on the tables:
sessions ID(462624691)
map ID(510624862)
links ID(1790629422)
It looks like the repair with data loss is my only choice but I would definitely prefer to know which rows are messed up. I'm also wary of running the repair as it's probably going to take well over an hour on the huge sessions table. I don't know how it got in this corrupted state. I inherited a DB of this size (50GB) that's been known to be very sensitive to any admin or index fiddling due to the high load. After I get this repaired I feel I should run the CHECKDB in a maintenance plan but I'm not sure if this will cause slowdowns in itself if it runs for 2.5 hours. The DB backup takes over 2 hours leaving almost no spare time in the off peak time.
Any advice/suggestions? Thanks.
DBCC results for 'dbloc'.
DBCC results for 'sessions'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 462624691, index ID 0: Page (1:9517861) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 462624691, index ID 0: Page (1:9659261) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 462624691, index ID 7: Page (1:5825743) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 462624691, index ID 7: Page (1:5890660) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 462624691, index ID 7: Page (1:5931145) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 462624691, index ID 7: Page (1:5950021) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 462624691, index ID 7: Page (1:5978420) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 462624691, index ID 7: Page (1:5988261) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 462624691, index ID 7: Page (1:6046306) could not be processed. See other errors for details.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 109 and 110.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 112 and 113.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 113 and 114.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 114 and 115.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 117 and 118.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 118 and 119.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 121 and 122.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 122 and 123.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 0. Keys out of order on page (1:11853027), slots 124 and 125.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 510624862, index ID 0: Page (1:11858027) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 510624862, index ID 0, page (1:11858027). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 510624862, index ID 0: Page (1:11865547) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 510624862, index ID 0, page (1:11865547). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 510624862, index ID 2: Page (1:11889147) could not be processed. See other errors for details.
DBCC results for 'sessions'.
There are 153364096 rows in 3102681 pages for object 'sessions'.
CHECKDB found 0 allocation errors and 9 consistency errors in table 'sessions' (object ID 462624691).
DBCC results for 'map'.
Server: Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 510624862, index ID 2, page (1:11889147). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 3. Keys out of order on page (1:11931268), slots 206 and 207.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 3. Keys out of order on page (1:11931268), slots 209 and 210.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 3. Keys out of order on page (1:11931268), slots 210 and 211.
Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 510624862, Index ID 3. Keys out of order on page (1:11931268), slots 230 and 231.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 510624862, index ID 11: Page (1:11988308) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 510624862, index ID 11, page (1:11988308), row 194. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 7251 and 18.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 510624862, index ID 11: Page (1:12003992) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 510624862, index ID 11, page (1:12003992). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
There are 15576829 rows in 65455 pages for object 'map'.
CHECKDB found 0 allocation errors and 23 consistency errors in table 'map' (object ID 510624862).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1790629422, index ID 16: Page (1:11471717) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1790629422, index ID 16, page (1:11471717), row 88. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 3500 and 28.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1790629422, index ID 16: Page (1:11474112) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1790629422, index ID 16, page (1:11474112), row 108. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 745 and 20.
DBCC results for 'links'.
There are 9919777 rows in 124284 pages for object 'links'.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'links' (object ID 1790629422).
CHECKDB found 0 allocation errors and 36 consistency errors in database 'dbloc'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (dbloc ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
View 2 Replies
View Related
Aug 15, 2014
I have a table that contains 1.6 million rows, and is about 2.6GB in size.One of the columns is ntext and contained some xml.Realistically, I don't need the xml for anything older than about 2 months, however, i'd like to keep some of the data in the other fields.I decided that if I updated the xml to blank, I would see some considerable space savings, however that doesn't appear to be the case.This is the output of sp_spaceused for my table
name rows reserved data index unused
CommitmentsForPosting1660979 2740336 KB 1857104 KB312 KB882920 KB
After I updated the table to remove the xml, the output of sp_spaceused remained the same.My first thought was that it was probably statistics, so I updated statistics for the table, and nothing changed.I then updated statistics for everything in the database, still no change.I then ran DBCC CLEANTABLE for that table. I didn't really expect it to make a difference, and no surprise, it didn't.
The index on the table is a clustered index on just a GUID column.I rebuilt the index and again it still made no difference (that's a bit of a lie - index_size changed by a few hundred KB)my next test was to run 'select * into XXX from YYY' to create a copy of this table with the same data and data types. I also created the same clustered index from the original table onto the new one.If I then run sp_spaceused on this new copy of the table, I see what I expect to see in sp_spaceused - a table using approximately 256MB of space
name rows reserved data index unused
SPS_TEST 1660979 266400 KB 266400 KB 304 KB56 KB
To be honest, this isn't hugely critical, but I'm just curious as to why the original table is still reporting 2.6GB size, when I think it should probably be nearer 256MB.
View 9 Replies
View Related
Jul 8, 2007
Hi Cindy,
After hours (days?) researching this, your name keeps popping up, you must be the GOTO person for VFP. So:
We have a server that runs a VFP application and stores .dbf free tables in a directory shared as F:apps ele.
I am working on an XPPro box running SQL Server Express 2005 using Management Studio Express.
I am logged on as a user with administrator rights for the domain
We would like to be able to query this data and move it to our SQL tables as needed.
Here is what I have:
EXEC sp_addlinkedserver @server = 'tele',
@srvproduct = 'VFP',
@provider = 'VFPOLEDB',
@datasrc = 'F:apps ele',
@provstr = 'VFPOLEDB.1'
GO
SELECT * FROM tele...PROSPECT_DIVU
Here is what I get:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "VFPOLEDB" for linked server "tele" reported an error. Access denied.
Msg 7301, Level 16, State 2, Line 1
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "VFPOLEDB" for linked server "tele".
I have tried:
exec sp_addlinkedsrvlogin
@rmtsrvname = 'tele',
@useself = false,
@locallogin = NULL,
@rmtuser = 'admin',
@rmtpassword = NULL
go
Same result.
I have also tried:
EXEC sp_addlinkedserver
'tele2',
'Jet 4.0',
'Microsoft.Jet.OLEDB.4.0',
'F:apps ele',
NULL,
'dBase IV'
GO
When I run:
select * from tele2...prospect_divu
I get:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "tele2" returned message "The Microsoft Jet database engine could not find the object 'prospect_divu'. Make sure the object exists and that you spell its name and the path name correctly.".
Msg 7311, Level 16, State 2, Line 1
Cannot obtain the schema rowset "DBSCHEMA_COLUMNS" for OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "tele2". The provider supports the interface, but returns a failure code when it is used.
What would you suggest?
View 4 Replies
View Related