Re: Extents maxed out???

In article <36D803D7.312ECF3@cornell.edu>, Sandeep Singh <ss64@cornell.edu> writes >Hello all, > >I am facing a strange incidence of a table that has stopped growing >and am writing this in the hope that someone can give me any tips on >what might be going on. > >I am adminitering an OnLine (7.2) instance working as a backend for >BPCS (6.004) in which a table is not allowing any more inserts from >BPCS. I tried to insert a row manually and it gave me an ISAM error >136, which means that the maximum number of extents have been >allocated for the table. > >According to the Informix Error listing, this could be caused either >because of the dbspace getting full (which I am certain is not the >case, besides all the other tables are growing) or that too many extents > >have been allocated to that table -which is also not the case because >the "nextns" value from onstat -t for that table is merely 88 and >although the nextns value may not be an accurate index of the total >number of extents for that table, so I eye-balled the oncheck -pT >listing for that table and 88 appears to be the ball-park figure. > >The table schema does not have a FIRST EXTENT/NEXT EXTENT >defined and so the defaults are: > >FIRST EXTENT: 8 >(CURRENT) NEXT EXTENT: 128 > >The allocated pages is 6504 and used pages is 6504 and the table >is not growing after about 3000 rows! I would appreciate if anybody >who has experienced this or have any ideas on what could be going on >could send me an email. Thanks for your time. > Try unload the table, dbschema the table edit the dbschema to include first extent info and next extent info. Drop the table Reload the table. >Sandeep > >PS: There is no table fragmentation scheme for this database although >BPCS (as for all other tables) has a large number of indexes. The data >pages are less than half the total pages used by the table. > > > > > -- David Williams