Analyzing Table Information with SAPDBA
Use
You can use SAPDBA for Informix to comprehensively analyze information about a single table. If you want to look at information on more than one table, see
Analyzing Tables by Fill Level, Size, and Extents with SAPDBA.
If a table has very few extents left, an alert is raised in the Release 4 alert monitor in the Computing Center Management System (CCMS) of the R/3 System. For more information, see
Monitoring the Database with the Release 4 Alert Monitor (Informix).
Prerequisites
Procedure
SAPDBA displays the report.

Sometimes SAPDBA offers to
update statistics before the Table Information report screen appears, because statistics data on the table is out-of-date. You can immediately perform an update for the table concerned to get an accurate report on it. For more information about how to identify tables needing an update and how to perform the update, see Update Statistics with SAPDBA.The entries on the report have the following meanings:
Entry |
Meaning |
dbspace |
Shows where the table is logically stored. If the table is fragmented, it is stored in a number of different dbspaces instead of in one single dbspace. |
fragmentation |
Allows tables to be spread across separate dbspaces. Possible values are none, round-robin, or by expression. Only relevant for Informix version 7.1 or later. |
locking mode |
Refers to how data in the table is locked by the database server. |
first extent |
Shows the size (in kilobytes) of the first extent (that is, physical storage unit) of the table |
next extent |
Shows the size (in kilobytes) of the next extent, which would be allocated if the table needed expanding |
size |
Shows how big the table is (in kilobytes). The size given here is not necessarily filled with data. See the fill level field for how full the table is. |
extents |
Shows the number of extents currently used by the table, with the number still available for extension of the table shown in brackets. If there are no extents still available and the table needs expanding, SAPDBA reports an error message. You can prevent this situation arising by performing Reorganize Single Table. |
rows |
Shows the number of rows in the table |
columns |
Shows the number of columns in the table |
row size |
Shows the width of a row in bytes |
indexes |
Shows the number of indexes on the table |
fill level |
Shows approximately how full the table is. Fill level is not known immediately if the table contains blobpages. In this case, the field simply contains a hyphen. You can request SAPDBA to calculate the table fill level. |
SAPDBA has to count the blobpages individually, so this can take some time, especially with larger tables. The fill level is calculated for data pages and blobpages together.

SAPDBA locks the table when calculating fill level. A locked table can affect the operation of the R/3 System if the table needs to be accessed. Therefore, it is best to execute this action when the R/3 System is down or not being heavily used.
Result
You now have a better picture of the storage situation for the table in question. If you want to change the storage parameters on the table or its indexes, choose one of the following:
See also:
Informix documentation