Oracle® Enterprise Manager Oracle Database and Database-Related Metric Reference Manual 12c Release 1 (12.1.0.2.0) Part Number E25160-03 |
|
|
PDF · Mobi · ePub |
This section provides details on the Oracle Pluggable Database (PDB) metrics.
This section provides details on the datafile metrics.
Name of the database file or temporary file.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Name of the tablespace to which the file belongs
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Autoextensible indicator.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Creation size of the file (in bytes)
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Size of the file in bytes.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Number of tablespace blocks used as autoextension increment. Block size is contained in the BLOCK_SIZE column of the CDB_TABLESPACES view.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Maximum file size in bytes
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
The filesystem or the raw device used by this datafile or temporary file.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
Perl script utility to retrieve the full file path.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
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).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
This section provides details on database feature usage metrics.
Database identifier of the database being tracked
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The DBID column from the CDB_FEATURE_USAGE_STATISTICS view
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.
Name of the feature
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The NAME column from the CDB_FEATURE_USAGE_STATISTICS view
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.
Database version in which the feature was tracked
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The VERSION column from the CDB_FEATURE_USAGE_STATISTICS view
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.
Number of times the system has detected usage for the feature
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The DETECTED_USES column from the CDB_FEATURE_USAGE_STATISTICS view
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.
This column stores feature-specific usage data in character format.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The FEATURE_INFO column from the CDB_FEATURE_USAGE_STATISTICS view
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.
Number of times the system has woken up and checked for feature usage
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The TOTAL_SAMPLES column from the CDB_FEATURE_USAGE_STATISTICS view
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.
This column stores feature-specific usage data in number format.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The AUX_COUNT column from the CDB_FEATURE_USAGE_STATISTICS view
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.
Indicates whether usage was detected the last time the system checked (TRUE) or not (FALSE)
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The CURRENTLY_USED column from the CDB_FEATURE_USAGE_STATISTICS view
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.
First sample time the system detected usage of the feature
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The FIRST_USAGE_DATE column from the CDB_FEATURE_USAGE_STATISTICS view
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.
Amount of time (in seconds) between the last two usage sample times
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The LAST_SAMPLE_DATE column from the CDB_FEATURE_USAGE_STATISTICS view
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.
Amount of time (in hours) between the last two usage sample times
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The LAST_SAMPLE_PERIOD column from the CDB_FEATURE_USAGE_STATISTICS view
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.
Last sample time the system detected usage of the feature
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The LAST_USAGE_DATE column from the CDB_FEATURE_USAGE_STATISTICS view
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.
This metric category contains the metrics associated with invalid objects.
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. |
This metric category contains the metrics that represent the number of invalid objects in each schema.
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% |
For each metric index:
SELECT count(1)
View the status of the database objects in the schema identified by the Invalid Object Owner metric. Recompile objects as necessary.
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.
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%.. |
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.
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%. |
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.
This is a user-readable message, including any Ora-error, encountered during response evaluation.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
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.
This section describes the rollback metrics.
Name of the rollback segment
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The SEGMENT_NAME column from the CDB_ROLLBACK_SEGS view.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Current size of active extents, averaged over time.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The AVEACTIVE column from the V$ROLLSTAT view
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Average shrink size
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The AVESHRINK column from the V$ROLLSTAT view
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Number of extents in the rollback segment
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The EXTENTS column from the V$ROLLSTAT view
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
High watermark of the rollback segment size
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The HWMSIZE column from the V$ROLLSTAT view
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Initial extent size in bytes
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The INITIAL_EXTENT column from the CDB_ROLLBACK_SEGS view.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Maximum number of extents
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The MAX_EXTENTS column from the CDB_ROLLBACK_SEGS view.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Minimum number of extents
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The MIN_EXTENTS column from the CDB_ROLLBACK_SEGS view.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Secondary extent size in bytes
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The NEXT_EXTENT column from the CDB_ROLLBACK_SEGS view.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Optimal size of the rollback segment
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The OPTSIZE column from the V$ROLLSTAT view
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Percent increase for extent size
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The PCT_INCREASE column from the CDB_ROLLBACK_SEGS view.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Size (in bytes) of the rollback segment.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The RSSIZE column from the V$ROLLSTAT view
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Number of times the size of a rollback segment decreases
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The SHRINKS column from the V$ROLLSTAT view
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
The status of the rollback segment (one of OFFLINE, ONLINE, NEEDS RECOVERY, PARTLY AVAILABLE, UNDEFINED).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The STATUS column from the CDB_ROLLBACK_SEGS view.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Name of the tablespace containing the rollback segment
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The TABLESPACE_NAME column from the CDB_ROLLBACK_SEGS view.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Number of times the rollback segment is wrapped
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The WRAPS column from the V$ROLLSTAT view
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
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.
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.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 60 Minutes |
This section provides details on the tablespace metrics.
Name of the tablespace.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The TABLESPACE_NAME column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Type of extent allocation in effect for the tablespace (one of SYSTEM, UNIFORM, USER).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The ALLOCATION_TYPE column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Indicates whether the tablespace is a bigfile tablespace (YES) or a smallfile tablespace (NO).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The BIGFILE column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Tablespace block size.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The BLOCK_SIZE column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
One of UNDO, PERMANENT or TEMPORARY.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The CONTENTS column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Indicates whether the extents in the tablespace are dictionary managed (DICTIONARY) or locally managed (LOCAL).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The EXTENT_MANAGEMENT column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Default percent increase for extent size.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The PCT_INCREASE column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Default initial extent size.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The INITIAL_EXTENT column from CDB_TABLESPACES
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Default logging (one of LOGGING, NOLOGGING).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The LOGGING column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Default maximum number of extents
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The MAX_EXTENTS column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Default minimum number of extents.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The MIN_EXTENTS column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Minimum extent size for this tablespace.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The MIN_EXTLEN column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Default incremental extent size.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The NEXT_EXTENT column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Indicates whether the free and used segment space in the tablespace is managed using free lists (MANUAL) or bitmaps (AUTO).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The SEGMENT_SPACE_MANAGEMENT column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Tablespace status (one of ONLINE, OFFLINE, READ ONLY).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The STATUS column from CDB_TABLESPACES.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Allocated size in bytes of the tablespace.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
Sum of BYTES column from CDB_DATA_FILES for permanent and undo tablespaces; sum of BYTES column from CDB_TEMP_FILES for temporary tablespaces.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
Size in bytes of the used space of the tablespace.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
This is a configuration metric so this column is purely informative and collected to provide DBAs with information necessary to manage the current database.
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.
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.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
Tablespace Allocated Space (MB) is calculated by looping though the tablespace�s data files and totalling the size of the data files.
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.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
The following section describes the temporary file status metrics.
The absolute file number of the temporary file, used to join with other database tables and views to retrieve additional information.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The FILE# column of the V$TEMPFILE view.
This information is purely Informative.
The name of the temporary file.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The NAME column of the V$TEMPFILE view.
This information is purely Informative.
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%.. |
The STATUS column of the V$TEMPFILE view.
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.
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.
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.
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.
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.
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. |
(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.
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.
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.
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.
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.
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. |
(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.
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.
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.
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. |
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.
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.
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.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The first 10 segment names that cannot allocate an additional extent in the tablespace.
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.
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. |
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.
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.
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.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
The first 10 segment names approaching their MaxExtent in the tablespace.
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.