The DBA_TABLESPACE_USAGE_METRICS View Needs to be Rebuilt in 10g
(Doc ID 738101.1)
Last updated on JULY 25, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.2.0.4 [Release 10.1 to 10.2]Enterprise Manager for Oracle Database - Version 10.1.0.2 to 10.2.0.4 [Release 10.1 to 10.2]
Enterprise Manager Base Platform - Version 10.1.0.2 to 10.2.0.4 [Release 10.1 to 10.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
Enterprise Manager for RDBMS - Version: 10.1.0.2 to 10.2.0.4
Enterprise Manager Grid Control - Version: 10.1.0.2 to 10.2.0.4
RDBMS
EM
DBCONSOLE
GRID CONTROL
Symptoms
1) Attempts to use DBA_TABLESPACE_USAGE_METRICS have resulted in:
- Inconsistent or incorrect values for DBA_TABLESPACE_USAGE_METRICS when compared to other space metrics using scripts for DBA_DATA_FILES, DBA_TABLESPACES, DBA_FREE_SPACE ... etc.
- Incorrect, undersized or oversized values used by GC, EM or DBConsole for Tablespace metric ALERTs
2) Tablespaces can 'fill up' leading to potential database or application stoppage due to this improper metric assessment. The problem is that by surpassing the expected ALERT thresholds DBAs are not warned of the space utilitization problem.
Changes
No known changes are associated with the problem:
- The problem can be intermittent for a single tablespace
- The problem may occur for only one or a few of the total tablespaces measured or monitored by EM ( this is usually the case, making the problem more unexpected )
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |