All of the details shown in the Tablespace Partition Information pane are listed below in alphabetic order. This pane is available on the Details tab of the Tablespace Analysis drilldown.
Initially, details are shown in Spotlight's default order. You can sort and arrange them in different ways using options on the right-click menu for column headers.
Description |
Value |
Number of Quiescers |
The number of agents that have quiesced a tablespace in SHARE, UPDATE, or EXCLUSIVE mode. If the value is greater than 0 (zero), click the Quiescers tab to see more information about the quiescer(s). |
State Change OBID |
The identifier of the object that caused the state of a tablespace to be "Load pending" or "Delete pending". |
State Change Tbsp ID |
The identifier of the tablespace for the object that caused the state of a tablespace to be "Load pending" or "Delete pending". |
Minimum Recovery Time |
The earliest point in time to which a tablespace can be rolled forward. The timestamp includes year, month, date, and hour, in that order. |
Total Pages |
The total number of pages in a tablespace. This is a measure of the amount of operating system space used by the tablespace. For a DMS tablespace, the total is the sum of table-space container sizes, including overhead pages. For an SMS tablespace, the total is the sum of all file space used for the tables stored in the tablespace. (The total is only available when the buffer pool switch is on). |
Usable Pages |
The total number of pages in a DMS tablespace minus overhead pages. For an SMS tablespace, usable pages are equal to total pages. |
Used Pages |
The total number of pages currently used in a DMS table space. For an SMS table, used pages are equal to total pages. |
Free Pages |
The number of pages currently free in a tablespace. This value applies to DMS tablespaces. A value of 0 (zero) is shown for SMS tablespaces. |
Pending Free Pages |
The number of pages in a tablespace that would become free if all pending transactions were committed or rolled back. This value applies to DMS tablespaces. A value of 0 (zero) is shown for SMS tablespaces. |
Current Top Page |
The page number of the first free extent in a table space. This is the extent that comes after the last extent allocated. The top page marks the current level of space use in a tablespace. It applies to DMS tablespaces. A value of 0 (zero) is shown for SMS tablespaces. |
Rebalance Extents Remaining |
The number of extents the rebalancer still needs to move. This value can be used along with rebalance extents processed (see above) to track the progress of rebalancing. It applies to DMS tablespaces. A value of 0 (zero) is shown for SMS tablespaces. |
Rebalance Extents Processed |
The number of extents the rebalancer has moved since it was started. This value can be used along with rebalance extents remaining (see below) to track the progress of rebalancing. It applies to DMS table spaces. A value of 0 (zero) is shown for SMS tablespaces. |
Rebalancer Priority |
The priority at which the rebalancer is running in the database. This value applies to DMS tablespaces. A value of 0 (zero) is shown for SMS tablespaces. |
Rebalancer Start |
The time the rebalancer was first started. The timestamp includes year, month, date, and hour, in that order. This value applies to DMS tablespaces. A value of 0 (zero) is shown for SMS tablespaces. |
Rebalancer Restart |
The time the rebalancer was restarted after being paused or stopped. The timestamp includes year, month, date, and hour, in that order. This value applies to DMS tablespaces. A value of 0 (zero) is shown for SMS tablespaces. |
Rebalance Last Extent Moved |
The last extent moved by the rebalancer. This value applies to DMS tablespaces. A value of 0 (zero) is shown for SMS tablespaces. |
Tablespace Ranges |
The total number of ranges in a tablespace map. This value applies to DMS tablespaces. A value of 0 (zero) is shown for SMS tablespaces. |
Tablespace Containers |
The total number of containers in a tablespace. |
Initial Size |
The initial size of an automatic storage tablespace in bytes. This is the size of the tablespace when it was created. The value applies to non-temporary automatic storage tablespaces. |
Current Size |
The current size of the tablespace. |
Maximum Size |
The maximum size in bytes to which a tablespace can automatically grow. If the tablespace can grow without restriction, Unlimited is shown. If the values for maximum size and current size are the same, the tablespace can no longer grow. This value applies to tablespaces for which automatic resizing is enabled. |
Increase Size |
This value indicates whether automatic resizing is enabled for a tablespace. Automatic is shown if auto resize is enabled. When an auto-resize tablespace needs more space, DB2 automatically determines the amount of space to add. The value applies to DMS tablespaces and non-temporary automatic storage tablespaces. A value of 0 (zero) is shown for SMS tablespaces and temporary automatic storage tablespaces. |
Increase Size Percent |
The amount of space that will be added to an auto-resize tablespace when it becomes full and has not reached its maximum size. DB2 automatically determines how much space to add. The increase is based on a percentage of the current tablespace size at resize time. This value applies to tablespaces for which automatic resizing is enabled. |
Last Resize Time |
The last time the size of a tablespace was increased successfully. The timestamp includes year, month, date, and hour, in that order. This value applies to tablespaces for which automatic resizing is enabled. |
Last Resize Failed |
This value indicates whether the last attempt to automatically increase the size of the tablespace failed:
For an automatic storage tablespace, a failed attempt could mean the database is out of space. For a non-automatic storage table space, a failed attempt could mean that the filesystem is full or that the maximum size of the tablespace has been reached. This value applies to tablespaces for which automatic resizing is enabled. |
Paths Dropped |
(DB2 9.7 and later) Indicator whether the tablespace exists on any storage paths that no longer exist. |
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center