September 4, 2008 at 3:50 pm
Page (1:84617), slot 40 for text, ntext, or image node does not exist.. has any one come across this before?
Warm Regards,
Arthur Lorenzini
Sioux Falls, SD
September 5, 2008 at 12:45 am
Database corruption. Do you have an up-to-date backup?
Please run the following and post the output.
DBCC CHECKDB ( < Database name > ) WITH NO_INFOMSGS
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 10, 2008 at 12:33 pm
OK, it poped again today:
Page (1:69724084), slot 5 for text, ntext, or image node does not exist..
I ran the following command but can't dechiper the contents:
DBCC TRACEON (3604);
DBCC PAGE ('ProMaxOnline',1,69724084,1)
PAGE: (1:69724084)
------------------
BUFFER:
-------
BUF @0x01AD39C0
---------------
bpage = 0x54F1E000 bhash = 0x00000000 bpageno = (1:69724084)
bdbid = 7 breferences = 1 bstat = 0x9
bspin = 0 bnext = 0x00000000
PAGE HEADER:
------------
Page @0x54F1E000
----------------
m_pageId = (1:69724084) m_headerVersion = 1 m_type = 3
m_typeFlagBits = 0x0 m_level = 0 m_flagBits = 0x8008
m_objId = 1307971836 m_indexId = 255 m_prevPage = (0:0)
m_nextPage = (0:0) pminlen = 0 m_slotCnt = 18
m_freeCnt = 6768 m_freeData = 7873 m_reservedCnt = 168
m_lsn = (1349524:7287:57) m_xactReserved = 168 m_xdesId = (1:1330201232)
m_ghostRecCnt = 0 m_tornBits = 1040130
Allocation Status
-----------------
GAM (1:69527552) = ALLOCATED
SGAM (1:69527553) = NOT ALLOCATED
PFS (1:69718560) = 0x41 ALLOCATED 50_PCT_FULL DIFF (1:69527558) = CHANGED
ML (1:69527559) = NOT MIN_LOGGED
DATA:
-----
Slot 15, Offset 0x60
--------------------
Record Type = BLOB_FRAGMENT Record Attributes =
54F1E060: 04640008 2ca50000 00001e3b 7f310003 ..d....,;.....1.
54F1E070: 36317f30 7f303033 7f357f31 39337f30 0.16300.1.5.0.39
54F1E080: 7f32337f 327f3532 7f307f30 7f307f30 .32.25.20.0.0.0.
54F1E090: 7f307f30 7f307f30 7f307f30 7f307f30 0.0.0.0.0.0.0.0.
54F1E0A0: 7f307f30 7f307f30 80307f30 7f317f32 0.0.0.0.0.0.2.1.
54F1E0B0: 34323631 7f307f39 7f307f35 30303436 16249.0.5.0.6400
54F1E0C0: 3731357f 31347f35 337f3532 7f303033 .5175.4125.3300.
54F1E0D0: 7f307f30 7f307f30 7f307f30 7f307f30 0.0.0.0.0.0.0.0.
54F1E0E0: 7f307f30 7f307f30 7f307f30 7f307f30 0.0.0.0.0.0.0.0.
54F1E0F0: 7f358030 36317f30 7f393432 7f357f31 0.5.0.16249.1.5.
54F1E100: 337f3733 30337f37 7f33327f 7f307f30 37.37.30.23.0.0.
54F1E110: 7f307f30 7f307f30 307f3333 307f307f 0.0.0.0.33.0.0.0
54F1E120: 307f307f 307f307f 307f307f 307f307f .0.0.0.0.0.0.0.0
54F1E130: 307f3880 3336317f 317f3030 307f357f .8.0.16300.1.5.0
54F1E140: 337f307f 35327f32 7f30327f 7f307f30 .0.32.25.20.0.0.
54F1E150: 7f307f30 7f307f30 30337f30 307f307f 0.0.0.0.0.30.0.0
54F1E160: 7f34327f 7f307f30 7f307f30 80307f30 .24.0.0.0.0.0.0.
54F1E170: 307f3631 3336317f 317f3030 307f357f 16.0.16300.1.5.0
54F1E180: 7f35337f 327f3233 30327f35 307f307f .35.32.25.20.0.0
54F1E190: 307f307f 307f307f 307f307f 307f307f .0.0.0.0.0.0.0.0
54F1E1A0: 307f307f 307f307f 307f307f 3180307f .0.0.0.0.0.0.0.1
54F1E1B0: 7f307f37 34323631 7f317f39 7f307f35 7.0.16249.1.5.0.
54F1E1C0: 31357f30 347f3537 7f353231 30303333 0.5175.4125.3300
54F1E1D0: 307f307f 307f307f 307f307f 307f307f .0.0.0.0.0.0.0.0
54F1E1E0: 307f307f 307f307f 307f307f 307f307f .0.0.0.0.0.0.0.0
54F1E1F0: 3280307f 7f307f32 30333631 7f317f30 .0.22.0.16300.1.
54F1E200: 7f307f35 327f3633 32327f39 307f307f 5.0.36.29.22.0.0
54F1E210: 307f307f 307f307f 307f307f 307f307f .0.0.0.0.0.0.0.0
54F1E220: 307f307f 307f307f 307f307f 307f307f .0.0.0.0.0.0.0.0
54F1E230: 7f333280 36317f30 7f393432 7f357f31 .23.0.16249.1.5.
54F1E240: 39337f30 7f32337f 327f3532 7f307f30 0.39.32.25.20.0.
54F1E250: 7f307f30 7f307f30 7f307f30 7f307f30 0.0.0.0.0.0.0.0.
54F1E260: 7f307f30 7f307f30 7f307f30 80307f30 0.0.0.0.0.0.0.0.
54F1E270: 307f3134 3836317f 317f3030 307f357f 41.0.16800.1.5.0
54F1E280: 7f34337f 327f3233 30327f35 307f307f .34.32.25.20.0.0
54F1E290: 307f307f 337f307f 7f307f33 327f3033 .0.0.0.33.0.30.2
54F1E2A0: 7f307f39 33327f30 307f307f 307f307f 9.0.0.23.0.0.0.0
54F1E2B0: 3480307f 7f307f33 34323631 7f317f39 .0.43.0.16249.1.
54F1E2C0: 7f307f35 30303436 3731357f 31347f35 5.0.6400.5175.41
54F1E2D0: 337f3532 7f303033 7f307f30 7f307f30 25.3300.0.0.0.0.
54F1E2E0: 38357f30 307f3030 347f307f 7f303536 0.5800.0.0.4650.
54F1E2F0: 7f307f30 35323733 307f307f 307f307f 0.0.3725.0.0.0.0
54F1E300: 3480307f 7f307f39 30383631 7f317f30 .0.49.0.16800.1.
54F1E310: 7f307f35 39327f30 7f33327f 307f3032 5.0.0.29.23.20.0
54F1E320: 307f307f 307f307f 307f307f 307f307f .0.0.0.0.0.0.0.0
54F1E330: 307f307f 307f307f 307f307f 307f307f .0.0.0.0.0.0.0.0
54F1E340: 7f303580 36317f30 7f303038 7f357f31 .50.0.16800.1.5.
54F1E350: 7f307f30 327f3932 30327f33 307f307f 0.0.29.23.20.0.0
54F1E360: 307f307f 307f307f 307f307f 307f307f .0.0.0.0.0.0.0.0
54F1E370: 307f307f 307f307f 307f307f 3580307f .0.0.0.0.0.0.0.5
54F1E380: 7f307f33 30333631 7f317f30 7f307f35 3.0.16300.1.5.0.
54F1E390: 32337f30 7f35327f 307f3032 307f307f 0.32.25.20.0.0.0
54F1E3A0: 307f307f 307f307f 7f30337f 307f3832 .0.0.0.0.30.28.0
54F1E3B0: 327f307f 7f307f32 7f307f30 80307f30 .0.22.0.0.0.0.0.
54F1E3C0: 307f3137 3236317f 307f3934 307f357f 71.0.16249.0.5.0
54F1E3D0: 3034367f 31357f30 347f3537 7f353231 .6400.5175.4125.
54F1E3E0: 30303333 307f307f 307f307f 307f307f 3300.0.0.0.0.0.0
54F1E3F0: 307f307f 307f307f 307f307f 307f307f .0.0.0.0.0.0.0.0
54F1E400: 307f307f 3780307f 7f307f32 30333631 .0.0.0.72.0.1630
54F1E410: 7f317f30 7f307f35 38327f30 7f35327f 0.1.5.0.0.28.25.
54F1E420: 307f3032 307f307f 307f307f 307f307f 20.0.0.0.0.0.0.0
54F1E430: 7f37327f 307f3632 307f307f 307f307f .27.26.0.0.0.0.0
54F1E440: 7f37317f 80307f30 307f3338 3935317f .17.0.0.83.0.159
54F1E450: 317f3437 307f357f 327f307f 32327f38 74.1.5.0.0.28.22
54F1E460: 7f38317f 7f307f30 7f307f30 7f307f30 .18.0.0.0.0.0.0.
54F1E470: 7f307f30 7f307f30 7f307f30 7f307f30 0.0.0.0.0.0.0.0.
54F1E480: 7f307f30 34388030 317f307f 34373935 0.0.0.84.0.15974
54F1E490: 357f317f 307f307f 7f38327f 317f3232 .1.5.0.0.28.22.1
54F1E4A0: 7f307f38 7f307f30 7f307f30 7f307f30 8.0.0.0.0.0.0.0.
54F1E4B0: 7f307f30 7f307f30 7f307f30 7f307f30 0.0.0.0.0.0.0.0.
54F1E4C0: 80307f30 0.0.
Slot 16, Offset 0x4c4
---------------------
Record Type = BLOB_FRAGMENT Record Attributes =
54F1E4C4: 00540008 2ca50000 00001e3b 00050004 ..T....,;.......
54F1E4D4: 00000001 00000002 00000456 0427e7b4 ........V.....'.
54F1E4E4: 000f0001 1859ad6c 00080891 1859ad6c ....l.Y.....l.Y.
54F1E4F4: 006ceffb 00000004 1859adb8 00000000 ..l.......Y.....
54F1E504: 69bafa20 2f9c140f 1859ad98 0040a2ba ..i.../..Y...@.
54F1E514: 0052c76b k.R.
Slot 17, Offset 0x518
---------------------
Record Type = BLOB_FRAGMENT Record Attributes =
54F1E518: 00540008 2ca60000 00001e3b 001e0000 ..T....,;.......
54F1E528: 00000002 31307f31 7f31307f 307f3130 ....1.01.01.01.0
54F1E538: 31307f31 7f31307f 397f3730 38343530 1.01.01.07.90548
54F1E548: 00003537 00000000 00000000 00000000 75..............
54F1E558: 00000000 00000000 00000000 00000000 ................
54F1E568: 00000000 ....
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Warm Regards,
Arthur Lorenzini
Sioux Falls, SD
September 10, 2008 at 12:55 pm
Also how would I find which table is being effected? I can't run DBCC CheckDB because this DB is 689GB and it would bring it to its knees.
Warm Regards,
Arthur Lorenzini
Sioux Falls, SD
September 10, 2008 at 1:18 pm
SELECT Object_name(1307971836)
That's the ID of the table and is given in the header of the page
Two things.
You need to run a checkDB. Until you do, you won't know if there's other, more severe corruption. If you can't do it now, do it over the weekend or whenever the server's quiet. 600 GB database shouldn't take too long, provided your drives aren't overloaded. I had a 1 TB database on a slow (badly configured) SAN that took about 5 hours to check completely
If you absolutely cannot checkDB the database, take a backup, restore the backup elsewhere and run a check on that.
Second, if you have recurring corruption, there's very likely something wrong with the hardware. Corruption shouldn't happen and SQL doesn't corrupt it's own files (unless you've run into a bug). Check the windows event log, check any hardware logs that you may have, if you can run an IO stress test (SQLIOSim) then do so.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 10, 2008 at 1:26 pm
I found the table that is indicated in the objecid and it contains Text datatype. I know that this is a blob field and have read somewhere this could be causing it. Would a DBCC CheckAlloc (tablename) do me any good at this point?
Warm Regards,
Arthur Lorenzini
Sioux Falls, SD
September 10, 2008 at 1:32 pm
Would using NOLOCKS be a underlying cause for this?
Warm Regards,
Arthur Lorenzini
Sioux Falls, SD
September 10, 2008 at 1:42 pm
Arthur.Lorenzini (9/10/2008)
I found the table that is indicated in the objecid and it contains Text datatype. I know that this is a blob field and have read somewhere this could be causing it. Would a DBCC CheckAlloc (tablename) do me any good at this point?
It might, but it won't answer the question of is there any other corruption anywhere else in the database...
That error is specific to blobs, it can't occur with any other data type.
Would using NOLOCKS be a underlying cause for this?
It's possible, but I wouldn't think so.
The error is saying there's an inconsistency on the page. The page metadata says there's a slot 5, but when it looks at the page, there isn't. This isn't something that nolock's going to mess up, because even with nolock, there are still latches put in place to prevent one process from modifying the physical structure of the page while another process is reading.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 10, 2008 at 2:04 pm
Do you know if Microsoft has any KB on this issue. I just know that is what is going to be asked.
Warm Regards,
Arthur Lorenzini
Sioux Falls, SD
September 23, 2008 at 11:24 am
I have seen a similar error in the past when using NOLOCK on an active table with a blob column. The scenario is that someone starts a query that is basically
[font="Courier New"]SELECT * FROM MYLARGETABLEWITHBLOB (NOLOCK) WHERE blah='whatever'[/font]
During the time that the query is running, someone comes in and deletes one of the records that would be in the recordset that would be returned. I think that SQL Server makes 2 passes at the data, one to get the base data, and another to grab the blob data. I believe that when it goes to snag the blob data that the row has been removed, so it can't find it and pops an error.
Anyway, that is what is generally the case for me.
Hope that helps.
Larry
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply