RE: Chunk reported full, while it shouldn't ...

It's funny but a few weeks ago I saw on this newsgroup a comment to the effect that training courses tell you about setting extent sizes correctly, etc but that it isn't really necessary. And today I have been trying to cope with a database that ran out of space (one table has 194 extents!) and now this error. I think we should all pat lots of attention to the need for space planning on IDS systems. I wrote the original user instructions on this back in 1988 (Turbo in those days) and many of them still hold. But the important thing is that all DBAs should plan their disk space, set up extent sizes, and montior growth. Hopefully if they follow that model they won't encounter problems like this. I refer you to the IDS Admin reference and guide for the detailed information. Regards Malcolm -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On Behalf Of Petzi Sent: 31 March 2004 06:30 To: informix-list@iiug.org Subject: Chunk reported full, while it shouldn't ... Folks, Maybe it's a FAQ, but then I haven't found it ... One a DB, I get error messages that the database is full. Looking at onspaces, I notice that only 78 blocks are free (out of 950000). SO what I did, for each database, I took size*nrows for each table in each db, and I noticed that it represents only 210 MB, while the full chunk is nearly 2GB. So we have nearly 90% overhead here, which I consider a bit too much :) This DB has a lot of activity (one table for instance contains more than 6 millions entries that are updated every 24 hours). Could it be some stupid stuff like a transaction log that is filling the database (DB has been up and running for 4 months) ? If yes, how can I clear it without touching the data ? Cheers, Petzi sending to informix-list