Oracle RAC Tablespaces Test
Tablespaces should be adequately sized. If not, then the tablespaces may frequently run very low on free space, causing all statements that attempt to acquire new space in the tablespace to fail. This in turn will result in serious performance issues ranging from slowdowns to shutdowns. Continuous monitoring of tablespace size and usage is hence important.
The RAC Tablespaces test auto-discovers the tablespaces managed by the Oracle RAC, and reports how well every tablespace has been utilized. In the process, the test also reveals the type of database objects (tables, indexes, partitions, LOB segments, etc.) that are occupying space in the tablespace. This way, you will be able to instantly identify the tablespace left with very little free space, and also zero-in on those objects that could be eroding space in that tablespace.
Target of the test : Oracle RAC
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for each tablespace managed by the monitored Oracle RAC
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Table size |
Indicates the size of the tables present in this tablespace. |
GB |
A high value for these measures indicates that a tables and indexes consume a large chunk of space in the tablespace. |
Index size |
Indicates the space consumed by the indexes on the tables present in this tablespace. |
GB |
|
Table partition size |
Indicates the size of all partitions of tables present in this tablespace. |
GB |
Partitioning addresses key issues in supporting very large tables and indexes by letting you decompose them into smaller and more manageable pieces called partitions. Each partition of a table or index must have the same logical attributes, such as column names, datatypes, and constraints, but each partition can have separate physical attributes such as pctfree, pctused, and tablespaces. A high value for these measures indicates that table and index partitions consume a large chunk of space in the tablespace. |
Index partiton size |
Indicates the size of all partitions of indexes present in this tablespace. |
GB |
|
Lob segment size |
Indicates the size of LOB segments in this tablespace. |
GB |
LOBs (Large Object) are Oracle’s data structures designed to store and retrieve large amounts of unstructured data such as video, audio, photo images, etc within the database. Whenever a table containing a LOB column is created, two segments are created to hold the specified LOB column. These segments are of type LOBSEGMENT and LOBINDEX. The LOBINDEX segment is used to access LOB chunks/pages stored in the LOBSEGMENT segment. The values of these measures report the size of the LOBSEGMENT sements and the LOBINDEX segments (respectively). A high value for these measures, quiet naturally, indicates that too many large objects are stored in the tablespace. |
Lob index size |
Indicates the size of LOB indexes in this tablespace. |
GB |
|
Lob partition size |
Indicates the size of table partitions with LOBs in this tablespace.
|
GB |
You can partition tables with LOBs. As a result, LOBs can take advantage of all of the benefits of partitioning. For example, LOB segments can be spread between several tablespaces to balance I/O load and to make backup and recovery more manageable. LOBs in a partitioned table also become easier to maintain. A high value for this measure indicates that table partitions containing LOB columns are consuming a large amount of space in this tablespace. |
Maximum size |
Indicates the maximum extent up to which a tablespace can grow. |
GB |
|
Used size |
Indicates the size up to which this tablespace has been utilized. |
GB |
If this value is very high, it indicates that the tablespace memory is almost full. |
Free size |
Indicates the amount of unused space available in this tablespace. |
GB |
If this value is very low, then it indicates over-utilization of the tablespace. |
Free space usage |
Indicates the space available for overall growth expressed as a ratio of Free size with respect to the Maximum size of the tablespace. |
Percent |
If this value is very low, then it indicates over-utilization of the tablespace. Also, if the value of this measure is below 80 %, then sufficient space must be allocated to the tablespace. |
Recycle bin size |
Indicates the current recycle bin size of this tablespace. |
MB |
|