Re: Strange Lockups on IDS 7.31.UD8

The "I/O bad request chunk 4095" message could be due to a corrupted index pointing to a nonexistent chunk. In any case, if oncheck -cDI confirms a bad index, drop and recreate the index. "Anthony" <anthony@zoraptera.com> wrote in message news:1124228243.115539.65000@g47g2000cwa.googlegroups.com... > The machine is the same one that we've been using for about ... 2 > years. We've been running IDS on it the whole time. > > However, that doesn't mean those values haven't been wrong the whole > time. The values for the parameters you asked about are: > > MULTIPROCESSOR 1 # 0 for single-processor, 1 for> multi-processor > NUMCPUVPS 2 # Number of user (cpu) vps > SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps> to one > > I also noticed the index errors from last Thursday look more like: > > 09:44:58 Assert Failed: ptmap > 09:44:58 IBM Informix Dynamic Server Version 7.31.UD8 > 09:44:58 Who: Session(19, informix@corp.inventconnect.com, -1,> 2146684976) > Thread(154, sqlexec, 7ff2b3c0, 1) > File: rspartn.c Line: 1867 > 09:44:58 Results: Could not complete operation on> 'development:"root".invention' > 09:44:58 Action: Run 'oncheck -cDI development:"root".invention' > 09:45:02 See Also: /db0/tmp/af.482edd9, shmem.482edd9.0 > 09:46:35 I/O bad request chunk 4095, pagenum 1048575, pagecnt 1 > 09:46:39 listener-thread: err = -25587: oserr = 0: errstr = : Network> receive failed. > > However, running an oncheck -cDI doesn't show any problems (other than > the bad index). I would expect to see something about a bad chunk. > Isn't that what the above error states? > > --Anthony >