Chunk really full??? Puzzling . . .

The following is the output of an `onstat -d` for a particular chunk - calldata_dbs_4_cnd_1. de04c18 13 13 0 400000 0 PO- /chunks/calldata_dbs_4_cnk_1 ^ zero free space Notice that the amount of free space is 0. I have a table defined which fragments inserts for the month of August to this chunk: fragment by expression (MONTH (calldate ) IN (1 ,5 ,9 )) in calldata_dbs_1 , (MONTH (calldate ) IN (2 ,6 ,10 )) in calldata_dbs_2 , (MONTH (calldate ) IN (3 ,7 ,11 )) in calldata_dbs_3 , (MONTH (calldate ) IN (4 ,8 ,12 )) in calldata_dbs_4 Dbspace "calldata_dbs_4" and chunk "calldata_dbs_4_cnk_1" are equivalent, and there are no other chunks allocated to dbspace "calldata_dbs_4". Although the current status of the calldata_dbs_4_cnk_1, as reported by `onstat -d` is that it has no free space, we are still able to insert rows into the table for the month of August. How is this possble? The only thing that I can think of is that at some point all of the chunk was allocated, then some rows were deleted. But the extents are still allocated for the table and not shown as being free even though rows have been deleted from the table. If this is the case, how does one find out the "real" free space in a chunk? Thanks for any clarification on this. -- * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ADDRESS ALTERED TO FOIL SPAMMERS: Remove "*NO-SPAM*" to reply. Cosmo Lee Multi-User Computer Systems Brooklyn, NY "JUST SAY 'NO' TO SPAM" * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *