In a production system you should check for full tablespaces on a regular basis in order to recognize storage problems early and avoid them. In particular, you should check whether there is sufficient space in all tablespaces before transmitting mass data (after system installation or release upgrade, for example).
If you find that the tablespaces are full, you should extend them. Additional storage space is then available. In exceptional situations, it may make sense to reorganize the tablespaces concerned.
To check tablespaces do the following:
Alternatively, use transaction code DB02.
The values in the Used column tell you which tablespaces are almost full.
You can estimate the degree of fragmentation from the ratio of the values under Tab/Ind and Extents.
See also: Monitoring Table and Index Fragmentation (Oracle)
To display tablespace information in graphical format:
From the Memory Management: Tablespaces screen, choose Graphics by columns.
The following information is displayed:
To display an overview of the storage parameters of the tablespaces:
From the Memory Management: Tablespaces screen, choose Storage parameter to display the storage parameters of the individual tablespaces.You can also display the storage parameters of the individual objects of a tablespace from the Memory Management: Tablespaces screen by clicking on the tablespace and performing a detailed analysis of the tables/indexes of this tablespace.
See also: Tablespace Analysis (Oracle)
Storage management problems can occur more frequently in some tablespaces than in others. You should always monitor these tablespaces closely, especially during data transfer after installation of your SAP system. To do this, you can use BR*Tools to show information about tablespaces.
See also:
Storage Management Errors (Oracle)
Checking for Freespace Problems (Oracle)
Checking Storage Parameters (Oracle)