Re: sysmaster:syspaghdr

Hi all, here is the query for the still available extents: select {+ ordered, index(a, syspaghdridx) } -- necessary c.tabname, -- the table or index c.dbsname, -- the database b.name, -- the dbspace trunc(a.pg_frcnt / 8) frext -- the free extents from sysmaster:sysdbspaces b, sysmaster:syspaghdr a, sysmaster:systabnames c where a.pg_partnum = sysmaster:partaddr(b.dbsnum, 1) and sysmaster:bitval(a.pg_flags, 2) = 1 and a.pg_nslots = 5 and c.partnum = sysmaster:partaddr(b.dbsnum, a.pg_pagenum) order by 3 asc -- show me the problem candidates first This works in 9.4 and i think it should work in 10, too. But note: for fragmented table or indexes it shows the table (or index) multiple times (for each fragment of a table one row), so you have to consider the dbspace.name column, too. If you find, that you only have a few (< 30) extents left and the table or index should grow in the future, then adjust you NEXT EXTENT SIZE as soon as possible (and consider a scheduled downtime for a rebuild). Hope this helps avoiding a nasty problem. Here are two additional links with interesting and detailed information about this issue: But, i'm sorry - really! - they are in german: :-( http://www.ordix.de/onews2/4_2004/siteengine/page/onews_db/ibm_ids_architektur.html http://www.ordix.de/onews2/1_2005/ibm_ids_reorganisation.php