Our process is uploading data to a table. Expected data is around 50 GB. First extent was set to 40GB and next extent to 4 GB. However the process stops after uploading around 33 GB of data. The error message is as follows:
271: Could not insert new row into the table.
136: ISAM error: no more extents
This error message implies that the number of extents allocated for this table has been exhausted and no more extents can be allocated to this table. Our analysis shows that overall 220 extents can be allocated to this table and 17 extents have been allocated to this table till the error message. The dbspace has chunks of size 2GB. And the initial extent allocated is of size 2GB and next extent also is of size 2GB irrespective of the limits we have set earlier(40GB and 4GB). This is understandable as the max size of an extent is limited by the chunk size. However, what baffles us is the no more extents being allocated after 17 eventhough there are free chunks in the dbspace. Any pointers on what could be happening?

We are using Informix 7.31 on HP-UX 11i.

Hi,

Have you checked (using oncheck -pt db:table ) thet the table really has just 17 extents, or is it only a guess? If the dbspace you are loading data into had tables before it's quite possible that the free space within could be very fragmented.

Hope it helps.

Hi,

Have you checked (using oncheck -pt db:table ) thet the table really has just 17 extents, or is it only a guess? If the dbspace you are loading data into had tables before it's quite possible that the free space within could be very fragmented.

Hope it helps.

I have found the problem. The problem is that a single partition (ie table, index, table fragment, index fragment) cannot exceed 16,777,216 (2^24) pages on most platforms, including HPUX, IDS's page size is 2K so the maximum partition size is 32GB. So I had to fragment the table to make it accept more than 32 GB data.