Re: Upgrade from Informix 5 to 7.23

That's too bad! I am going to upgrade from 5.07 to 7.22 next week. My testing on experimental machine for a couple of weeks was fine except that once I got very similar crash for unknown reason. I called Informix, they said it might be incompatible OS (I was testing on Solaris 2.5 while the product is for 2.5.1 where I have the production system). Of course, I do not have a heavy load on my testing macine, and your experience has really scared me. Could you, pls, reply when you find what cases the problem? Regarding to the backup - I tested ontape and was able to make a backup and restore. Thanks ======================================================================= Boris Niyazov Ph: 212-854-4094 IT Department Fax: 212-316-2623 Columbia Law School Email: ban5@columbia.edu Jason Bramble wrote: > > Sorry folks for posting the same message, but I did not include all the > information on the first one... > > We have just upgraded our database from Informix 5 to 7.23, running on > Solaris 2.51. The size of the database is 48Gb. Since our upgrade this > past weekend, the machine hasn't been stable for more than an hour. > Informix keeps aborting from an "Assert Error". We currently have an > Informix Tech on-site, as well as the vendor (Boris) who supplied us the > application we are using. Everyone is scratching their heads on this here. > Any help would be really appriciated! Here is the message from the online > log: > > 09:24:00 Assert Failed: Internal Error - Segmentation Violation > > 09:24:00 Who: Session(3695, boris@trend, 19419, 637937636)> > Thread(3776, sqlexec, 28618f58, 5) > > 09:24:00 Results: OnLine must abort > > 09:24:00 Action: Reinitialize shared memory > > 09:24:00 See Also: /tmp/af.ec08370 > > 09:24:00 rsinit.c, line 9947, thread 3776, proc id 323, Segmentation > Violation.> > > 09:24:00 PANIC: Attempting to bring system down> > The stack trace file for this assert error reads: > > 09:24:00 > 09:24:00 Assert Failed: Internal Error - Segmentation Violation > 09:24:00 Who: Session(3695, boris@trend, 19419, 637937636) > Thread(3776, sqlexec, 28618f58, 5) > 09:24:00 Results: OnLine must abort > 09:24:00 Action: Reinitialize shared memory > 09:24:00 See Also: /tmp/af.ec08370 > 09:24:00 Stack for thread: 3776 sqlexec> > base: 0x2933a018 > len: 33280 > pc: 0x003a5d88 > tos: 0x293411b8 > > 0x003a56dc mt_affail (0xec08370, 0x568e54, 0x28618f58, 0x260627e4, > 0x260627e4, 0x2681e438) > 0x00297e14 rsam_affail (0x26177eb0, 0x2681e438, 0x568e54, 0x28618f58, > 0x260627e4, 0x0) > 0x0007c058 hang_thread (0x506998, 0x2400, 0xb, 0x507208, 0x0, 0x0) > 0xef5b8c7c ***unknown*** (0xb, 0x0, 0x29341a88, 0x15, 0x0, 0x0) > 0x0019d788 gettab (0x264e4160, 0x4d04e054, 0x1, 0x264e4030, > 0x28962c50, 0x29341e60) > 0x001b2c40 tlgetddtab (0x264e4620, 0x264e4030, 0x29341f44, 0x264e4418, > 0x264e4820, 0x28138e17) > 0x001b3514 spgettab (0x264e4620, 0x264e4030, 0x29341f44, 0x15, > 0x264e4820, 0x264e4b19) > 0x001b3404 tlp2tnode (0x264e4620, 0x264e47f0, 0x0, 0x264e4030, > 0x264e4820, 0x264e47d1) > 0x001af300 sel2cb (0x264e4750, 0x264e4030, 0x0, 0x264e4820, 0x0, > 0x4650) > 0x001aeccc qblk2cb (0x264e4790, 0x264e4030, 0x0, 0x184dd8, 0x1, > 0x50ecce) > 0x001a8950 p_sp2cb (0x0, 0x264e4030, 0x0, 0x646, 0x332, 0x332) > 0x0016a768 parsecmd (0x1, 0x0, 0x0, 0x5724b4, 0x37, 0x0) > 0x0016a164 sqcmd (0x1, 0x0, 0xe230, 0xa004800, 0x8, 0x40) > 0x0017eee8 sqmain (0xe000, 0x1, 0x5724b4, 0x572400, 0x5748dc, 0x1) > 0x0038b32c startup (0x260a8018, 0x29d07168, 0x1, 0x28c41168, > 0x5748dc, 0xc) > 0x003868fc mt_wait (0x0, 0x0, 0x0, 0x0, 0x0, 0x0) > 0x00000000 ***unknown*** > > 09:24:00 > ------------------ End of assertion failure 0 ----------------- > > Also, I had one more question... I have heard a rumor that Informix 7.x > can not backup on a Solaris 2.51 machine. Does anyone know if this is > valid or not? Thanx again! --