RE: [Exist-open] db corruption in 1.0b2 1107 after heavy processing

[Robin S. <Rob...@as...>]

I believe these are very similar if not the same problems we have with =
our exist installation (1.0b1).
=20
Robin
=20
Robin Tori Schroeder (formerly Schoeninger)=20
International Institute for Sustainability=20
P.O. Box 873211=20
Arizona State University=20
Tempe, Arizona 85287-3211=20
Phone: (480) 727-7290=20


-----Original Message-----
From: exi...@li... =
[mailto:exi...@li...]On Behalf Of Kaj ten =
Voorde (Mendix)
Sent: Friday, December 17, 2004 2:53 AM
To: exi...@li...
Subject: [Exist-open] db corruption in 1.0b2 1107 after heavy processing


hi,
=20
I'm using the 1.0b2 1107 release and it didn't give me any corruption =
until now. I have a script which collects stock mutations and calculates =
new stock amount on a lot of products. This means that a lot of =
xupdate:update modifications are done in short time. It gives me the =
following error:
=20
17:42:25,484 DEBUG [NodeImpl] Unknown node type: -1
17:42:25,500 WARN  [NodeIterator] illegal node on page 4009; tid =3D 98; =
next =3D -1; prev =3D 4052; offset =3D 1733; len =3D 1763
17:42:25,500 DEBUG [NodeIterator] Page 4009: 0[0:38] 1[42:7] 2[53:2] =
3[59:7] 4[70:33] 5[107:6] 6[117:2] 7[123:7] 8[134:33] 9[171:6] 10[181:2] =
11[187:7] 12[198:37] 13[239:6] 14[249:7] 15[260:33] 16[297:7] 17[308:2] =
18[314:7] 19[325:38] 20[367:7] 21[378:2] 22[384:7] 23[395:45] 24[444:7] =
25[455:7] 26[466:22] 27[492:7] 28[503:2] 29[509:2] 30[515:2] 31[521:7] =
32[532:45] 33[581:7] 34[592:7] 35[603:22] 36[629:7] 37[640:2] 38[646:2] =
39[652:2] 40[658:7] 41[669:33] 42[706:7] 43[717:2] 44[723:7] 45[734:36] =
46[774:6] 47[784:5] 48[793:7] 49[804:36] 50[844:7] 51[855:5] 52[864:7] =
53[875:45] 54[924:6] 55[934:6] 56[944:7] 57[955:26] 58[985:7] 59[996:23] =
60[1023:26] 61[1053:3] 62[1060:7] 63[1071:36] 64[1111:6] 65[1121:6] =
66[1131:2] 67[1137:7] 68[1148:37] 69[1189:7] 70[1200:6] 71[1210:5] =
72[1219:7] 73[1230:45] 74[1279:6] 75[1289:6] 76[1299:7] 77[1310:28] =
78[1342:7] 79[1353:24] 80[1381:28] 81[1413:3] 82[1420:7] 83[1431:37] =
84[1472:7] 85[1483:7] 86[1494:45] 87[1543:7] 88[1554:7] 89[1565:22] =
90[1591:7] 91[1602:25] 92[1631:22] 93[1657:3] 94[1664:7] 95[1675:33] =
96[1712:7] 97[1723:2] 98[1729:30] ; records in page: 99; nextTID: 98
17:42:25,515 DEBUG [NodeIterator] Contents of page 4009: ......
=20
I was able to restore the db from a hourly backup and i re-run the same =
script. It gives me exactly the same error on the same place. Even when =
i export and import the db it gives me this error. I was able to track =
down which objects are on the corrupted page. I checked them in the db =
before running the script, but they looked fine.
=20
I hope that this issue will be dealed with in forthcoming releases. But =
is there i way i can avoid this error for now?
=20
grtz,
=20
Kaj ten Voorde