Checking Tablespaces 
Checking Tablespaces
You should check whether a tablespace needs to be extended, and distinguish between two cases:
If the tablespace has sufficient free storage space, it is probably a fragmentation of free storage space which causes the storage problems. This will occur only if DROP operations are performed frequently. Database objects that are frequently deleted (dropped) and created anew should be separated.
You can solve the storage problems by reorganizing the fragmented tablespace or the fragmented tables and indexes which it contains. An extension of the tablespace would then not be necessary.
A reorganization is time-consuming and complicated, however. SAP therefore recommends that you extend the tablespace rather than reorganizing it. You should reorganize this tablespace only if one or more of the following conditions apply:
See
A full tablespace must always be extended.
If an extension of a tablespace causes your database to approach the limit value determined by the operating system for the number of files, it can be useful to reorganize this tablespace after an extension or to extend the tablespace during the reorganization. However, a reorganization is not very likely necessary because the limit value for the data files is very high (at least 254 files are available).