VP died - Should the server continue

We had an AF on one of the VPs in our production server. 09:09:37 Assert Failed: Memory free block header corruption detected in mt_shm_malloc_segid 3 09:09:37 Informix Dynamic Server 2000 Version 9.21.UC4XE 09:09:37 Who: Session(123545, gui@whflxsnp03, -1, -2127782116) Thread(154189, sqlexec, 666bd058, 3) File: mtshpool.c Line: 3296 09:09:37 Results: Pool repaired 09:09:37 Action: Please notify Informix Technical Support. 09:09:37 stack trace for pid 29214 written to /tmp/af.5e358831 09:09:37 See Also: /tmp/af.5e358831 But the engine is up and running. Is it safe to continue as if nothing has happened? TIA. Ravi

Ravi, If nothing else went wrong continuing is probably save (but I wouldn't bet on it). I would recommend that you talk to Informix Technical Support to get this analyzed. (send them the /tmp/af.5e358831 which should contain a stack trace). Memory corruption can be a serious problem and could have all sort of bad consequences if it happens again. Your corruption was in a list of free memory blocks belonging to some memory pool and could be repaired. This usually happens if some thread in the server continues using memory after it has freed it. If this memory is reallocated for some other purpose and used by the old owner at the same time you may run into major trouble. Michael rkusenet wrote: > We had an AF on one of the VPs in our production server. > > 09:09:37 Assert Failed: Memory free block header corruption detected in > mt_shm_malloc_segid 3 > 09:09:37 Informix Dynamic Server 2000 Version 9.21.UC4XE > 09:09:37 Who: Session(123545, gui@whflxsnp03, -1, -2127782116) > Thread(154189, sqlexec, 666bd058, 3) > File: mtshpool.c Line: 3296 > 09:09:37 Results: Pool repaired > 09:09:37 Action: Please notify Informix Technical Support. > 09:09:37 stack trace for pid 29214 written to /tmp/af.5e358831 > 09:09:37 See Also: /tmp/af.5e358831 > > But the engine is up and running. > > Is it safe to continue as if nothing has happened? > > TIA. > > Ravi > > >