9 Pluggable Databases
This section provides details on the Pluggable Databases (PDB) metrics.
9.1 Datafiles
This section provides details on the datafile metrics.
9.1.1 Datafile Name
Name of the database file or temporary file.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The FILE_NAME column of the CDB_DATA_FILES view if a permanent datafile. The FILE_NAME column of the CDB_TEMP_FILES view if a temporary file.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.1.2 Tablespace
Name of the tablespace to which the file belongs
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The TABLESPACE column of the CDB_DATA_FILES view if a permanent datafile; the TABLESPACE column of the CDB_TEMP_FILES view if a temporary file.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.1.3 Autoextensible
Autoextensible indicator.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The AUTOEXTENSIBLE column of the CDB_DATA_FILES view if a permanent datafile; the AUTOEXTENSIBLE column of the CDB_TEMP_FILES view if a temporary file.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.1.4 Initial File Size
Creation size of the file (in bytes)
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The CREATE_BYTES column of the V$DATAFILE view if a permanent datafile; the CREATE_BYTES column of the V$TEMPFILE view if a temporary file.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.1.5 File Size
Size of the file in bytes.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The BYTES column of the CDB_DATA_FILES view if a permanent datafile; the BYTES column of the CDB_TEMP_FILES view if a temporary file.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.1.6 Increment By
Number of tablespace blocks used as autoextension increment. Block size is contained in the BLOCK_SIZE column of the CDB_TABLESPACES view.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The INCREMENT_BY column of the CDB_DATA_FILES view if a permanent datafile; the INCREMENT_BY column of the CDB_TEMP_FILES view if a temporary file.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.1.7 Max File Size
Maximum file size in bytes
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The MAXBYTES column of the CDB_DATA_FILES view if a permanent datafile; the MAXBYTES column of the CDB_TEMP_FILES view if a temporary file.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.1.8 Storage Entity
The filesystem or the raw device used by this datafile or temporary file.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
Perl script utility to retrieve the full file path.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.1.9 Status
The ONLINE status of the database file (one of SYSOFF, SYSTEM, OFFLINE, ONLINE, RECOVER) or the status of the temporary file (one of OFFLINE, ONLINE, UNKNOWN).
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The ONLINE_STATUS column of the CDB_DATA_FILES view if a permanent datafile; the STATUS column of the CDB_TEMP_FILES view if a temporary file.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.2 Database Feature Usage
This section provides details on database feature usage metrics.
9.2.1 DBID
Database identifier of the database being tracked
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The DBID column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.2 Feature Name
Name of the feature
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The NAME column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.3 Version
Database version in which the feature was tracked
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The VERSION column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.4 Detected Usages
Number of times the system has detected usage for the feature
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The DETECTED_USES column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.5 Feature Info
This column stores feature-specific usage data in character format.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The FEATURE_INFO column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.6 Total Samples
Number of times the system has woken up and checked for feature usage
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The TOTAL_SAMPLES column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.7 Count
This column stores feature-specific usage data in number format.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The AUX_COUNT column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.8 Currently Used
Indicates whether usage was detected the last time the system checked (TRUE) or not (FALSE)
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The CURRENTLY_USED column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.9 First Usage Date
First sample time the system detected usage of the feature
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The FIRST_USAGE_DATE column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.10 Last Sample Date
Amount of time (in seconds) between the last two usage sample times
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The LAST_SAMPLE_DATE column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.11 Last Sample Period
Amount of time (in hours) between the last two usage sample times
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The LAST_SAMPLE_PERIOD column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.2.12 Last Usage Date
Last sample time the system detected usage of the feature
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The LAST_USAGE_DATE column from the CDB_FEATURE_USAGE_STATISTICS view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information about which database features are being used.
9.3 Invalid Objects
This metric category contains the metrics associated with invalid objects.
9.3.1 Total Invalid Object Count
This metric represents the total invalid object count.
This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.
Metric Summary for Database Control and Cloud Control
The following table shows how often the metric‘s value is collected and compared against the default thresholds. The ‘Consecutive Number of Occurrences Preceding Notification‘ column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 24 Hours After Every Sample > Not Defined Not Defined* 1 %value% object(s) are invalid in the database.
9.4 Invalid Objects by Schema
This metric category contains the metrics that represent the number of invalid objects in each schema.
9.4.1 Owner‘s Invalid Object Count
This metric represents the invalid object count by owner.
This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.
Metric Summary for Database Control and Cloud Control
The following table shows how often the metric‘s value is collected and compared against the default thresholds. The ‘Consecutive Number of Occurrences Preceding Notification‘ column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 24 Hours After Every Sample > Not Defined Not Defined 1 %value% object(s) are invalid in the %owner% schema in pluggable database %pdbName%
Data Source
For each metric index:
SELECT count(1)
User Action
View the status of the database objects in the schema identified by the Invalid Object Owner metric. Recompile objects as necessary.
9.5 Response
Response metrics represent the responsiveness of the Oracle Server, with respect to a client. For PDB, it is also indicative of the state of the PDB. For example, an Open state maps to Up and a Closed/Mounted state maps to Down. If the PDB target exists but the PDB has been dropped/unplugged from the CDB, the target will be in Metric Collection Error.
9.5.1 State
This metric represents the state of the pluggable database.
Metric Summary for Database Control and Cloud Control
The following table shows how often the metric‘s value is collected and compared against the default thresholds. The ‘Consecutive Number of Occurrences Preceding Notification‘ column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 5 Minutes After Every Sample MATCH MOUNTED DOWN|UNKNOWN* 1 The database status is %value%..
User Action
Check the listener configured for the CDB to make sure it is running and serves the CDB. If listener is fine, check if the PDB is in the mount/closed state and open the PDB.
9.5.2 Status
This metric checks whether a new connection can be established to a database. If the maximum number of users is exceeded or the listener is down, this test is triggered.
Metric Summary for Database Control and Cloud Control
The following table shows how often the metric‘s value is collected and compared against the default thresholds. The ‘Consecutive Number of Occurrences Preceding Notification‘ column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 5 Minutes After Every Sample = Not Defined 0 1 Failed to connect to database instance: %oraerr%.
User Action
Check the listener configured for the CDB to make sure it is running and serves the CDB. If listener is fine, check if the PDB is in the mount/closed state and open the PDB.
9.5.3 ORA- Error
This is a user-readable message, including any Ora-error, encountered during response evaluation.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 5 Minutes
User Action
Check the listener configured for the CDB to make sure it is running and serves the CDB. If listener is fine, check if the PDB is in the mount/closed state and open the PDB.
9.6 Rollback Segments
This section describes the rollback metrics.
9.6.1 Name
Name of the rollback segment
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The SEGMENT_NAME column from the CDB_ROLLBACK_SEGS view.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.2 Aveactive
Current size of active extents, averaged over time.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The AVEACTIVE column from the V$ROLLSTAT view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.3 Aveshrink
Average shrink size
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The AVESHRINK column from the V$ROLLSTAT view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.4 Extents
Number of extents in the rollback segment
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The EXTENTS column from the V$ROLLSTAT view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.5 Hwmsize
High watermark of the rollback segment size
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The HWMSIZE column from the V$ROLLSTAT view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.6 Initial Size
Initial extent size in bytes
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The INITIAL_EXTENT column from the CDB_ROLLBACK_SEGS view.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.7 Maximum Size
Maximum number of extents
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The MAX_EXTENTS column from the CDB_ROLLBACK_SEGS view.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.8 Minimum Extents
Minimum number of extents
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The MIN_EXTENTS column from the CDB_ROLLBACK_SEGS view.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.9 Next Size
Secondary extent size in bytes
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The NEXT_EXTENT column from the CDB_ROLLBACK_SEGS view.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.10 Optsize
Optimal size of the rollback segment
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The OPTSIZE column from the V$ROLLSTAT view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.11 Pct Increase
Percent increase for extent size
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The PCT_INCREASE column from the CDB_ROLLBACK_SEGS view.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.12 Size
Size (in bytes) of the rollback segment.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The RSSIZE column from the V$ROLLSTAT view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.13 Shrinks
Number of times the size of a rollback segment decreases
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The SHRINKS column from the V$ROLLSTAT view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.14 Status
The status of the rollback segment (one of OFFLINE, ONLINE, NEEDS RECOVERY, PARTLY AVAILABLE, UNDEFINED).
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The STATUS column from the CDB_ROLLBACK_SEGS view.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.15 Tablespace Name
Name of the tablespace containing the rollback segment
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The TABLESPACE_NAME column from the CDB_ROLLBACK_SEGS view.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.6.16 Wraps
Number of times the rollback segment is wrapped
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The WRAPS column from the V$ROLLSTAT view
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.7 Segment Advisor Recommendations
Oracle uses the Automatic Segment Advisor job to detect segment issues regularly within maintenance windows. It determines whether the segments have unused space that can be released. The Number of recommendations is the number of segments that have Reclaimable Space. The recommendations come from all runs of the automatic segment advisor job and any user-scheduled segment advisor jobs.
9.7.1 Number of recommendations
Oracle uses the Automatic Segment Advisor job to detect segment issues regularly within maintenance windows. It determines whether the segments have unused space that can be released. The Number of recommendations is the number of segments that have Reclaimable Space. The recommendations come from all runs of the automatic segment advisor job and any user-scheduled segment advisor jobs.
This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 60 Minutes
9.8 Tablespaces
This section provides details on the tablespace metrics.
9.8.1 Tablespace Name
Name of the tablespace.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The TABLESPACE_NAME column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.2 Allocation Type
Type of extent allocation in effect for the tablespace (one of SYSTEM, UNIFORM, USER).
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The ALLOCATION_TYPE column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.3 Big File
Indicates whether the tablespace is a bigfile tablespace (YES) or a smallfile tablespace (NO).
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The BIGFILE column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.4 Block Size
Tablespace block size.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The BLOCK_SIZE column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.5 Type
One of UNDO, PERMANENT or TEMPORARY.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The CONTENTS column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.6 Extent Management
Indicates whether the extents in the tablespace are dictionary managed (DICTIONARY) or locally managed (LOCAL).
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The EXTENT_MANAGEMENT column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.7 Increment By
Default percent increase for extent size.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The PCT_INCREASE column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.8 Initial Ext Size
Default initial extent size.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The INITIAL_EXTENT column from CDB_TABLESPACES
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.9 Logging
Default logging (one of LOGGING, NOLOGGING).
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The LOGGING column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.10 Max Extents
Default maximum number of extents
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The MAX_EXTENTS column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.11 Minimum Extents
Default minimum number of extents.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The MIN_EXTENTS column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.12 Minimum Extent Size
Minimum extent size for this tablespace.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The MIN_EXTLEN column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.13 Next Extent
Default incremental extent size.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The NEXT_EXTENT column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.14 Segment Space Management
Indicates whether the free and used segment space in the tablespace is managed using free lists (MANUAL) or bitmaps (AUTO).
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The SEGMENT_SPACE_MANAGEMENT column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.15 Status
Tablespace status (one of ONLINE, OFFLINE, READ ONLY).
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The STATUS column from CDB_TABLESPACES.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.16 Size
Allocated size in bytes of the tablespace.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
Sum of BYTES column from CDB_DATA_FILES for permanent and undo tablespaces; sum of BYTES column from CDB_TEMP_FILES for temporary tablespaces.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.8.17 Used Size(B)
Size in bytes of the used space of the tablespace.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
Sum of BYTES column from CDB_DATA_FILES minus the sum of BYTES from CDB_FREE_SPACE for permanent and undo tablespaces; Sum of USED_BLOCKS FROM GV$SORT_SEGMENT times BLOCK_SIZE from CDB_TABLESPACES for temporary tablespaces.
User Action
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
9.9 Tablespace Allocation
The metrics in this metric category check the amount of space used and the amount of space allocated to each tablespace. The used space can then be compared to the allocated space to determine how much space is unused in the tablespace. This metric is intended for reporting, rather than alerts. Historical views of unused allocated free space can help DBAs to correctly size their tablespaces, eliminating wasted space.
9.9.1 Tablespace Allocated Space (MB)
The allocated space of a tablespace is the sum of the current size of its data files. A portion of this allocated space is used to store data while some may be free space. If segments are added to a tablespace, or if existing segments grow, they will use the allocated free space. The allocated free space is only available to segments within the tablespace. If, over time, the segments within a tablespace are not using this free space, the allocated free space is not being used.
This metric calculates the space allocated for each tablespace. It is not intended to generate alerts. Rather it should be used in conjunction with the Allocated Space Used (MB) metric to produce a historical view of the amount of space being used and unused by each tablespace.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
Tablespace Allocated Space (MB) is calculated by looping though the tablespace?s data files and totalling the size of the data files.
9.9.2 Tablespace Used Space (MB)
This metric calculates the space used for each tablespace. It is not intended to generate alerts. Rather it should be used in conjunction with the Tablespace Allocated Space (MB) metric to produce a historical view of the amount of space being used and unused by each tablespace.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
Tablespace Used Space (MB) is Tablespace Allocated Space (MB)? Tablespace Allocated Free Space (MB) where:
Tablespace Allocated Space (MB) is calculated by looping through the tablespace?s data files and totaling the size of the data files.
Tablespace Allocated Free Space (MB) is calculated by looping through the tablespace?s data files and totaling the size of the free space in each data file.
9.10 Temporary File Status
The following section describes the temporary file status metrics.
9.10.1 Temporary File Id
The absolute file number of the temporary file, used to join with other database tables and views to retrieve additional information.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 15 Minutes
Data Source
The FILE# column of the V$TEMPFILE view.
User Action
This information is purely Informative.
9.10.2 File Name
The name of the temporary file.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 15 Minutes
Data Source
The NAME column of the V$TEMPFILE view.
User Action
This information is purely Informative.
9.10.3 Status
The status of the temporary file, either ONLINE or OFFLINE.
Metric Summary for Database Control and Cloud Control
The following table shows how often the metric‘s value is collected and compared against the default thresholds. The ‘Consecutive Number of Occurrences Preceding Notification‘ column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 15 Minutes After Every Sample MATCH OFFLINE Not Defined 1 The temporary file %NAME% in pluggable database %pdbName% is %STATUS%..
Data Source
The STATUS column of the V$TEMPFILE view.
User Action
If the default settings are still in use, an offline temporary file will generate an incident (alert). User action is to determine whether this file is expected to be offline and if not, to switch it back online. Also, if this file is expected to be offline, the user should insure that the temporary tablespace it belongs to has other available online temporary files.
9.11 Tablespaces Full
The metrics in this metric category check for the amount of space used by each tablespace. The used space is then compared to the available free space to determine tablespace fullness. The available free space accounts for the maximum data file size as well as available disk space. This means that a tablespace will not be flagged as full if data files can extend and there is enough disk space available for them to extend.
9.11.1 Tablespace Free Space (MB)
As segments within a tablespace grow, the available free space decreases. If there is no longer any available free space, meaning data files reached their maximum size or there is no more disk space, then the creation of new segments or the extension of existing segments will fail.
This metric checks for the total available free space in each tablespace. This metric is intended for larger tablespaces, where the Available Space Used (%) metric is less meaningful. If the available free space falls below the size specified in the threshold arguments, then a warning or critical alert is generated.
If the version of the monitored database target is Oracle Database 10g Release 1 or later and the tablespace uses Local Extent Management, then the Oracle Database Server evaluates this metric internally every 10 minutes. Alternatively, if the version of the monitored Database target is Oracle 9i or earlier, or the tablespace uses Dictionary Extent Management, then the Oracle Management Agent tests the value of this metric every 30 minutes.
Data Source
MaximumSize? Total Used Space where:
TotalUsedSpace: Total used space in MB of tablespace
MaximumSize: Maximum size (in MB) of the tablespace. The maximum size is determined by looping through the tablespace?s data files, as well as additional free space on the disk that would be available for the tablespace should a data file autoextend.
User Action
Perform one of the following:
Increase the size of the tablespace by: Enabling automatic extension for one of its existing data files, manually resizing one of its existing data files, or adding a new data file.
If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.
Relocate segments to another tablespace, thereby increasing the free space in this tablespace.
Run the Segment Advisor on the tablespace.
9.11.2 Tablespace Space Used (%)
As segments within a tablespace grow, the available free space decreases. If there is no longer any available free space, meaning data files have reached their maximum size or there is no more disk space, then the creation of new segments or the extension of existing segments will fail.
This metric checks the Available Space Used (%) for each tablespace. If the percentage of used space is greater than the values specified in the threshold arguments, then a warning or critical alert is generated.
If the version of the monitored database target is Oracle Database 10g Release 1 or later and the tablespace uses Local Extent Management, then the Oracle Database Server evaluates this metric internally every 10 minutes. Alternatively, if the version of the monitored Database target is Oracle 9i or earlier, or the tablespace uses Dictionary Extent Management, then the Oracle Management Agent tests the value of this metric every 30 minutes.
Metric Summary for Database Control and Cloud Control
The following table shows how often the metric‘s value is collected and compared against the default thresholds. The ‘Consecutive Number of Occurrences Preceding Notification‘ column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 30 Minutes After Every Sample > 85 97 1 TTablespace [%name%] in pluggable database [%pdbName%] is [%value% percent] full.
Data Source
(TotalUsedSpace / MaximumSize) * 100 where:
TotalUsedSpace: total used space in MB of tablespace
MaximumSize: Maximum size (in MB) of the tablespace. The maximum size is determined by looping through the tablespace?s data files, as well as additional free space on the disk that would be available for the tablespace should a data file autoextend.
For additional information about the data source, refer to the fullTbsp.pl Perl script located in the sysman/admin/scripts directory.
User Action
Perform one of the following:
Increase the size of the tablespace by: Enabling automatic extension for one of its existing data files, manually resizing one of its existing data files, or adding a new data file.
If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.
Relocate segments to another tablespace, thus increasing the free space in this tablespace.
Run the Segment Advisor on the tablespace.
9.12 Tablespaces Full (dictionary managed)
The metrics in this metric category check for the amount of space used by each tablespace. The used space is then compared to the available free space to determine tablespace fullness. The available free space accounts for the maximum data file size as well as available disk space. This means that a tablespace will not be flagged as full if data files can extend, and there is enough disk space available for them to extend.
9.12.1 Tablespace Free Space (MB) (dictionary managed)
As segments within a tablespace grow, the available free space decreases. If there is no longer any available free space, meaning data files have reached their maximum size or there is no more disk space, then the creation of new segments or the extension of existing segments will fail.
This metric checks for the total available free space in each tablespace. This metric is intended for larger tablespaces, where the Available Space Used (%) metric is less meaningful. If the available free space falls below the size specified in the threshold arguments, then a warning or critical alert is generated.
If the version of the monitored database target is Oracle Database 10g Release 1 or later and the tablespace uses Local Extent Management, then the Oracle Database Server evaluates this metric internally every 10 minutes. Alternatively, if the version of the monitored Database target is Oracle 9i or earlier, or the tablespace uses Dictionary Extent Management, then the Oracle Management Agent tests the value of this metric every 30 minutes.
Data Source
MaximumSize? Total Used Space where:
TotalUsedSpace: Total used space in MB of tablespace
MaximumSize: Maximum size (in MB) of the tablespace. The maximum size is determined by looping through the tablespace?s data files, as well as additional free space on the disk that would be available for the tablespace should a data file autoextend.
9.12.2 Tablespace Space Used (%) (dictionary managed)
As segments within a tablespace grow, the available free space decreases. If there is no longer any available free space, meaning data files have reached their maximum size or there is no more disk space, then the creation of new segments or the extension of existing segments will fail.
This metric checks the Available Space Used (%) for each tablespace. If the percentage of used space is greater than the values specified in the threshold arguments, then a warning or critical alert is generated.
If the version of the monitored database target is Oracle Database 10g Release 1 or later and the tablespace uses Local Extent Management, then the Oracle Database Server evaluates this metric internally every 10 minutes. Alternatively, if the version of the monitored Database target is Oracle 9i or earlier, or the tablespace uses Dictionary Extent Management, then the Oracle Management Agent tests the value of this metric every 30 minutes.
Metric Summary for Database Control and Cloud Control
The following table shows how often the metric‘s value is collected and compared against the default thresholds. The ‘Consecutive Number of Occurrences Preceding Notification‘ column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 30 Minutes After Every Sample > 85 97 1 TTablespace [%name%] in pluggable database [%pdbName%] is [%value% percent] full.
Data Source
(TotalUsedSpace / MaximumSize) * 100 where:
TotalUsedSpace: Total used space in MB of tablespace
MaximumSize: Maximum size (in MB) of the tablespace. The maximum size is determined by looping through the tablespace?s data files, as well as additional free space on the disk that would be available for the tablespace should a data file autoextend.
User Action
Perform one of the following:
Increase the size of the tablespace by: Enabling automatic extension for one of its existing data files, manually resizing one of its existing data files, or adding a new data file.
If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.
Relocate segments to another tablespace, thereby increasing the free space in this tablespace.
Run the Segment Advisor on the tablespace.
9.13 Tablespaces With Problem Segments
The metrics in this metric category check for the following:
The largest chunk-free space in the tablespace. If any table, index, cluster, or rollback segment within the tablespace cannot allocate one additional extent, then an alert is generated.
Whether any of the segments in the tablespace are approaching their maximum extents. If, for any segment, the maximum number of extents minus the number of existing extents is less than 2, an alert is generated.
Only the tablespaces with problem segments are returned as results.
9.13.1 Segments Not Able to Extend Count
This metric checks for segments that cannot allocate an additional extent. If the number of segments is greater than the values specified in the threshold arguments, a warning or critical alert is generated.
Metric Summary for Database Control and Cloud Control
The following table shows how often the metric‘s value is collected and compared against the default thresholds. The ‘Consecutive Number of Occurrences Preceding Notification‘ column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 24 Hours After Every Sample > 0 %value% segments in %name% tablespace in pluggable database %pdbName% unable to extend.
Data Source
After checking for the largest chunk free space in the tablespace, this is the number of segments that cannot allocate an additional extent.
For additional information about the data source, refer to the problemTbsp.pl Perl script located in the sysman/admin/scripts directory.
User Action
Perform one of the following:
Increase the size of the tablespace by enabling automatic extension for one of its existing data files, manually resizing one of its existing data files, or adding a new data file.
If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.
Relocate segments to another tablespace, thereby increasing the free space in this tablespace.
9.13.2 Segments Not Able to Extend
This metric checks for segments that cannot allocate an additional extent.
This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The first 10 segment names that cannot allocate an additional extent in the tablespace.
User Action
Perform one of the following:
Increase the size of the tablespace by enabling automatic extension for one of its existing data files, manually resizing one of its existing data files, or adding a new data file.
If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.
9.13.3 Segments Approaching Maximum Extents Count
This metric checks for segments nearing the upper limit of the number of maximum extents. If the number of segments is greater than the values specified in the threshold arguments, a warning or critical alert is generated.
Metric Summary for Database Control and Cloud Control
The following table shows how often the metric‘s value is collected and compared against the default thresholds. The ‘Consecutive Number of Occurrences Preceding Notification‘ column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 24 Hours After Every Sample > 0 %value% segments in %name% tablespace pluggable database %pdbName% approaching max extents.
Data Source
Number of segments for which the maximum number of extents minus the number of existing extents is less than 2.
For additional information about the data source, refer to the problemTbsp.pl Perl script located in the sysman/admin/scripts directory.
User Action
If possible, increase the value of the segment?s MAXEXTENTS storage parameter. Otherwise, rebuild the segment with a larger extent size ensuring the extents within a segment are the same size by using a locally managed tablespace. For a dictionary managed tablespace, specify STORAGE parameters where NEXT=INITIAL and PCTINCREASE = 0.
9.13.4 Segments Approaching Maximum Extents
Segments nearing the upper limit of maximum extents. This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.
Metric Summary
The following table shows how often the metric‘s value is collected.
Target Version Collection Frequency
All Versions Every 24 Hours
Data Source
The first 10 segment names approaching their MaxExtent in the tablespace.
User Action
If possible, increase the value of the segment?s MAXEXTENTS storage parameter. Otherwise, rebuild the segment with a larger extent size ensuring the extents within a segment are the same size by specifying STORAGE parameters where NEXT=INITIAL and PCTINCREASE = 0.
For segments that are linearly scanned, choose an extent size that is a multiple of the number of blocks read during each multiblock read. This ensures that the Oracle multiblock read capability is used efficiently.