PROUTIL IDXANALYS qualifier

Displays information on index blocks.

Syntax

proutil db-name -C idxanalys [ area area-name ]
     [ tenant tenant-name| group group-name| shared ]
     [-csoutput [ -fieldsep sep-value][ -csfilePrefix pref-name ] 
           [ -verbose ] [ -RO ]  ]

Parameters

db-name
Specifies the database to analyze.
area area-name
Specifies that IDXANALYS is to be performed on the area-name area only.
tenant tenant-name
Specifies that IDXANALYS is to be filtered to only provide information related to objects that are owned by tenant-name. If tenant-name is not valid, IDXANALYS exits with an error. Specifying tenant is only allowed on databases enabled for multi-tenancy.
group group-name
Specifies that IDXANALYS is to be filtered to only provide information related to objects that are owned by group-name. If group-name is not valid, IDXANALYS exits with an error. Specifying group is only allowed on databases enabled for multi-tenancy.
shared
Specifies that IDXANALYS is to be filtered to only provide information related to shared objects. Specifying shared is only allowed on databases enabled for multi-tenancy.
-csoutput

Specifies that IDXANALYS output the analysis data to text files in addition to the screen. The result is that the following files are created:

  • db-name .ix.txt — For index analysis output
  • db-name .block.txt — For block analysis output

For more information about the contents of the files, see the Database analysis output.

-fieldsep sep-value
When -csoutput is specified, sep-value indicates the value to separate the columns of output. A space is used by default. Accepted values for sep-value are:
  • Any ASCII character between 0x21 and 0x7E
  • sp — to denote a space (the default)
  • tab — to denote a the TAB character (<\t> or ASCII character 0x09)
-csfilePrefix pref-name
When -csoutput is specified, pref-name indicates a file name prefix. The database name is used by default. All remaining elements of the file name are not customizable.
-verbose
When -csoutput is specified, the first row of the output files contains header names for each column of output. For example:
"Time Stamp" "DBUID" "DB name" "Area" "Area #" "Partition Type" "Tenancy" "Tenancy #" "Partition Policy" "Partition" "Partition #" "Owner" "Table" "Table #" "Index" "Index #" "State" "Fields" "Levels" "Blocks" "Size" "Utilization" "Factor" "DPsOnChain" "DPsOffChain" "LeafBlocks" "LeafBlocksOnChain"
2026-02-27T11:48:13.000-5:00 "yEdqpHgDw5awFMdPYAfWMg" "custdb1" "Control Area" 1 "-" "-" 0 "-" "-" 0 "PUB" "_Area" -71 "_Area-Number" 1027 1 1 1 1 143    1.8    1.0    0.0    0.0 1 0
2026-02-27T11:48:13.000-5:00 "yEdqpHgDw5awFMdPYAfWMg" "custdb1" "Control Area" 1 "-" "-" 0 "-" "-" 0 "PUB" "_AreaExtent" -72 "_AreaExtent-Area" 1028 1 2 1 1 173    2.1    1.0    0.0    0.0 1 0
2026-02-27T11:48:13.000-5:00 "yEdqpHgDw5awFMdPYAfWMg" "custdb1" "Schema Area" 6 "-" "-" 0 "-" "-" 0 "PUB" "_Client-Session" -200 "_Auth-time" 1083 1 1 1 1 3    0.0    1.0 "-" "-" "-" "-"
-RO
Runs the utility in read-only mode. Use read-only mode to connect to databases on read-only media or to diagnose and repair issues on a stopped database before starting it. Read-only mode allows any number of connections at once, up to the maximum number of connections. You may run multiple diagnostic utilities concurrently, while the database broker is down, if they all support read-only connection and you run them in read-only mode. This reduces bottlenecks and expedites disaster recovery on large databases.
Note: Use -RO with caution because it is designed to work only with a read-only connection. Unexpected errors may result if you specify -RO when using a single-user or multi-user connection.

IDXANALYS calculates the number of index blocks and the percentage of the database used by the index blocks. The _UserStatus virtual system table displays the utility's progress. See Manage Performance for more information.

Output format

Both non-partitioned and partitioned indexes appear in the summary for shared objects in alphabetical order by name. For partitioned indexes, the data for the index of indexes appears first, followed by the remainder of partitions in alphabetical order by partition name. There is no differentiation between local and global indexes. However, a global index will have only a single line of information with a partitionId of 0.

Example

The following output is a sample display of PROUTIL IDXANALYS:

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
Record Number: ~914 +/- 6.8% (95% confidence, SRS approximation); Record Size: ~1.6K bytes



INDEX BLOCK SUMMARY FOR AREA "Index Area3": 23
-------------------------------------------------------


INDEX BLOCK SUMMARY FOR SHARED OBJECTS:
--------------------------------------------
Table                      Index  Fields Levels         Blocks    Size  % Util  Factor    % DPsOnChain    % DPsOffChain      LeafBlocks  LeafBlocksOnChain
PUB.OrderLine
  ItemNum                     45       1      2            305    1.2M    49.6     2.0             N/A              N/A             N/A                N/A
  OrderLine                   44       2      3          19593  103.6M    67.9     1.6            50.0              0.0           19560               9771
  OrderLineStatus             46       1      2            307    1.2M    49.4     2.0             N/A              N/A             N/A                N/A

                    --------------------------------------------------------------------------------------------------------------------------------------
Subtotals:                                               20205  105.9M    67.3     0.6            50.0              0.0           19560               9771

For more information, see Analyze index use.