Informix Error No More Extents
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. 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. 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 guess? If the dbspace you are
to 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 12 of 12 Thread: Error: 136 No more extents 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 03-18-02,23:50 #1 TblXtnt View Profile View Forum Posts Registered User Join Date Mar 2002 Posts 5 Unanswered: Error: 136 No more extents Hi all, I must be overlooking something, I am running Informix730UC5 on solaris 7, I http://www.dbforums.com/showthread.php?1082881-quot-No-more-extents-quot-issue have a table that is around 16.77 million pages (300Million Rows) The row size is 62 bytes and is 15 columns no varchars mostly integers and a char(1) field, which is 17 extents. each extent around 999880 pages. There are 4 indexes they are each one integer column. By all my reckoning I should be able to support 221 extents based on the prevailing knowledge of the calculations of maximum extents ( as confusing as it is, http://www.dbforums.com/showthread.php?325626-Error-136-No-more-extents but the two formulae that I have found each yield similar values ). Can anyone advise me as to where I have mis-calculated or give me a clue as to where I have gone wrong in planning this table. Thanks in advance. Confused Reply With Quote 03-19-02,17:38 #2 rnealejr View Profile View Forum Posts Registered User Join Date Feb 2002 Posts 2,232 Since you are only using 17 extents I would check the free space on your chunks. How big are your chunks/extents ??? Reply With Quote 03-19-02,18:08 #3 TblXtnt View Profile View Forum Posts Registered User Join Date Mar 2002 Posts 5 Originally posted by rnealejr Since you are only using 17 extents I would check the free space on your chunks. How big are your chunks/extents ??? I have 40 dbspaces each 2Gb, naturally enough 30 are full, 5 are at around 50% and 5 are completely empty so I have approximately 13Gb free in the instance. There is sufficient space for the creation of the extent and as such the error must be ( as far as I can ascertain ) related to the number of extents. I greatly appreciate any directions that can be suggested. Thanks Reply With Quote 03-21-02,09:14 #4 rnealejr View Profile View Forum Posts Registered User Join Date Feb 2002 Posts 2,232 What are your extent sizes ? Reply With Quote 03-21-02,12:23 #5 townscr
Management Business Intelligence & DW Solutions Jaspersoft Microsoft: SSAS, SSRS, SSIS Netezza View All CRM Integration & Customization Salesforce http://www.xtivia.com/informix-error-136-no-extents/ Infor CRM SugarCRM Microsoft Dynamics Database Support & Management Remote DBA Managed Services Database Professional Services IT Managed Services Database http://www.baanboard.com/baanboard/showthread.php?t=14350 Software Licensing Supported Database Platforms SOA Consulting Technology Transformation Service Architectural Services Event Enterprise & Events Processing Implementation Services Managed Services Digital Experience Solutions Liferay informix error DXP Consulting Hippo CMS Consulting Jahia DXM Consulting View a Free Liferay DXP Demo Blog Company Customers & Partners Customers Success Stories Industries Partners Insights Webinars Innovations About Us Awards & Recognition Leadership Team Vision Events, News & PR XTIVIA Careers Contact Us Today! Informix error -136: informix error no “no more extents” December 20, 2012 Barrie Shaw Databases Informix software has a hard limit of 16,777,134 for the number of data pages that can be used in a single table partition. This is true for all versions of Informix software from 7.31 to 11.70. Unfortunately, if you hit this limit, the message that is returned is a misleading “no more extents” error. You can run “oncheck –pt dbname:tablename” to find out if the problem is the number of extents or pages. If the number of used pages is 16,777,215, then you have maxed out on pages. In order to resolve this problem, you can delete data out of the table or fragment the table into multiple partitions. Of course, the time to think about this is before you reach 16.7 million pages, as fragmenting such a large table could mean significant down time for a critical application. The number
password Frontpage Sponsor Main Frontpage Forum Jobs NewsStories RSS NewsfeedsCategoriesERP Geek Industry & Technology Opinion Security Sources Calendar Polls Shop Web Links Baanboard at LinkedIn Reference Content BaanERP Tutorial Programmer's Manual Thread Tools Display Modes #1 30th January 2004, 19:35 minos1 Newbie Join Date: Jan 2004 Posts: 1 Baan: B40b2 - DB: informix - OS: Unix 1136 informix error..please HELP!!! Hi everybody, I have the problem with a few lists and the generated error is: "Fatal error : Error 1136 (bdb_errno 1136) on tfgld410105 in db_insert(51)" I need help with that...I executed the Debugger option and discover an relation error...this error is: 136: ENOSPACE No Space in shared memory I need a Solution, is't urgent, and I don't know resolve that problem..the server was initialized, but, the error still be there. Sorry for my bad english, I speak Spanish. minos1 View Public Profile Find all posts by minos1 Sponsored Links #2 30th January 2004, 21:43 Brendan Shine Senior Member Join Date: Oct 2001 Location: Washington Posts: 129 Baan: LN, Vc&b, IVc4, IVc3, IVb, Triton 3.1b - DB: Informix 7.31 FC6, Oracle 7,8,9,10 - OS: HP-UX 11, AIX, Dynix/ptx 4.4.4 finderr 136 -- ISAM error: no more extents. bshell6.1> finderr 136 -136 ISAM error: no more extents. The database server needs to add an extent to a table but cannot do so. Either not enough disk space is available in the dbspace, or the table has been given the maximum number of extents that is allowed. The database server administrator can determine the cause as follows: 1. Determine the tblspace number for the table. It is the value in the partnum column of the systables table for this table. 2. Convert the tblspace number to hexadecimal and extract its most-significant 2 digits (the high-order byte). This chunk number indicates where the table resides. 3. Use the tbstat or onstat utility -t option to find out disk usage for this table. Note particularly the values reported for npages (disk pages available), nused (disk pages used), and nextns (number of extents). If nused is less than npages, and nextns is large (over 200), the table has too many extents. The upper limit o