Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
zardoz
Starting Member
3 Posts |
Posted - 2007-01-18 : 08:11:40
|
Hi,we consistently have logical page errors on one of our SQL Servers.The output from CHECKDB is shown below. Any ideas why this keeps happening. We recently replaced the disk thinking this would solve the problem.DBCC results for 'TMP_tbl_Pay_Totals'.Server: Msg 2533, Level 16, State 1, Line 1Table error: Page (1:391469) allocated to object ID 1412968160, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.AND later on Server: Msg 2533, Level 16, State 1, Line 1Table error: Page (1:398376) allocated to object ID 1412968160, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.Server: Msg 2533, Level 16, State 1, Line 1Table error: Page (1:398377) allocated to object ID 1412968160, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.Server: Msg 2533, Level 16, State 1, Line 1Table error: Page (1:398378) allocated to object ID 1412968160, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.Server: Msg 2533, Level 16, State 1, Line 1Table error: Page (1:398379) allocated to object ID 1412968160, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.Server: Msg 2533, Level 16, State 1, Line 1Table error: Page (1:398448) allocated to object ID 1412968160, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.Server: Msg 2533, Level 16, State 1, Line 1Table error: Page (1:398449) allocated to object ID 1412968160, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.Server: Msg 2533, Level 16, State 1, Line 1Table error: Page (1:398450) allocated to object ID 1412968160, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.Server: Msg 2533, Level 16, State 1, Line 1Table error: Page (1:398451) allocated to object ID 1412968160, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.Server: Msg 2533, Level 16, State 1, Line 1Table error: Page (1:398452) allocated to object ID 1412968160, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.Server: Msg 2533, Level 16, State 1, Line 1Final bitCHECKDB found 0 allocation errors and 11 consistency errors in database 'ISS'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (ISS ).Any help or ideas much appreciated. |
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2007-01-18 : 09:04:54
|
Can you do the following please?dbcc traceon (3604)godbcc page (ISS, 1, 398376, 3)goand post the results?And some questions:1) When did the errors start happening?2) Are they always for the same pages?3) When you replaced the disk, did you restore a clean copy of the database onto the new drives?4) what version + SP are you running?ThanksPaul RandalPrincipal Lead Program Manager, Microsoft SQL Server Core Storage Engine (Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)http://blogs.msdn.com/sqlserverstorageengine/default.aspx |
|
|
zardoz
Starting Member
3 Posts |
Posted - 2007-01-22 : 06:52:45
|
dbcc page output attached. This was run today and the issue occurred last thursday so I am not sure if this is useful. Maybe I need to run it again immediately after the issue occurs.DBCC execution completed. If DBCC printed error messages, contact your system administrator.PAGE: (1:398376)----------------BUFFER:-------BUF @0x01443F40---------------bpage = 0x529CA000 bhash = 0x00000000 bpageno = (1:398376)bdbid = 10 breferences = 1 bstat = 0x9bspin = 0 bnext = 0x00000000 PAGE HEADER:------------Page @0x529CA000----------------m_pageId = (1:398376) m_headerVersion = 1 m_type = 2m_typeFlagBits = 0x0 m_level = 0 m_flagBits = 0x24m_objId = 1306487733 m_indexId = 2 m_prevPage = (1:398215)m_nextPage = (1:398377) pminlen = 25 m_slotCnt = 270m_freeCnt = 806 m_freeData = 6846 m_reservedCnt = 0m_lsn = (6919:50:25) m_xactReserved = 0 m_xdesId = (0:28770643)m_ghostRecCnt = 0 m_tornBits = 0 Allocation Status-----------------GAM (1:2) = ALLOCATED SGAM (1:3) = NOT ALLOCATEDPFS (1:396312) = 0x40 ALLOCATED 0_PCT_FULL DIFF (1:6) = CHANGEDML (1:7) = NOT MIN_LOGGED (270 row(s) affected)DBCC execution completed. If DBCC printed error messages, contact your system administrator.1) The errors have happened intermittently for about a year. DBCC checkdb or dropping and recreating indexes has solved it.2) I am not sure whether the page is always the same - we didnt keep a note (guess we should have). My gut feeling is no.3) Yes4)2000 8.00.760 (SP3)Thanks for your help.Jonathan |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2007-01-24 : 08:08:35
|
Have you replaced the IO controller(s) too? If not, are their firmware up-to-date? How often are the corruptions happening?Paul RandalPrincipal Lead Program Manager, Microsoft SQL Server Core Storage Engine (Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)http://blogs.msdn.com/sqlserverstorageengine/default.aspx |
|
|
zardoz
Starting Member
3 Posts |
Posted - 2007-02-02 : 09:59:35
|
Hi,sorry about the delay in getting back to you have been busy (as I am sure have you)We didnt replace the I/O controllers, however the firmware is up to date. The corruptions probably happen once a week. We are planning to apply SP4 in the next few weeks to try and resolve this but have to do some testing firstThanks,Jonathan |
|
|
|
|
|
|
|