Re: sugessiong regarding chunks

Not to worry. The Physical Log is allocated once when the engine starts up and is fixed size, it does not grow. If it reaches 75% full the engine forces a checkpoint and empties it. Similarly the set of logical logs is fixed (unless you have 9.30 or later and have enabled automatic logical log additions) and the set of logs is used round-robin. When the last one fills the first is reused and its 'uniqid' is updated assuming it has been backed up (or discarded to /dev/null). If you do have 9.30 and are using the new add-a-log feature this only happens if the next log to be used has not yet been backed up. Only then will the engine try to add another logical log and if it cannot find space on the same dbspace the other logs are in it will place it in another dbspace. For details on how this all works see the Administrator's Guide and Administrator's Reference. BTW, I hope this is not a production instance, dumping logical logs to /dev/null is a VERY BAD idea unless the data is purely for testing purposes. I would not even do it in a development instance on the chance I'd lose a brand new, undocumented, schema. Art S. Kagel ----- Original Message ----- From: Nagarjuna K.... <nagarjuna.kurra@gujaratgas.com> At: 2/21 5:24 > hi all, > > By observing the onstat -d output , it shows less than 2 % of lldbs and > phydbs are free.i Have set my LTAPEDEV to /dev/null > but still it shows the same . > > do i need to add extra chunks to lldbs and phydbs > Dbspaces > address number flags fchunk nchunks flags owner name > d2d04158 1 1001 1 1 N informix rootdbs > d2d056f8 2 1 2 1 N informix physdbs > d2d057b8 3 1 3 1 N informix logdbs > d2d05878 4 1 4 4 N informix dbs1 > d2d05938 5 1 5 3 N informix dbs2 > d2d059f8 6 1 6 6 N informix dbs3 > d2d05ab8 7 2001 7 1 N T informix tempdbs > 7 active, 2047 maximum > > Chunks > address chk/dbs offset size free bpages flags pathname > d2d04218 1 1 0 50000 47535 PO- /dev/ifmx/rootdbs > d2d048f8 2 2 0 50000 947 PO- /dev/ifmx/physdbs > d2d049d8 3 3 0 76000 947 PO- /dev/ifmx/lldbs > d2d04ab8 4 4 0 1048000 15222 PO- /dev/ifmx/dbs1 > d2d04b98 5 5 0 980000 178 PO- /dev/ifmx/dbs2 > d2d04c78 6 6 0 920000 127 PO- /dev/ifmx/dbs3 > d2d04d58 7 7 0 250000 249455 PO- /dev/ifmx/tempdbs > d2d04e38 8 4 0 350000 3670 PO- > /dev/ifmx/chunk_123 > d2d04f18 9 5 350000 350000 731 PO- > /dev/ifmx/chunk_123 > d2d04ff8 10 6 700000 340000 68 PO- > /dev/ifmx/chunk_123 > d2d050d8 11 6 0 275000 525 PO- /dev/ifmx/dbs3_c2 > d2d051b8 12 4 0 250000 52628 PO- > /dev/ifmx/chunk_234 > d2d05298 13 5 250000 500000 435984 PO- > /dev/ifmx/chunk_234 > d2d05378 14 6 750000 250000 44805 PO- > /dev/ifmx/chunk_234 > d2d05458 15 4 0 500000 499997 PO- > /dev/ifmx/dbs1_170103 > d2d05538 16 6 0 50000 49997 PO- > /dev/ifmx/dbs3_170103 > d2d05618 17 6 50000 450000 449997 PO- > /dev/ifmx/dbs3_170103 > 17 active, 2047 maximum > > with regards > > Nagarjuna.K