Re: Sysmaster Corruption

Bryan Hughes wrote: > > Lori, > > We have two 3.5 TB Informix ODS 7.24 UC1 databases on two SUN Enterprise > 6000's with 12 CPUs, and 8 GB of memory (soon to grow up into a pair of > E10000's) running Solaris 2.5.1 and have not experience any problems with > corruption of the sysmaster. One system has been up for over 200 days now. > I have heard rumors that Informix 7.24 is not stable with Solaris 2.6 (but > this is only hearsay). > > I will let you know of a known bug we discovered rather painfully (don't > have the case ID here at home) with 7.24 on Solaris with tables that have a > lots of fragments. The bug is in how the optimizer calculates maximum > memory needed by each scan thread. The optimizer uses a signed int, instead > of an unsigned, when calculating the amount of memory needed for each > thread. If your max memory is defined as > 1.9 GB then the optimizer > calculates negative memory causing the engine to sequentually do a table > scan. For us, each table has ~2,000,000,000 rows in 260 fragments and a > sequential table scan probably wouldn't finish this year. > > Informix wrote: > > > I have been seeing some messages going around regarding sysmaster > > corruption with 7.24.UC3 on a HP platform. > > > > We are considering upgrading to 7.23.UC4 on Solaris 2.x. Has anyone > > experienced any problems with sysmaster corruption on the Sun platform, > > 2.4, 2.5, 2.5.1 or 2.6 and this version of Informix. There was a serious problem running IDS under Solaris 2.6 which I understand Informix and Sun together fixed very recently. you should contact Informix about what IDS subversion upgrade or OS patches you need so that it does not bite you later. Art S. Kagel