DBA_TABLESPACE_USAGE_METRICS Showing Wrong Tablespace Size and Usage in Multitenant Environment with Autoextend Enabled
(Doc ID 2972815.1)
Last updated on MAY 02, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterInformation in this document applies to any platform.
Symptoms
TABLESPACE_SIZE column from DBA_TABLESPACE_USAGE_METRICS or CDB_TABLESPACE_USAGE_METRICS views could show the current allocated space rather than the maximum datafile size for tablespaces with autoextend enabled datafiles. This could lead to the wrong calculations of the used space and used percentage. This specific scenario involved bigfile tablespaces with autoextend enabled and the confirmation that there was enough free space in the underlying storage to allocate the maximum size that the datafile can reach.
As per the Database Reference Manual the TABLESPACE_SIZE column is a derived value which takes into account if autoextend is enabled for datafile(s) within the tablespace and the underlying storage free space (ASM or FileSystem).
The maximum size of the tablespace, expressed as number of data blocks
If the tablespace contains any datafiles with autoextend enabled, then this column displays the maximum size to which the tablespace can grow. Underlying storage free space, such as Oracle ASM or file system storage, is also taken into account when computing this value.
For example:
If a tablespace has a current size of 5 GB, the combined maximum size of its datafiles is 32 GB, and its underlying storage has 20 GB of free space, then this column will have a value of approximately 25 GB.
If a tablespace has a current size of 10 GB, the combined maximum size its datafiles is 20 GB, and its underlying storage has 25 GB of free space, then this column will have a value of approximately 20 GB.
If the tablespace contains only datafiles with autoextend disabled, then this column displays the combined size of all datafiles in the tablespace.
It has been verified that the Database has been patched or is running a release which includes the fixes for the bugs listed in Doc ID 2749032.1
Changes
MAXSIZE attribute (MAX_PDB_STORAGE) was set at PDB level
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 |