Use PROUTIL IDXANALYS to get information about index blocks and usage, as shown:

 proutil db-name -C idxanalys
After running the command, review the output. It should be like the following example:
INDEX BLOCK SUMMARY FOR AREA "Index Area2": 22
-------------------------------------------------------


INDEX BLOCK SUMMARY FOR SHARED OBJECTS:
--------------------------------------------
Table                      Index  Fields Levels         Blocks    Size  % Util  Factor    % DPsOnChain    % DPsOffChain      LeafBlocks  LeafBlocksOnChain
PUB.Order
  CustOrder                   40       2      3          20006   97.4M    62.6     1.7            98.4              0.6           19973              19675
  OrderDate                   41       1      2            386  418.9K    13.6     2.7             N/A              N/A             N/A                N/A
  OrderNum                    39       1      3          11066   85.4M    99.1     1.0             0.0             99.0           11052                  0
  OrderStatus                 42       1      2            386  420.4K    13.7     2.7             N/A              N/A             N/A                N/A
  SalesRep                    43       1      2            386  418.5K    13.6     2.7             N/A              N/A             N/A                N/A

                    --------------------------------------------------------------------------------------------------------------------------------------
Subtotals:                                               32230  184.1M    73.4     0.9            52.4             46.6           31025              19675

The IDXANALYS qualifier provides:

  • The number of fields and levels in each index
  • The size of each index, in blocks and in bytes
  • The percent utilization within the index (that is, the degree of disk space efficiency)
  • A factor value that indicates whether to rebuild each index
  • A summary of indexes for the current database and the percentage of total index space used by each index
  • Visibility into delete placeholder usage within index leaf blocks, including the proportion of leaf‑block space occupied by delete placeholders, whether those placeholders are on the delete chain, and the number of leaf blocks affected
Note: You can run PROUTIL IDXANALYS while the database is in use; however, PROUTIL generates only approximate information. For the most accurate result, scan the full index while the database is shut down.

For more information, see PROUTIL IDXANALYS.

Utilization—% Util

The most important field in the IDXANALYS display is the % Util field. This field shows the degree of consolidation of each index. If an index is several hundred blocks and your application most frequently retrieves data, an index utilization of 85% or higher is optimal. There are two ways to increase an index's utilization rate:

  • Compress the index with the database online or offline with the PROUTIL IDXCOMPACT utility. For more information, see PROUTIL IDXCOMPACT qualifier.
  • Rebuild and compress the index offline with the PROUTIL IDXBUILD utility. For more information, see PROUTIL IDXBUILD qualifier.

Index structure and size—Levels and Blocks

The Levels field shows the number of reads PROUTIL performs in each index per entry. The Blocks field show you the size of each index.

Rebuild indicator—Factor

The Factor field is based on the utilization and size of the index; it is an indicator of when you should rebuild indexes. The table below provides a description of the different ranges of values for the Factor field. When you use the Factor field to decide whether to rebuild an index, consider the context of how the particular index is used. For example, if an index is highly active, with continuous insertions and deletions, its utilization rate varies greatly, and a rebuild is inadvisable. However, a static index with a high factor value benefits from a rebuild.

Table 1. Factor values
Factor range Description
1 to 2 The index is well-utilized and balanced. You do not have to rebuild it.
2 to 2.5 The index is less than 50 percent utilized and/or the index is unbalanced. You should consider a rebuild.
2.5 to 3 The index is less than 25 percent utilized and/or the index is very unbalanced. You should rebuild this index.

Delete placeholder impact

While %Util and Factor describe overall index efficiency, they do not distinguish between space used by active keys and space consumed by delete placeholders. The following delete placeholder-related columns provide this additional visibility:
  • % DPsOnChain—Specifies the percentage of leaf‑block key storage occupied by delete placeholder bytes that are still linked through the index delete chain. This value is calculated relative to the total bytes used by all keys on leaf blocks, including delete placeholders. High values can indicate sustained delete-chain growth and potential traversal overhead.
  • %DPsOffChain—Specifies the percentage of delete placeholder bytes that are no longer on the indexdelete chain but still occupy leaf-block key space, helping explain residual space consumption even whenutilization appears low. This value is calculated relative to the total bytes used by all keys on leaf blocks,including delete placeholders.
  • LeafBlocks—Specifies the total number of leaf blocks in the index.
  • LeafBlocksOnChain—Specifies the number of leaf blocks that are part of the index delete chain.
Note: The delete placeholder-related columns are populated only for unique indexes. Non‑unique indexes do not generate delete placeholders and therefore display N/A values for these columns.
High values for % DPsOnChain combined with a large number of LeafBlocksOnChain, typically indicate that delete placeholders dominate the index structure and that the index is a strong candidate for PROUTIL IDXCOMPACT. The delete placeholder-related columns are especially useful when evaluating the effectiveness of PROUTIL IDXCOMPACT operations, as changes in these values can indicate how delete placeholders are being removed from the index structure.
When used together with %Util and Factor, these columns help you:
  • Distinguish between poor utilization caused by normal index growth versus delete-placeholder activity.
  • Make more informed decisions about whether an index rebuild will reclaim meaningful space.
  • Identify indexes where delete-chain behavior, rather than overall size or depth, is the primary contributorto inefficiency.