Very Computer

Thanks for your help.

Regards,
Thanh Ngo

Study onstat -d and also make sure your table is actually going into the
dbspace you think it is.

here's what Informix says about ISAM error -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 of extents per table
is between 200 and 50.
                    The limit varies with the table definition and the
disk-page size in use.
                    Reallocate the table using fewer, larger extents.
Unload the table data to a flat
                    file. Drop the table. Re-create the table,
specifying a first-extent size sufficient
                    to hold all its current data and a next-extent size
between one-fourth and
                    one-six*th its current size. Then reload the data
into the table.

                    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.

How big are the extents for your tables?
Do you still have enough space left in your dbspaces to
accomodate the allocation of additional extents?

Quote:>Can someone show me how to find if my table is hit
>max number of extents which a table can have?.
>I got error -271 and -136 when loading data to a table,
>and this table only has 7 extents.

>Thanks for your help.

>Regards,
>Thanh Ngo

I refer you to a utility written by Tim Schaefer to calculate exactly your
question. You can find it at URL:
  http://www.iiug.org/members/memb_software/archive/maxextents

However, I don't believe that's your problem, unless you have gadzillion
special columns and another gadzillion indexes on that table. In either case
you'd need to go back to the table's design phase and rethink some things
about the way the table was build.

Assuming you have kept to a sane number of indexes and special columns, your
dbspace is most likely filling up during the load.  It may not show afterward
because the transaction may be rolling back before you have  a chance to
investigate.

Download the following utilities from IIUG:

beautify-unl.sh  :
    http://www.iiug.org/members/memb_software/archive/beautify-unl
partitions.sh    :
    http://www.iiug.org/members/memb_software/archive/partitions
dbspace-pages.sh :
    http://www.iiug.org/members/memb_software/archive/monitor_space

(dbspace-pages.sh is one of three utilities in article monitor_space.)

Note: You need beautify-unl.sh because the other utilities call them.

Keep at lease two windows open.  On the first window start the load. In the
other window keep running dbspace-pages.sh so you can see if the dbspace is
filling up.  If you like, open a third window and keep running partitions.sh,
specifying only this target table [partitions.sh -t my_table].

This way you can monitor both the table and dbspace to see what's wrong.

Good luck.
    -- Jake (shameless plugger) Salomon

 -----  Posted via NewsOne.Net: Free (anonymous) Usenet News via the Web  -----
  http://newsone.net/ -- Free reading and anonymous posting to 60,000+ groups
   NewsOne.Net prohibits users from posting spam.  If this or other posts

Art S. Kagel