Tablespace Utilization Page
The table and chart in the Tablespace Utilization page show the amount of used and free space in each tablespace.
To open the Tablespace Utilization page
- Select the Spotlight on Oracle RAC connection in the Spotlight Browser.
-
Click Disk Storage | Tablespace Utilization.
The Tablespace Utilization Grid
Note: There may be a discrepancy between the tablespace number on the Spotlight on Oracle RAC home page and the number of tablespaces displayed in the Tablespace Utilization page. This is because the count on the home page excludes temporary tablespaces.
| Column | Description |
|---|---|
|
Name |
The name of the tablespace. |
|
Total (MB) |
The total amount of space in this tablespace. |
|
Free (MB) |
The total amount of free space in this tablespace. |
|
Used (MB) |
The amount of space used in this tablespace. |
| Contents | This column informs you that the contents of the tablespace are either PERMANENT or TEMPORARY. |
| Status | The current status of the tablespace (ONLINE, OFFLINE, or READ ONLY). |
| Fragments | The number of fragments in this tablespace. (Blank for temporary tablespaces OR if the value is zero.) |
| Allocation type | The type of extent allocation to be used for this tablespace. Values include USER (where the user is responsible for the way in which extents are to be allocated), SYSTEM (where the system automatically allocates extents), or UNIFORM (where the same uniform size is to be applied to all extents). |
| Avg Frag (MB) | The average size of fragments in this tablespace. (Blank for temporary tablespaces OR if the value of the Fragments column is zero.) |
| Bigfile |
Whether the tablespace is a BIGFILE tablespace. BIGFILE tablespaces are supported only for locally managed tablespaces with automatic segment-space management. Note: Available for Oracle 10g and later. |
| Default table compression |
Whether table compression is enabled for this tablespace by default. Note: Available for Oracle 10g and later. |
| Extent management | This column displays the type of extent management tracking that is to be used for the tablespace. The values specified can be DICTIONARY (where the management of extents is to be maintained within the Oracle data dictionary), or LOCAL (where the management of extents is to be maintained within the tablespace itself). |
| Forced logging |
Whether the tablespace is in FORCE LOGGING mode. In FORCE LOGGING mode, Oracle overrides any NO LOGGING setting for individual objects, and logs all changes to all objects in the tablespace except changes to temporary segments. The database must be open and in READ WRITE mode. The use of FORCE LOGGING can affect performance. |
| Logging | This column shows you whether or not redo entries are to be generated for the tablespace. The values specified can either be LOGGING or NO LOGGING. |
| Max Frag (MB) | The biggest fragment in this tablespace. (Blank for temporary tablespaces OR if the value of the Fragments column is zero.) |
|
Min Frag (MB) |
The smallest fragment in this tablespace. (Blank for temporary tablespaces OR if the value of the Fragments column is zero.) |
| Retention |
Whether unexpired UNDOs are retained in the tablespace. This applies only to UNDO tablespaces. Note: Available for Oracle 10g and later. |
|
Segment management |
Whether free and used segments are managed manually via free lists, or automatically via bitmaps. |