WARNING! Physical Log size 140000 is too small.

Dear Sir, i have the following Warning becoming from Primary: WARNING! Physical Log size 140000 is too small. Physical Log overflows may occur during peak activity. Recommended minimum Physical Log size is 160 times maximum concurrent user threads. and here is the output from the onstat -d: IBM Informix Dynamic Server Version 11.50.UC1 -- On-Line (Prim) -- Up 4 days 11:22:14 -- 385232 Kbytes Dbspaces address number flags fchunk nchunks pgsize flags owner name 4b1f17f8 1 0x40001 1 1 2048 N B informix rootdbs 4b2d2c70 2 0x40001 2 1 2048 N B informix hisdbs 4b2d2dd0 3 0x40001 3 1 2048 N B informix logdbs 4b2c0c30 4 0x40001 4 1 2048 N B informix physdbs 4b2c0d90 5 0x40001 5 1 2048 N B informix tempdbs 4b1f1b70 6 0x40011 6 1 8192 N BB informix blobdbs 4b1f1cd0 7 0x40001 7 1 2048 N B informix regindbs 7 active, 2047 maximum Note: For BLOB chunks, the number of free pages shown is out of date. Run 'onstat -d update' for current stats. Chunks address chunk/dbs offset size free bpages flags pathname 4b1f1958 1 1 5 100000 88541 PO-B /dev/sdb1 4b1f1e30 2 2 100010 4000000 2627301 PO-B /dev/sdb1 4bc1a018 3 3 4100015 500000 399947 PO-B /dev/sdb1 4bc1a1e8 4 4 4600020 250000 179947 PO-B /dev/sdb1 4bc1a3b8 5 5 4850025 250000 249697 PO-B /dev/sdb1 4bc1a588 6 6 5100030 1000000 ~250000 250000 POBB /dev/sdb1 4bc1a758 7 7 6100035 250000 247162 PO-B /dev/sdb1 7 active, 32766 maximum NOTE: The values in the "size" and "free" columns for DBspace chunks are displayed in terms of "pgsize" of the DBspace to which they belong. Expanded chunk capacity mode: always -- any help will be welcome Regards, Muthana AL-Temimi M.Sc. Informations- und Kommunikations-Systeme Technische Universitaet Hamburg Harburg -Rechenzentrum- Schwarzenbergstr. 95 (E) D-21073 Hamburg Tel.: +49.40.42878.2338 Fax.: +49.40.42793.5160 E-Mail: m.al@tu-harburg.de http://www.tu-harburg.de/rzt

That should not pose a problem unless you happen to crash your system during a physical log overflow situation. I asked questions around this in an advanced performance tuning class earlier this year and was told you cannot make it too large. If I were you, I would allocate a dbspace with a large enough chunk to hold twice the recommended minimum size and fill it up with plog.