This chapter provides information about the Pluggable Databases (PDB) metrics.
For each metric, it provides the following information:
Description
Metric table
The metric table can include some or all of the following: target version, default collection frequency, default warning threshold, default critical threshold, and alert text.
This metric category provides details on database feature usage metrics.
This column stores feature-specific usage data in number format.
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.
Indicates whether usage was detected the last time the system checked (TRUE) or not (FALSE)
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.
Database identifier of the database being tracked
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.
Number of times the system has detected usage for the feature
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.
This column stores feature-specific usage data in character format.
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.
Name of the feature
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.
First sample time the system detected usage of the feature
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.
Amount of time (in seconds) between the last two usage sample times
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.
Amount of time (in hours) between the last two usage sample times
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.
Last sample time the system detected usage of the feature
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.
Number of times the system has woken up and checked for feature usage
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.
Database version in which the feature was tracked
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.
This metric category provides details on the datafile metrics.
Autoextensible indicator.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
Data Source
The AUTOEXTENSIBLE column of the CDB_DATA_FILES view if a permanent datafile or 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.
Name of the database file or temporary file.
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.
Size of the file in bytes.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
Data Source
The BYTES column of the CDB_DATA_FILES view if a permanent datafile or 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.
Creation size of the file (in bytes)
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
Data Source
The CREATE_BYTES column of the V$DATAFILE view if a permanent datafile or 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.
Number of tablespace blocks used as autoextension increment. Block size is contained in the BLOCK_SIZE column of the CDB_TABLESPACES view.
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 or 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.
Maximum file size in bytes
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
Data Source
The MAXBYTES column of the CDB_DATA_FILES view if a permanent datafile or 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.
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).
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 or 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.
The filesystem or the raw device used by this datafile or temporary file.
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.
Name of the tablespace to which the file belongs
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
Data Source
The TABLESPACE column of the CDB_DATA_FILES view if a permanent datafile or 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.
The metrics in this category represent the health of database jobs registered through the DBMS_SCHEDULER interface.
The Oracle Server job queue is a database table that stores information about local jobs such as the PL/SQL call to execute for a job such as when to run a job. Database replication is also managed by using the Oracle job queue mechanism using jobs to push deferred transactions to remote master sites, to purge applied transactions from the deferred transaction queue or to refresh snapshot refresh groups.
A job can be broken in two ways:
Oracle failed to successfully execute the job after a specified number of attempts (defined in the job).
The job is explicitly marked as broken by using the procedure DBMS_JOB.BROKEN.
This metric checks for broken DBMS jobs. A critical alert is generated if the number of broken jobs exceeds the value specified by the threshold argument.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | 0 | Not Defined | %value% job(s) are broken. |
The Oracle Server job queue is a database table that stores information about local jobs such as the PL/SQL call to execute for a job such as when to run a job. Database replication is also managed by using the Oracle job queue mechanism using jobs to push deferred transactions to remote master sites, to purge applied transactions from the deferred transaction queue or to refresh snapshot refresh groups.
If a job returns an error while Oracle is attempting to execute it, the job fails. Oracle repeatedly tries to execute the job doubling the interval of each attempt. If the job fails after a specified number of times (specified in the job definition), Oracle automatically marks the job as broken and no longer tries to execute it.
This metric checks for failed DBMS jobs. An alert is generated if the number of failed job exceeds the value specified by the threshold argument.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | 0 | Not Defined | %value% job(s) have failed. |
The metrics in this category include the service CPU time and service response time.
This metric represents the average CPU time, in microseconds, for calls to a particular database service.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | CPU per call for service %keyValue% is %value% microseconds |
This metric represents the average elapsed time, in microseconds, for calls to a particular database service.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Elapsed time per call for service %keyValue% is %value% microseconds |
The metrics in this category check for the number of failed logins on the target database. This check is performed every interval specified by the collection frequency and returns the number of failed logins for the last 30 minutes. These metrics will only work for databases where the audit_trail initialization parameter is set to DB or XML and the session is being audited.
This metric checks for the number of failed logins on the target database. This check is performed every interval specified by the collection frequency and returns the number of failed logins for the last 30 minutes. This metric will only work for databases where the audit_trail initialization parameter is set to DB or XML and the session is being audited.
If the failed login count crosses the values specified in the threshold arguments, then a warning or critical alert is generated. Because it is important to know every time a significant number of failed logins occurs on a system, on every collection, this metric determines the number of failed login attempts in the last 30 minutes and overrides the current alert instead of a new alert. You can manually clear these alerts.They will not automatically cleared after the next collection.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 30 Minutes | 150 | 300 | Number of failed login attempts exceeds threshold value. |
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.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined* | %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.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | %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.
The metrics in this category monitor the age and state of the first (top of the queue) message for each buffered queue in the database except for the system queues. Queues that are in the schema of SYS, SYSTEM, DBSNMP, and SYSMAN are defined as system level queues.
This metric provides the average age (in seconds) of the messages in the buffered queue for all nonsystem queues in the database.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Average age of messages in %schema%.%queue_name% queue is %value% seconds. |
This metric displays the current number of overflow messages spilled to disk from the buffered queue.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Current number of overflow messages spilled to disk from the buffered queue %schema%.%queue_name% is %value% |
This metric gives the age (in seconds) of the first message in the buffered queue for all non-system queues in the database.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Age of first message in %schema%.%queue_name% buffered queue is %value% seconds. |
This metric gives the messages processed percentage per minute per buffered queue in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Messages processed for queue %schema%.%queue_name% is %value% percent. |
This metric gives the total number of messages processed per minute per buffered queue in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Total messages processed per minute in the last interval for queue %schema%.%queue_name% is %value% |
This metric gives the total number of messages received or enqueued into the buffered queue per minute in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Total messages processed per minute in the last interval for queue %schema%.%queue_name% is %value% |
This metric category monitors the messages for buffered queues per subscriber in the database.
This metric display's the average age of messages in the buffered queue per queue in seconds.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Average age of messages for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% seconds. |
This metric displays the age of the first message in the buffered queue per queue per subscriber in seconds.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Age of first message for subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% seconds. |
This metric gives the messages processed percentage for the buffered queue per subscriber. Messages processed percent is calculated as the percent of the total number messages processed or dequeued to the total number of messages received or enqueued.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Messages processed for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% percent. |
This metric gives the total number of messages processed per minute per buffered queue subscriber in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Messages processed per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value. |
This metric gives the total number of messages processed per minute per buffered queue subscriber in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Total messages processed per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% |
This metric gives the total number of messages received or enqueued into the queue per subscriber per minute in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Total messages received per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% |
The metrics in this category monitor the age and state of the first (top of the queue) message for each persistent queue in the database except for the system queues. Queues that are in the schema of SYS, SYSTEM, DBSNMP, and SYSMAN are defined as system level queues.
This metric displays the average age of messages in the persistent queue per queue in seconds.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Average age of messages in %schema%.%queue_name% queue is %value% seconds. |
This metric gives the age (in seconds) of the first message in the persistent queue for all non-system queues in the database.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Age of first message in %schema%.%queue_name% queue is %value% seconds. |
This metric provides the unique global database name.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
This metric gives the messages processed percentage for the persistent queue. Messages processed percent is calculated as the percent of the total number messages processed or dequeued to the total number of messages received or enqueued.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Messages processed for queue %schema%.%queue_name% is %value% percent. |
This metric gives the messages processed percentage per minute per persistent queue in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Messages processed per minute in the last interval for queue %schema%.%queue_name% is %value% |
This metric gives the total number of messages processed per minute per persistent queue in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Total messages processed per minute in the last interval for queue %schema%.%queue_name% is %value% |
This metric gives the total number of messages received or enqueued into the queue per minute in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Total messages received per minute in the last interval for queue %schema%.%queue_name% is %value% |
The metrics in this category monitor the age and state of the first (top of the queue) message for each persistent queue per queue subscriber in the database except for the system queues. Queues that are in the schema of SYS, SYSTEM, DBSNMP, and SYSMAN are defined as system level queues.
This metric display's the average age of messages in the persistent queue per queue in seconds.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Average age of messages for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% seconds. |
This metric gives the age (in seconds) of the first message in the persistent queue per subscriber for all non-system queues in the database.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Age of first message for subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% seconds. |
This metric provides the unique global database name.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
This metric gives the messages processed percentage per minute per persistent queue subscriber in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Messages processed per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% |
This metric gives the messages processed percentage for the persistent queue per subscriber. Messages processed percent is calculated as the percent of the total number messages processed or dequeued to the total number of messages received or enqueued.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Messages processed for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% percent. |
This metric gives the messages processed percentage per minute per persistent queue subscriber in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Total messages processed per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value%. |
This metric gives the total number of messages received or enqueued into the queue per subscriber per minute in the last collection interval of the metric.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | Not Defined | Not Defined | Total messages received per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value%. |
This metric category 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.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 5 Minutes | MOUNTED | DOWN¦UNKNOWN* | 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.
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.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 5 Minutes | Not Defined | 0 | 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.
This is a user-readable message, including any Ora-error, encountered during response evaluation.
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.
This metric category provides the rollback metrics.
Name of the rollback segment
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.
Current size of active extents, averaged over time.
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.
Average shrink size
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.
Number of extents in the rollback segment
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.
High watermark of the rollback segment size
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.
Initial extent size in bytes
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.
Maximum number of extents
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.
Minimum number of extents
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.
Secondary extent size in bytes
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.
Optimal size of the rollback segment
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.
Percent increase for extent size
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.
Size (in bytes) of the rollback segment.
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.
Number of times the size of a rollback segment decreases
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.
The status of the rollback segment (one of OFFLINE, ONLINE, NEEDS RECOVERY, PARTLY AVAILABLE, UNDEFINED).
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.
Name of the tablespace containing the rollback segment
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.
Number of times the rollback segment is wrapped
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.
This metric category provides 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.
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.
Target Version | Collection Frequency |
---|---|
All Versions | Every 60 Minutes |
This metric category provides details on the tablespace metrics.
Type of extent allocation in effect for the tablespace (one of SYSTEM, UNIFORM, USER).
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.
Indicates whether the tablespace is a bigfile tablespace (YES) or a smallfile tablespace (NO).
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.
Tablespace block size.
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.
Indicates whether the extents in the tablespace are dictionary managed (DICTIONARY) or locally managed (LOCAL).
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.
Default percent increase for extent size.
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.
Default initial extent size.
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.
Default logging (one of LOGGING, NOLOGGING).
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.
Default maximum number of extents
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.
Minimum extent size for this tablespace.
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.
Default minimum number of extents.
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.
Default incremental extent size.
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.
Indicates whether the free and used segment space in the tablespace is managed using free lists (MANUAL) or bitmaps (AUTO).
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.
Allocated size in bytes of the tablespace.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
Data Source
Sum of BYTES column from CDB_DATA_FILES for permanent and undo tablespaces or the 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.
Tablespace status (one of ONLINE, OFFLINE, READ ONLY).
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.
Name of the tablespace.
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.
One of UNDO, PERMANENT or TEMPORARY.
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.
Size in bytes of the used space of the tablespace.
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 or the 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.
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.
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.
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.
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.
The allocated space of a tablespace is the sum of the current size of its datafiles. Some of this allocated space is used to store data and some of it 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, then the allocated free space is being wasted.
This metric calculates the space used for each tablespace. It is not intended to generate alerts. Use 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.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 30 Minutes | Not Defined | Not Defined | Tablespace [%name%] only has [%value% megabytes] free space |
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.
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.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 30 Minutes | 85 | 97 | Tablespace [%name%] 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.
The metrics in this category check for the amount of space used by each locally managed temporary tablespace. The used space is then compared to the available free space to determine tablespace fullness. The available free space takes into account 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 more free space available, that is, the data files have hit 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 temporary tablespace. This metric is intended for larger temporary 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.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 30 Minutes | Not Defined | Not Defined | Tablespace [%name%] has [%value% mbytes] free |
As segments within a tablespace grow, the available free space decreases. If there is no more free space available, that is, the data files have hit their maximum size or there is no more disk space, then the creation of new segments or the extension of existing segments will fail.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 30 Minutes | Not Defined | Not Defined | Tablespace [%name%] is [%value% percent] 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.
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.
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.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 30 Minutes | 85 | 97 | Tablespace [%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.
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 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.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | 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.
This metric reports segments which are nearing the upper limit of maximum extents.
Target Version | Collection Frequency |
---|---|
All Versions | Every 24 Hours |
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.
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.
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.
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.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 24 Hours | 0 | Not Defined | %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.
This metric category provides the temporary file status metrics.
The name of the temporary file.
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.
The status of the temporary file, either ONLINE or OFFLINE.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 15 Minutes | OFFLINE | Not Defined | 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). Determine whether this file is expected to be offline and if not, switch it back online. Also, if this file is expected to be offline, ensure that the temporary tablespace it belongs to has other available online temporary files.
The absolute file number of the temporary file, used to join with other database tables and views to retrieve additional information.
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.
The metrics in this category contain the metric that provides the number of database objects in a schema.
This metric displays the total number of database objects in a schema.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 15 Minutes | Not Defined | Not Defined | %value% object(s) exist in the %owner% schema. |
The metrics in this category contain the metric that provides the number of tables in a schema.
This metric displays the total number of tables in a schema.
Target Version | Evaluation and Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
---|---|---|---|---|
All Versions | Every 15 Minutes | Not Defined | Not Defined | %value% table(s) exist in the %owner% schema. |