136 Isam Error No More Extents
FacebookdeveloperWorks on TwitterdeveloperWorks on LinkedIndeveloperWorks on YouTubedeveloperWorks on Google+
check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 4 of 4 Thread: "No more extents" issue Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 12-30-04,00:39 #1 daljit_reck View Profile View Forum Posts Registered User Join Date Dec 2004 Location India Posts 4 Unanswered: "No more extents" issue Our process is uploading data to a table. Expected data is around 50 GB. https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014464002&ps=50 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 http://www.dbforums.com/showthread.php?1082881-quot-No-more-extents-quot-issue 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. Reply With Quote 12-31-04,03:22 #2 matute View Profile View Forum Posts Registered User Join Date Jun 2004 Location Madrid, Spain Posts 47 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. José Luis Matute. Regards from Spain. Reply With Quote 12-31-04,04:12 #3 matute View Profile View Forum Posts Registered User Join Date Jun 2004 Location Madrid, Spain Posts 47 Hi, Have you checked (using oncheck -pt db:table ) thet the table really has just 17 extents, or is it only a
from GoogleSign inHidden fieldsSearch for groups or messages
high enough to ensure a smooth operation of the instance. However, when using the old simple large objects TEXT and BYTE in Informix, this is not the case. Unlike the new smart large objects, these blobs cannot be stored in a smart blobspace and still have to be stored in the old blobspace.The problem is that blobs (data types TEXT and BYTE) stored in old blobspaces are not logged in the logical log. This is a great disadvantage if you want to use a high-availability solution such as HDR, RSS or SDS. Since all of these solutions work by exchanging logical log information, objects that do not appear in the logical log will not be replicated.The only way to log simple large objects in the logical log is to forego blobspaces and to store the blobs in the tablespace.This is where the Informix table limits come into play. Informix allows rows up to 32KB wide. In our case, this limit is not problematic since rows including simple-large-object data only contain a 56-byte simple-large-object descriptor. What is problematic in our case is the limit that the maximum number of data pages per fragment is 16,777,215. The question now is whether the blob pages needed for a simple large object count towards this number.The Informix documentation says nothing about this. In order to find out whether blob pages count as data pages, we have created a 100GB-sized chunk. As platform, we used Windows with a 4k page size. In the table with two text fields, we have inserted 300KB rows in a loop. The question was – how many rows can we insert? JavaScript is currently disabled.Please enable it for a better experience of Jumi. create table "informix".testtable ( f01 char(64) not null , f02 char(4), f03 char(30), f04 char(2), f05 char(1), f06 char(5), f07 char(5), f08 char(1), f09 text , f10 text , f11 char(8), f12 date, f13 date ); Scheme of Our Test Table If the blob pages do count as data pages, we should be able to reach the page limit. The number of rows needed for this can be calculated as follows: 300kByte data per row / 4kByte page size = 75 pages per row Limit for p