SAP Naming Conventions for Tablespaces and Data Files (SAP Library - SAP Database Guide: Oracle (BC-DB-ORA-DBA))

SAP Naming Conventions for Tablespaces and Data Files

Definition

In SAP Systems with the Oracle database, tablespaces and data files are named according to the conventions described in this section.

Use

You might need to create a new tablespace with SAPDBA, for example, in the following situations:

During the repository switch in a SAP system upgrade
When moving a table to a separate tablespace (for example, for administrative reasons)

For more information on extending a tablespace, see Extending a Tablespace.

Recommendation

We strongly recommend you to create new tablespaces and add data files to extend existing ones in accordance with the SAP naming conventions (see "Structure" below).

Monitoring Tablespaces

Monitor the following tablespaces with special care:

Certain 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 SAP System:

PSAPSTABD/I

PSAPCLUD/I

PSAPBTABD/I

PSAPPOOLD/I

PSAPPROTD/I

Certain tablespaces contain a large number of tables, which means that the number of extents for each tablespace is very high. You might experience problems with Oracle when you reorganize special tablespaces.

PSAPSTABD/I

PSAPBTABD/I

PSAPPOOLD/I

The SAP software compresses a large portion of its tables in order to save disk space. Therefore, when you export data, there is no point in compressing the tablespaces that contain the tables listed below. SAP's compressed tables are held primarily in the following tablespaces:

PSAPCLUD/I

PSAPDOCUD/I

PSAPPOOLD/I

PSAPSOURCED/I or PSAPES<release-number>D/I

PSAPLOADD/I or PSAPEL<release-number>D/I

Structure

Tablespaces

The following syntax is used for naming tablespaces (TSP):

PSAP<name>D for data tablespaces
PSAP<name>I for index tablespaces
PSAP<TSP>I (if it is not important to differentiate)

The 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
Oracle tablespaces	These tablespaces are required for operation of the Oracle DBMS, and contain no SAP data.
SYSTEM	Oracle DDIC
PSAPROLL	Rollback segments
PSAPTEMP	Sort processes
Basis tablespaces
PSAPEL300D/I	Development environment loads
PSAPES300D/I	Development environment sources
PSAPLOADD/I	Screen and report loads (ABAP)
PSAPSOURCED/I	Screen and report sources (ABAP)
PSAPDDICD/I	ABAP Dictionary
PSAPPROTD/I	Log-like tables (such as spool)
Application
PSAPCLUD/I	Cluster tables
PSAPPOOLD/I	Pooled tables (such as ATAB)
PSAPSTABD/I	Master data, transparent tables
PSAPBTABD/I	Transaction data, transparent tables
PSAPDOCUD/I	Doc., Sapscript, Sapfind
Customers
PSAPUSER1D/I	Customer tables

Data Files

When you add a new data file to extend a tablespace, SAPDBA attempts to add a new file to the standard SAP directory in which the most recent data file of the tablespace was stored. The most recent file is the one with the highest file number.

The naming conventions are as follows:

Directory: <ORACLE_HOME>/sapdata<n>/<tablespace name>_<file number>

File name: <tablespace name>.data<file number>

For more information on <ORACLE_HOME> , see:

Environment Variables (UNIX)

Environment Variables (Windows NT)

<n> is the sequentially assigned number of the SAP directory in which the data file will be stored.

<file number> is the sequentially assigned number of the data file in the tablespace. The same number also appears in the subdirectory that is created for each new file in a tablespace.