HELP - SQL 6.5 - Error : 625 - Could not retrieve row from logical page

Last Post 22 Dec 2004 01:46 PM by BobBarker. 1 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
wkenny
New Member
New Member

--
22 Dec 2004 09:02 AM
Hi all, here is my error message;

2004/12/22 13:54:42.64 spid107 Retrying row fetch: rowoffset entry 0 out of range (pg 0x120c9e1, obj 0x6be4cfe8, db 6, stat 1004/0)
2004/12/22 13:54:42.64 spid107
spid 107, Getrow: rowoffset entry 14(0) out of range (pg 0x120c9e1, obj 0x6be4cfe8, db 6, stat 100c/0)
2004/12/22 13:54:42.64 spid107 Error : 625, Severity: 20, State: 1
2004/12/22 13:54:42.64 spid107 Could not retrieve row from logical page 18926049 via RID because the entry in the offset table (= 0) for that RID (= 14) is less than or equal to 0.

Here is the output from DBCC Page;

PAGE:
Page not found in cache - read from disk.

BUFFER:
Buffer header for buffer 0x599df2a4
page=0x10270000 bdnew=0x0 bdold=0x0 bhash=0x0 bnew=0x0
bold=0x0 bvirtpg=89778768 bdbid=6 bpinproc=0 bkeep=0 bspid=0
bstat=0x0000 bpageno=0

PAGE HEADER:
Page header for page 0x10270000
pageno=19204688 nextpg=19204730 prevpg=18926049 objid=1810157544
timestamp=0005 534fe10c
nextrno=19 level=0 indid=0 freeoff=1938 minlen=48
page status bits: 0x100,0x8,0x4,0x1

DATA:
Offset 32 -
10270020: 11000c0b 747b073e db575e01 43520040 ....t{.>.W^.CR.@
10270030: b75d81ec 53c8c500 00000553 4fdc637b .]..S......SO.c{
10270040: 14ae47e1 7af03f59 01000000 01000000 ..G.z.?Y........
10270050: 6f00c595 ae0114ae 47e17a14 f03f7b14 o.......G.z..?{.
10270060: ae47e17a f03f312e 30303520 2d20312e .G.z.?1.005 - 1.
10270070: 30333031 2e303330 dd55b603 125c5858 0301.030.U...\XX
10270080: 58585858 5853463e 36363636 363632 XXXXXSF>6666662

Offset 143 -
1027008f: 11010c0b 747b073f db575e01 43520041 ....t{.?.W^.CR.A
1027009f: b75d81ed 53c8c500 00000553 4fdc9900 .]..S......SO...
102700af: 00000000 00000059 01000000 01000000 .......Y........
102700bf: 5d00c595 ae014e65 67617469 76654e45 ].....NegativeNE
102700cf: 47415449 5645dd55 b603124a 46464646 GATIVE.U...JFFFF
102700df: 46463e3e 36363636 36363636 32 FF>>666666662

Offset 236 -
102700ec: 11020c0b 747b0740 db575e01 43520042 ....t{.@.W^.CR.B
102700fc: b75d81ee 53c8c500 00000553 4fdccc00 .]..S......SO...
1027010c: 00000000 00144059 01000000 01000000 ......@Y........
1027011c: 6900c595 ae010000 00000000 14400000 i............@..
1027012c: 00000000 2040352e 30202d20 382e3035 .... @5.0 - 8.05
1027013c: 2e30dd55 b6031256 52525252 5252524f .0.U...VRRRRRRRO
1027014c: 463e3636 36363636 32 F>6666662

Offset 341 -
10270155: 11030c0b 747b0742 db575e01 43520044 ....t{.B.W^.CR.D
10270165: b75d81f0 53c8c500 00000553 4fdcff00 .]..S......SO...
10270175: 00000000 00000059 01000000 01000000 .......Y........
10270185: 5d00c595 ae014e65 67617469 76654e45 ].....NegativeNE
10270195: 47415449 5645dd55 b603124a 46464646 GATIVE.U...JFFFF
102701a5: 46463e3e 36363636 36363636 32 FF>>666666662

Offset 434 -
102701b2: 11040c0b 747b0743 db575e01 43520045 ....t{.C.W^.CR.E
102701c2: b75d81f1 53c8c500 00000553 4fdd3200 .]..S......SO.2.
102701d2: 00000000 00000059 01000000 01000000 .......Y........
102701e2: 5d00c595 ae014e65 67617469 76654e45 ].....NegativeNE
102701f2: 47415449 5645dd55 b603124a 46464646 GATIVE.U...JFFFF
10270202: 46463e3e 36363636 36363636 32 FF>>666666662

Offset 527 -
1027020f: 11050c0b 747b0744 db575e01 43520046 ....t{.D.W^.CR.F
1027021f: b75d81f2 53c8c500 00000553 4fddc700 .]..S......SO...
1027022f: 00000000 c05b4059 01000000 1d000000 .....[@Y........
1027023f: 7200c595 ae010000 00000080 4b400000 r...........K@..
1027024f: 00000000 00000000 00000000 00004e65 ..............Ne
1027025f: 67617469 76653e3d 313131dd 55b60312 gative>=111.U...
1027026f: 5f5b5b5b 5b5b5856 564e463e 36363636 _[[[[[XVVNF>6666
1027027f: 3632 62
BobBarker
New Member
New Member

--
22 Dec 2004 01:46 PM
Most likely you have a corrupt data file. I'm very sorry but you may very well be screwed. I hope you have a recent backup.

You may be able to repair the file using some DBCC commands, but I'm not familiar with SQL 6.5. You should post your question to the SQL Server 6.5 forum.

BB
You are not authorized to post a reply.

Acceptable Use Policy