Re: Help! Corrupted sysprocbody (7.20.UC2)
Posted in 1996
In article <321490ED.1259@csc.com>, "Chao Y. Din" <cdin@csc.com> writes
>We just had a hard disk failure on a Solaris 2.5.1 NFS file system. Somehow it
>caused "out of swap space" problem. At
>the same time we got sysprocbody error. They may be coincidence. Anyway, the
>online log messages are as follows.
>
What is the contents of the /tmp/af.... files.
>==========
>online.log
>==========
>
>13:58:41 Assert Failed: Page Check Error in btsearch:bad btree node
>13:58:41 Who: Session(66, informix@input2.mmsb.usmc.mil, 7770, 247051424)
> Thread(93, sqlexec, eb7cc08, 1)
>13:58:41 Results: Possible inconsistencies in index
>'input:"informix".sysprocbody-Key#1'
>13:58:41 Action: Run 'oncheck -cI 2097232'
>13:58:41 See Also: /tmp/af.5db5d4>
>When we tried oncheck with -cI, we got the following messages.
>
>==========
>online.log
>==========
>14:00:14 Assert Failed: Page Check Error in allocrow:bad bitmap page
>14:00:14 Who: Session(72, informix@input2.mmsb.usmc.mil, 7845, 247051424)
> Thread(99, sqlexec, eb7cc08, 1)
>14:00:14 Results: Possible inconsistencies in 'input:"informix".sysprocbody'
>14:00:14 Action: Run 'oncheck -cD 2097232'
>14:00:14 See Also: /tmp/af.63b72d, shmem.63b72d.0>
>Then we tried -cD option. Here is the response on the screen.
>
>==========
>screen
>==========
>oncheck -cD 2097232>TBLspace data check for input:informix.sysprocbody
>BAD PAGE 2000bd: pg_addr 18 != bp->bf_pagenum 2000bd
>Error reading from network
> Abnormal end !!!
>
>When we check the online.log, OnLine was shut down.
>
>==========
>online.log
>==========
>23:05:48 Assert Failed: Internal Error - Segmentation Violation
>23:05:48 Who: Session(78, informix@input2.mmsb.usmc.mil, 8731, 247051132)
> Thread(105, oncheck, eb7c7d0, 1)
>23:05:48 Results: OnLine must abort
>23:05:48 Action: Reinitialize shared memory
>23:05:48 See Also: /tmp/af.69370b, shmem.69370b.0
>23:12:09 rsinit.c, line 9495, thread 105, proc id 1684, Segmentation Violation.
>23:12:09 PANIC: Attempting to bring system down>
>We did call Informix Tech Supp. They don't know how to handle this case yet.
>Any suggestion?
>
>Chao
--
David Williams