RE: general informix wierdness

Rich, I haven't come across your particular problem. But, I did have similar results once when I miscalculated the offset of a dbspace. In my case, I had two dbspaces which resided on the same raw device. Due to bad addition on my part, I had defined the spaces to overlap. Thus, an update of one space wrote garbage into the second space. As it turned out, we only rarely used the second space and did not discover the problem for quite a while. When we did, though, we had a large number of oncheck errors similar to yours. I hope you aren't in this situation! --Craig (craig@chemistry.utah.edu) > >[...deleted text...] >Now we try a 'tbcheck -cD' on the offending database and it >returns a whole host of errors, i.e.: > > TBLSpace data check for pedb:blah.tl_ey_cg > > BAD PAGE 109480: pg_stamp 1268966 != PG_STAMP2 100008446 > BAD PAGE 0: pg_addr 0 != bp->bf_pagenum 109481 > >Informix tell us that this could be a disk error, low level >problem with the surface. Of course this is on a raw >partition so we can't check it. They suggest using a cooked >file - but this is really no good to us as we USE RAW PARTITIONS. >[...deleted text...] >