explanation of "out of space"

Would someone please explain to me (or point me to the explanation) of maxing out dbspace? About 2 months ago, I created a large dbspace to add room to a particular database (workgroup server, NT). Yesterday I deleted about 3 million records from a 5 million record table and updated statistics. This morning, when trying to add a record, I am told the record can't be saved because I am out of disk space. It is NOT physical hard drive space. Theoretically I should have room for about 3 million records in that same table, but obviously it doesn't work this way. Some clarification would be appreciated. MJ

In theory, you should be able to insert rows into the table. However, 1. With due respect, could you confirm that the 3 million rows actually got deleted - you could have run into a long transaction that rolled back the delete. 2. What is the Informix & ISAM error that you are getting when attempting to INSERT? 3. Try rebuilding your indexes. The simplest way is to DISABLE them (SET INDEXES, CONSTRAINTS FOR <table> DISABLED;), then ENABLE. It is possible that the new row needs to be put into a new index page, space for which does not exist. Rudy "M.J. Holley" wrote: > Would someone please explain to me (or point me to the explanation) of > maxing out dbspace? About 2 months ago, I created a large dbspace to add > room to a particular database (workgroup server, NT). Yesterday I deleted > about 3 million records from a 5 million record table and updated > statistics. This morning, when trying to add a record, I am told the record > can't be saved because I am out of disk space. It is NOT physical hard > drive space. Theoretically I should have room for about 3 million records in > that same table, but obviously it doesn't work this way. Some clarification > would be appreciated. > > MJ