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

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Table Corruption - DBCC Output

Author  Topic 

rkirk
Starting Member

10 Posts

Posted - 2005-12-14 : 11:43:52
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1513928615, index ID 0: Page (3:33709) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1513928615, index ID 0, page (3:33709), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 95 and 30.
DBCC results for 'Result'.
There are 41589306 rows in 660667 pages for object 'Result'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'Result' (object ID 1513928615).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (LASAR2.dbo.Result ).

rkirk
Starting Member

10 Posts

Posted - 2005-12-14 : 12:45:11
Ran Repair Rebuild and received the following:

Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1513928615, index ID 0: Page (3:33709) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1513928615, index ID 0, page (3:33709), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 95 and 30.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1513928615, index ID 1. Page (3:33709) was not seen in the scan although its parent (3:36665) and previous (3:41236) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1513928615, index ID 1. Page (3:34742) is missing a reference from previous page (3:33709). Possible chain linkage problem.
DBCC results for 'Result'.
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.
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 41589306 rows in 660667 pages for object 'Result'.
CHECKTABLE found 0 allocation errors and 4 consistency errors in table 'Result' (object ID 1513928615).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (LASAR2.dbo.Result repair_rebuild).
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-12-14 : 13:00:56
The output clearly says to run repair_allow_data_loss so why only run repair_rebuild?

Do you have a backup? You're going to lose data when you run repair as repair will delete heap page (3:33709).

Have you done any root cause analysis? (Checked for h/w problems in the SQL errorlog/Windows event log?)

Thanks

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2005-12-14 : 13:06:53
Paul, I expect rkirk will be back in a minute, but just in case not (although I can't be sure that it is relevant) there is a previous thread:

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=53547

which ends up "I'll at least save all of my dbcc outputs next time for posting."

Kristen
Go to Top of Page

rkirk
Starting Member

10 Posts

Posted - 2005-12-14 : 14:28:43
There were no errors in the Event Log, but the SQL error log does have user initiated stack dumps every time corruption error occurs.

I ran repair_allow_data_loss and am able to rebuild the table

The corruption occurred right after/during an index rebuild of the table after a data load.

This is a different server that my previous post. The other server still receives transient corruption errors, which we will likely open a support case for.
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-12-15 : 19:39:38
Wow - surprised you're still getting errors and haven't opened a case yet - hope you're not losing valuable data when this occurs.

What do you mean by user-initiated stack dumps? Can you post some of the stacks please?

Thanks


Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
Go to Top of Page

rkirk
Starting Member

10 Posts

Posted - 2005-12-20 : 17:38:47
We did open one, received a patch and they went away for a while. But they started occurring again a couple of weeks ago.

For the stack dump - This is the first one which occurred after an index rebuild on the Result table. This is the top, what portion do you want to see. I can post it to the forum, but as you know they are large files.

=====================================================================
BugCheck Dump
=====================================================================

This file is generated by Microsoft SQL Server 8.00.2039
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.

Computer type is AT/AT COMPATIBLE.
Current time is 19:54:44 12/13/05.
4 Intel x86 level 6, 549 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.


Memory
MemoryLoad = 74%
Total Physical = 2815 MB
Available Physical = 706 MB
Total Page File = 4193 MB
Available Page File = 2027 MB
Total Virtual = 2047 MB
Available Virtual = 240 MB

*Dump thread - spid = 61, PSS = 0x4d7ad250, EC = 0x4d7ad580
*
* User initiated stack dump. This is not a server exception dump.
*
*Stack Dump being sent to H:\MSSQL\MSSQL$DEV\log\SQLDump0069.txt
* *****************************************************************************
**
*
* BEGIN STACK DUMP:
* 12/13/05 19:54:44 spid 61
*
* ex_raise2: Exception raised, major=79, minor=87, severity=22
*
* Input Buffer 296 bytes -
* UPDATE dbo.Result SET comments= (Select count(*) FROM dbo.vwCommen
* tForResult WITH (NOLOCK) Where Result_Key = dbo.Result.Result_Key
* )
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00CBAFFF 008bb000
* Invalid Address 77F80000 77FFBFFF 0007c000

Go to Top of Page

rkirk
Starting Member

10 Posts

Posted - 2005-12-20 : 18:00:24
Stack #2



Memory
MemoryLoad = 74%
Total Physical = 2815 MB
Available Physical = 704 MB
Total Page File = 4193 MB
Available Page File = 2027 MB
Total Virtual = 2047 MB
Available Virtual = 240 MB

*Stack Dump being sent to H:\MSSQL\MSSQL$DEV\log\SQLDump0070.txt
* *****************************************************************************
**
*
* BEGIN STACK DUMP:
* 12/13/05 19:54:52 spid 61
*
* Exception Address = 004013B3
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000036
* Input Buffer 296 bytes -
* UPDATE dbo.Result SET comments= (Select count(*) FROM dbo.vwCommen
* tForResult WITH (NOLOCK) Where Result_Key = dbo.Result.Result_Key
* )
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00CBAFFF 008bb000
* Invalid Address 77F80000 77FFBFFF 0007c000
* ADVAPI32 7C2D0000 7C334FFF 00065000
Go to Top of Page

rkirk
Starting Member

10 Posts

Posted - 2005-12-20 : 18:01:42
Stack #3


Computer type is AT/AT COMPATIBLE.
Current time is 19:54:59 12/13/05.
4 Intel x86 level 6, 549 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.


Memory
MemoryLoad = 74%
Total Physical = 2815 MB
Available Physical = 704 MB
Total Page File = 4193 MB
Available Page File = 2027 MB
Total Virtual = 2047 MB
Available Virtual = 240 MB

*Stack Dump being sent to H:\MSSQL\MSSQL$DEV\log\SQLDump0072.txt
* *****************************************************************************
**
*
* BEGIN STACK DUMP:
* 12/13/05 19:54:59 spid 0
*
* Exception Address = 7C59BC3F (RaiseException + 00000056 Line 0+00000000)
* Exception Code = 400042ac PRINTSTACK
*
* MODULE BASE END SIZE
* sqlservr 00400000 00CBAFFF 008bb000
* Invalid Address 77F80000 77FFBFFF 0007c000
* ADVAPI32 7C2D0000 7C334FFF 00065000
* KERNEL32 7C570000 7C622FFF 000b3000
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-12-21 : 09:22:11
Looks like they're all record corruptions. Can you reproduce this every time after rebuilding the index? What about on different h/w? You need to open another case with PSS - its going to be too involved to do over the forums.

Thanks

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)
Go to Top of Page

rkirk
Starting Member

10 Posts

Posted - 2005-12-21 : 12:32:44
we have not been able to reproduce the error, but we will contact PSS today. Thanks.
Go to Top of Page

brycesimas
Starting Member

1 Post

Posted - 2007-08-14 : 10:35:51
I am having kind of the same but diffrent problem... I run service pack 4 I keep getting errors like

2007-07-26 11:05:17.35 spid99 ex_raise2: Exception raised, major=79, minor=87, severity=22, attempting to create symptom dump
2007-07-26 11:05:17.60 spid99 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 99, PSS = 0x2bbc51d8, EC = 0x2bbc5508
*
* User initiated stack dump. This is not a server exception dump.
*
*Stack Dump being sent to e:\database\MSSQL\log\SQLDump0011.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 07/26/07 11:05:17 spid 99
*
* ex_raise2: Exception raised, major=79, minor=87, severity=22
*
* & P R O F E S S I 26 00 50 00 52 00 4f 00 46 00 45 00 53 00 53 00 49 00
* O N A L . d b o . 4f 00 4e 00 41 00 4c 00 2e 00 64 00 62 00 6f 00 2e 00
* R e p o r t G e n 52 00 65 00 70 00 6f 00 72 00 74 00 47 00 65 00 6e 00
* e r a l L e d g e 65 00 72 00 61 00 6c 00 4c 00 65 00 64 00 67 00 65 00
* r ; 1 & 72 00 3b 00 31 00 00 00 00 00 26 04 04 03 00 00 00 00
* § Ð 4 47300 00 a7 14 00 09 04 d0 00 34 05 00 34 37 33 30 30 00 00
* § Ð 4 47300 & a7 14 00 09 04 d0 00 34 05 00 34 37 33 30 30 00 00 26
* & & × 01 01 07 00 00 26 01 01 07 00 00 26 02 02 d7 07 00 00
* & 26 04 04 01 00 00 00
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00CBEFFF 008bf000
* ntdll 77F80000 77FFAFFF 0007b000
* ADVAPI32 7C2D0000 7C334FFF 00065000
* KERNEL32 7C570000 7C623FFF 000b4000
* RPCRT4 77D30000 77D9EFFF 0006f000
* MSVCP71 7C3A0000 7C41AFFF 0007b000
* MSVCR71 7C340000 7C395FFF 00056000
* opends60 41060000 41065FFF 00006000
* SHELL32 7CF30000 7D175FFF 00246000
* GDI32 77F40000 77F7BFFF 0003c000
* USER32 77E10000 77E78FFF 00069000
* SHLWAPI 70A70000 70AD5FFF 00066000
* msvcrt 78000000 78044FFF 00045000
* COMCTL32 71710000 71793FFF 00084000
* sqlsort 42AE0000 42B6FFFF 00090000
* ums 41070000 4107CFFF 0000d000
* sqlevn70 41080000 4108AFFF 0000b000
* NETAPI32 02BF0000 02C3FFFF 00050000
* Secur32 02C40000 02C4EFFF 0000f000
* NTDSAPI 02C50000 02C60FFF 00011000
* DNSAPI 02C70000 02C93FFF 00024000
* WSOCK32 02CA0000 02CA7FFF 00008000
* WS2_32 02CB0000 02CC3FFF 00014000
* WS2HELP 02CD0000 02CD7FFF 00008000
* WLDAP32 02CE0000 02D0AFFF 0002b000
* NETRAP 02D10000 02D15FFF 00006000
* SAMLIB 02D20000 02D2FFFF 00010000
* AUTHZ 02D80000 02D8FFFF 00010000
* ole32 03020000 0310EFFF 000ef000
* XOLEHLP 03110000 03117FFF 00008000
* MSDTCPRX 03120000 031DAFFF 000bb000
* MTXCLU 031E0000 031EFFFF 00010000
* VERSION 031F0000 031F6FFF 00007000
* LZ32 03200000 03205FFF 00006000
* CLUSAPI 03210000 0321FFFF 00010000
* RESUTILS 03220000 0322CFFF 0000d000
* USERENV 03230000 03293FFF 00064000
* rnr20 032A0000 032ABFFF 0000c000
* iphlpapi 032F0000 03302FFF 00013000
* ICMP 03310000 03314FFF 00005000
* MPRAPI 03320000 03336FFF 00017000
* OLEAUT32 03340000 033DAFFF 0009b000
* ACTIVEDS 033E0000 0340EFFF 0002f000
* ADSLDPC 03410000 03432FFF 00023000
* RTUTILS 03440000 0344DFFF 0000e000
* SETUPAPI 03450000 034DDFFF 0008e000
* RASAPI32 034E0000 03513FFF 00034000
* rasman 03520000 03530FFF 00011000
* TAPI32 03540000 03561FFF 00022000
* DHCPCSVC 03570000 03588FFF 00019000
* winrnr 039B0000 039B7FFF 00008000
* rasadhlp 039C0000 039C4FFF 00005000
* SSNETLIB 04050000 04065FFF 00016000
* NTMARTA 040A0000 040BCFFF 0001d000
* WINSPOOL 051B0000 051CDFFF 0001e000
* MPR 051D0000 051E0FFF 00011000
* security 05590000 05593FFF 00004000
* msafd 06990000 069ADFFF 0001e000
* wshtcpip 06A00000 06A06FFF 00007000
* SSmsLPCn 06B20000 06B27FFF 00008000
* SSnmPN70 07CD0000 07CD6FFF 00007000
* mswsock 07D60000 07D71FFF 00012000
* kerberos 07DD0000 07E04FFF 00035000
* cryptdll 07E10000 07E1DFFF 0000e000
* MSASN1 07E20000 07E30FFF 00011000
* SQLFTQRY 08250000 08275FFF 00026000
* CLBCATQ 08280000 0830EFFF 0008f000
* sqloledb 08410000 0848CFFF 0007d000
* MSDART 08490000 084B3FFF 00024000
* comdlg32 084C0000 084FDFFF 0003e000
* MSDATL3 085A0000 085B4FFF 00015000
* oledb32 08940000 089AFFFF 00070000
* OLEDB32R 089B0000 089C0FFF 00011000
* msv1_0 08A60000 08A81FFF 00022000
* CRYPT32 08A90000 08B1BFFF 0008c000
* xpsqlbot 08B20000 08B25FFF 00006000
* rsabase 08DF0000 08E12FFF 00023000
* xpstar 08EB0000 08EFCFFF 0004d000
* SQLRESLD 08F00000 08F0BFFF 0000c000
* SQLSVC 08F10000 08F2AFFF 0001b000
* ODBC32 08F30000 08F69FFF 0003a000
* odbcbcp 08F70000 08F75FFF 00006000
* W95SCM 08F80000 08F8CFFF 0000d000
* SQLUNIRL 08F90000 08FBCFFF 0002d000
* SHFOLDER 08FC0000 08FC7FFF 00008000
* odbcint 09110000 09126FFF 00017000
* NDDEAPI 09130000 09136FFF 00007000
* SQLSVC 09140000 09145FFF 00006000
* xpstar 09150000 09158FFF 00009000
* psapi 11430000 1143AFFF 0000b000
* dbghelp 040C0000 041BFFFF 00100000
*
* Edi: 2BBC5508: 2BBC51D8 57AC70D0 54411A40 57AC7450 57AC78C8 570FA038
* Esi: 2BBC51D8: 00000063 00000000 00B6B214 00009977 00000000 00000000
* Eax: 00000000:
* Ebx: 0EF1DD74: 00130010 00610072 00730069 00320065 0020003A 00780045
* Ecx: 0EF1DDD4: 00000000 0001003F 00000000 00000000 00000000 00000000
* Edx: 0012E088: 00000000 2BBC51D8 2BBC5508 00000000 0003000E 000C0100
* Eip: 009BC6FB: 26EB0088 90909090 EC458B90 83E47D8B B3B904C7 8B000000
* Ebp: 0EF1DD58: 0EF1E598 009BD021 2BBC51D8 0EF1EA24 0000004F 00000057
* SegCs: 0000001B:
* EFlags: 00010246: 003D0068 003A0043 0057005C 004E0049 0054004E 0073005C
* Esp: 0EF1DD30: 2BBC5508 2BBC51D8 0EF1DD74 0EF1DDD4 0EF1DD30 0EF1D97C
* SegSs: 00000023:
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump
* 009BC6FB Module(sqlservr+005BC6FB) (GetOSErrString+00005017)
* 009BD021 Module(sqlservr+005BD021) (GetOSErrString+0000593D)
* 006EFB3F Module(sqlservr+002EFB3F) (SQLExit+00134DEF)
* 004AB0C9 Module(sqlservr+000AB0C9)
* 00620164 Module(sqlservr+00220164) (SQLExit+00065414)
* 00405664 Module(sqlservr+00005664)
* 00998CF8 Module(sqlservr+00598CF8) (CDStream::operator=+0004C3BB)
* 009998C8 Module(sqlservr+005998C8) (CDStream::operator=+0004CF8B)
* 00999E3F Module(sqlservr+00599E3F) (CDStream::operator=+0004D502)
* 005443FE Module(sqlservr+001443FE)
* 00544450 Module(sqlservr+00144450)
* 0042E085 Module(sqlservr+0002E085)
* 005442F5 Module(sqlservr+001442F5)
* 0054432F Module(sqlservr+0014432F)
* 008692CF Module(sqlservr+004692CF) (GetIMallocForMsxml+00072B5F)
* 00430C79 Module(sqlservr+00030C79)
* 00436C34 Module(sqlservr+00036C34)
* 00862E97 Module(sqlservr+00462E97) (GetIMallocForMsxml+0006C727)
* 0040CFD7 Module(sqlservr+0000CFD7)
* 00618C6A Module(sqlservr+00218C6A) (SQLExit+0005DF1A)
* 0040F670 Module(sqlservr+0000F670)
* 0040F928 Module(sqlservr+0000F928)
* 0041CC33 Module(sqlservr+0001CC33)
* 0041B5A7 Module(sqlservr+0001B5A7)
* 0041B9AD Module(sqlservr+0001B9AD)
* 0041B7CB Module(sqlservr+0001B7CB)
* 004415C5 Module(sqlservr+000415C5)
* 004417EC Module(sqlservr+000417EC)
* 00429072 Module(sqlservr+00029072)
* 41071B56 Module(ums+00001B56) (ProcessWorkRequests+000002D9)
* 41072724 Module(ums+00002724) (ThreadStartRoutine+00000098)
* 7C34940F Module(MSVCR71+0000940F) (endthread+000000AA)
* 7C57B396 Module(KERNEL32+0000B396) (lstrcmpiW+000000B7)
* -------------------------------------------------------------------------------
2007-07-26 11:05:29.50 spid99 Stack Signature for the dump is 0xD0A1C6C2
2007-07-26 11:05:29.53 spid99 Error: 7987, Severity: 22, State: 1

DBCC check completes with NO ERRORS but ever 1-2 weeks i get like 4-8 of these messages
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2007-08-17 : 19:48:06
See http://support.microsoft.com/kb/828337 - looks like you'll need to contact Product Support to help debug this.

Thanks

Paul Randal
Managing Director, SQLskills.com
Go to Top of Page
   

- Advertisement -