Tablespaces and SAP Naming Conventions 
Use
You can use SAPDBA to create new tablespaces in accordance with the SAP naming conventions, for example during the repository switch in a system upgrade. For administrative reasons, you may have to move a table to a separate tablespace. To help orientation, this tablespace should conform to the SAP naming convention.
See
Prerequisites
The following syntax is used for naming tablespaces (TSP):
PSAP<name>D
for data tablespacesThe following table contains an overview of all the SAP tablespaces and how they are used. The sizes are not absolute values since they can change according to how much the tablespace is used. They are there to help you compare the tablespaces.
Tablespace name |
Use |
Approximate size in MB |
Oracle tablespaces |
These tablespaces are required for operation of the Oracle RDBMS, and contain no SAP data. |
|
SYSTEM |
Oracle DDIC |
150 |
PSAPROLL |
Rollback segments |
300 |
PSAPTEMP |
Sort processes |
64 |
Basis tablespaces |
||
PSAPEL300D/I |
Development environment loads |
309/11 |
PSAPES300D/I |
Development environment sources |
1573/503 |
PSAPLOADD/I |
Screen and report loads (ABAP) |
65/37 |
PSAPSOURCED/I |
Screen and report sources (ABAP) |
58/14 |
PSAPDDICD/I |
ABAP Dictionary |
46/26 |
PSAPPROTD/I |
Log-like tables (such as spool) |
97/13 |
Application |
||
PSAPCLUD/I |
Cluster tables |
110/14 |
PSAPPOOLD/I |
Pooled tables (such as ATAB) |
392/254 |
PSAPSTABD/I |
Master data, transparent tables |
496/318 |
PSAPBTABD/I |
Transaction data, transparent tables |
209/191 |
PSAPDOCUD/I |
Doc., Sapscript, Sapfind |
70/13 |
Customers |
||
PSAPUSER1D/I |
Customer tables |
5/5 |
Activities
Monitor some tablespaces with special care, for the following reasons:
1. Some tablespaces have memory management problems (extent overflow, tablespace overflow, freespace problems) more often than others. Monitor the following tablespaces carefully, particularly during the transfer of data when you install your R/3 System:
PSAPSTABD/I
PSAPCLUD/I
PSAPBTABD/I
PSAPPOOLD/I
PSAPPROTD/I
2. Some tablespaces contain a large number of tables, which means that the number of extents for each tablespace is very high. You may experience problems with Oracle when you
reorganize special tablespaces.PSAPSTABD/I
PSAPBTABD/I
PSAPPOOLD/I
3. The SAP software compresses a large portion of its tables in order to save disk space. It is, therefore, not useful to compress the tablespaces that contain these tables when you export data. SAP's compressed tables are held primarily in the following tablespaces:
PSAPCLUD/I
PSAPDOCUD/I
PSAPPOOLD/I
PSAPSOURCED/I or PSAPES300D/I
PSAPLOADD/I or PSAPEL300D/I