Re: CLEANERS

hanna_shaw@my-deja.com schrieb: > > Hi, > > I only increased 'CLEANERS' from 64 to 128 and restarted the informix > server. I got the following warning message in log file: > > 00:42:53 WARNING! Physical Log size 0 is too small.> Physical Log overflows may occur during peak activity. > Recommended minimum Physical Log size is 20 times maximum > concurrent user threads. > > 00:42:54 WARNING! Logical log layout may cause Dynamic Server to get> into > a locked state. Recommended smallest logical log size > is 2 times maximum concurrent user threads. > > Is it serious message? What should I do? Change CLEANERS back to 64? > Before I changed CLEANERS, I never had such message. > You don't have to worry about this. It is a known bug. You can leave your settings. To avoid this meessage you can decrease LRUS an CLEANERS to 127 both. Going back to 64 is no good idea, because there is another bug with setting LRUS to a multiple of 2, for example 32 or 64. conclusion: decrease values to 127. Regards Frank

Frank Langelage wrote: > > hanna_shaw@my-deja.com schrieb: > > > > Hi, > > > > I only increased 'CLEANERS' from 64 to 128 and restarted the informix > > server. I got the following warning message in log file: > > > > 00:42:53 WARNING! Physical Log size 0 is too small.> > Physical Log overflows may occur during peak activity. > > Recommended minimum Physical Log size is 20 times maximum > > concurrent user threads. > > > > 00:42:54 WARNING! Logical log layout may cause Dynamic Server to get> > into > > a locked state. Recommended smallest logical log size > > is 2 times maximum concurrent user threads. > > > > Is it serious message? What should I do? Change CLEANERS back to 64? > > Before I changed CLEANERS, I never had such message. > > > > You don't have to worry about this. It is a known bug. You can leave > your settings. In case Frank is not clear enough, the bug above is annoying but harmless. > To avoid this meessage you can decrease LRUS an CLEANERS to 127 both. > Going back to 64 is no good idea, because there is another bug with > setting LRUS to a multiple of 2, for example 32 or 64. Not all multiples of 2, 32 is actually quite a good value in general. The only confirmed problem values are 64 & 96. Art S. Kagel