Results 1 to 12 of 12
  1. #1
    Join Date
    Mar 2002
    Posts
    5

    Post Unanswered: Error: 136 No more extents

    Hi all,

    I must be overlooking something, I am running Informix730UC5 on solaris 7, I 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, 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

  2. #2
    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 ???

  3. #3
    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

  4. #4
    Join Date
    Feb 2002
    Posts
    2,232
    What are your extent sizes ?

  5. #5
    Join Date
    Mar 2002
    Posts
    19
    Please send us :
    1) systables information for this table
    2) output of onstat -d
    3) output of onstat -pt <databasename>:table

    TIA
    Miranda

  6. #6
    Join Date
    Mar 2002
    Posts
    5
    Originally posted by rnealejr
    What are your extent sizes ?
    extent size 1999720
    next size 999860

  7. #7
    Join Date
    Mar 2002
    Posts
    5
    Originally posted by townscream
    Please send us :
    1) systables information for this table
    2) output of onstat -d
    3) output of onstat -pt <databasename>:table

    TIA
    Miranda
    TBLspace Report for archive:informix.ar_entr

    Physical Address 300024
    Creation date 07/06/00 23:47:02
    TBLspace Flags 802 Row Locking
    TBLspace use 4 bit bit-maps
    Maximum row size 62
    Number of special columns 0
    Number of keys 4
    Number of extents 17
    Current serial value 1
    First extent size 999860
    Next extent size 499930
    Number of pages allocated 16777215
    Number of pages used 16777215
    Number of data pages 9873272
    Number of rows 296198160
    Partition partnum 3145761
    Partition lockid 3145761
    Extents
    Logical Page Physical Page Size
    0 500003 999860
    999860 b00003 999860
    1999720 c00003 999860
    2999580 d00003 999860
    3999440 e00003 999860
    4999300 1200003 999860
    5999160 1300003 999860
    6999020 1400003 999860
    7998880 1500003 999860
    8998740 1600003 999860
    9998600 1700003 999860
    10998460 1800003 999860
    11998320 2000003 999860
    12998180 2100003 999860
    13998040 2230d43 823997
    14822037 2800003 999860
    15821897 2900003 955318

    address number flags fchunk nchunks flags owner name
    10102150 1 1 1 1 N informix dbs10root
    10134f30 2 1 2 1 N informix dbs10log01
    10134ff0 3 1 3 40 N informix dbs10data01
    101350b0 4 2001 4 1 N T informix dbs10temp01
    10135170 5 2001 25 1 N T informix dbs10temp02
    10135230 6 2001 26 1 N T informix dbs10temp03
    101352f0 7 2001 27 1 N T informix dbs10temp04
    7 active, 2047 maximum

    Chunks
    address chk/dbs offset size free bpages flags pathname
    10102210 1 1 25 100000 58517 PO- /links/dbs10root_01
    101024d0 2 2 0 250000 9947 PO- /links/dbs10log01_01
    101025b0 3 3 0 1000000 80 PO- /links/dbs10data01_01
    10102690 4 4 0 1024000 1023947 PO- /links/dbs10temp01_01
    10102770 5 3 0 1000000 137 PO- /links/dbs10data01_02
    10102930 7 3 0 1000000 137 PO- /links/dbs10data01_04
    10102a10 8 3 0 1000000 137 PO- /links/dbs10data01_05
    10102af0 9 3 0 1000000 0 PO- /links/dbs10data01_06
    10102bd0 10 3 0 1000000 137 PO- /links/dbs10data01_07
    10102cb0 11 3 0 1000000 137 PO- /links/dbs10data01_08
    10102d90 12 3 0 1000000 137 PO- /links/dbs10data01_09
    10102e70 13 3 0 1048575 0 PO- /links/dbs10data01_10
    10102f50 14 3 0 1048575 0 PO- /links/dbs10data01_11
    10103030 15 3 0 1023992 24129 PO- /links/dbs10data01_12
    10103110 16 3 0 1024000 0 PO- /links/dbs10data01_13
    101031f0 17 3 0 1024000 0 PO- /links/dbs10data01_14
    101032d0 18 3 0 1024000 0 PO- /links/dbs10data01_15
    101033b0 19 3 0 1024000 0 PO- /links/dbs10data01_16
    10103490 20 3 0 1024000 0 PO- /links/dbs10data01_17
    10103570 21 3 0 1024000 0 PO- /links/dbs10data01_18
    10103650 22 3 0 1024000 0 PO- /links/dbs10data01_19
    10103730 23 3 0 1024000 0 PO- /links/dbs10data01_20
    10103810 24 3 0 1024000 24137 PO- /links/dbs10data01_21
    101038f0 25 5 0 1024000 1023947 PO- /links/dbs10temp02_01
    101039d0 26 6 0 1024000 1023947 PO- /links/dbs10temp03_01
    10103ab0 27 7 0 1024000 1023947 PO- /links/dbs10temp04_01
    10103b90 28 3 0 1024000 24137 PO- /links/dbs10data01_22
    10103c70 29 3 0 1024000 24137 PO- /links/dbs10data01_23
    10103d50 30 3 0 1024000 3592 PO- /links/dbs10data01_24
    10103e30 31 3 0 1024000 16792 PO- /links/dbs10data01_25
    10103f10 32 3 0 1024000 24137 PO- /links/dbs10data01_26
    10129a30 33 3 0 1024000 24137 PO- /links/dbs10data01_27
    10129b10 34 3 0 1024000 0 PO- /links/dbs10data01_28
    10129bf0 35 3 0 1024000 24137 PO- /links/dbs10data01_29
    10129cd0 36 3 0 1024000 41568 PO- /links/dbs10data01_30
    10129db0 37 3 0 1024000 0 PO- /links/dbs10data01_31
    10129e90 38 3 0 1024000 0 PO- /links/dbs10data01_32
    10134830 39 3 0 1024000 0 PO- /links/dbs10data01_33
    10134910 40 3 0 1024000 0 PO- /links/dbs10data01_34
    101349f0 41 3 0 1024000 17479 PO- /links/dbs10data01_35
    10134ad0 42 3 0 1024000 51197 PO- /links/dbs10data01_36
    10134bb0 43 3 0 1024000 767997 PO- /links/dbs10data01_37
    10134c90 44 3 0 1024000 1023997 PO- /links/dbs10data01_38
    10134d70 45 3 0 1024000 1023997 PO- /links/dbs10data01_39
    10134e50 46 3 0 1024000 1023997 PO- /links/dbs10data01_40

    owner informix
    partnum 3145761
    tabid 101
    rowsize 62
    ncols 15
    nindexes 4
    nrows 207140117
    created 06/07/2000
    version 8847439
    tabtype T
    locklevel R
    npused 6904671
    fextsize 1999720
    nextsize 999860
    flags 0
    site
    dbname

    HTH
    TIA

  8. #8
    Join Date
    Mar 2002
    Posts
    19
    "If nextns is small or the difference between npages and nused is less than the size of the next-extent size for the table, not enough disk space is available in the dbspace where the table resides. Use the chunk number from step 2 and the ON-Monitor or ON-Monitor Chunks display to determine the dbspace, then add a new chunk to that dbspace"

    I really cant figure out what´s happening
    The table should be able to aquire an extra extent
    It´s in dbspace 3 that has chunks with sufficient space

    Sorry.

  9. #9
    Join Date
    Feb 2002
    Posts
    2,232
    Sorry I have not replied but I have been on vacation.

    Well, here is the deal - you have maxed out your pages (16 million is it). If you are still seeking a solution, please respond ...

  10. #10
    Join Date
    Mar 2002
    Posts
    5
    Originally posted by rnealejr
    Sorry I have not replied but I have been on vacation.

    Well, here is the deal - you have maxed out your pages (16 million is it). If you are still seeking a solution, please respond ...
    I would appreciate any comments or direction you may be able to provide. At this stage, I am looking into the feasibility of using a UNION VIEW to get around this at this point.

    TIA

  11. #11
    Join Date
    Feb 2002
    Posts
    2,232
    You will have to fragment your table using the ALTER FRAGMENT statement. This will allow your table to keep growing.

    Let me know if you need any additional information.

    Good luck !

  12. #12
    Join Date
    Apr 2004
    Posts
    10

    insert

    what are the reason about that a register of a table is not insert during a
    applicative execution and the engine doesn´t give any error.
    what we made and work it was to create an extent, at the beginning this
    goes ok, but after a day the problems start to occurr again.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •