SAP Naming Conventions for Tablespaces and Data Files

Tablespace Naming Convention as of SAP Web Application Server 6.10

The following table contains an overview of all the tablespaces in an SAP system and how they are used:

Tablespace Name	Use
SYSTEM	Oracle system tablespace
SYSAUX	Oracle auxiliary system tablespace
PSAPTEMP	Temporary obejcts (system default temporary tablespace)
PSAPTEMP<name>	Additional temporary objects, if required. Example: PSAPTEMP2.
PSAPUNDO	Undo tablespace (used from Oracle 9i instead of PSAPROLL)
PSAP<SID>	All objects of the SAP component <SID>. Example: PSAPC11.
PSAP<SID>ES<rel>[X] or PSAP<SID>EL<rel>[X]	Exchange tablespace for component <SID> upgrade. Example:PSAPC11ES640.
PSAP<SID>USR	Customer-specific objects for component <SID>. Example:PSAPC11USR.
PSAP<SID><name>	Additional customer-specific objects for component <SID>. Example: PSAPC11DAT.

The association of objects to PSAP<SID>, PSAP<SID>USR, or PSAP<SID><name> is controlled using the TABART in DD09L, TAORA, and IAORA. Exchange tablespaces have no TABART.

Tablespace Naming Convention Before SAP Web Application Server 6.10

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

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

The following table contains an overview of all the tablespaces in an SAP system and how they are used:

Tablespace name	Use
Oracle Tablespaces	These tablespaces are required for operation of the Oracle DBMS, and contain no SAP data.
SYSTEM	Oracle system tablespace
SYSAUX	Oracle auxiliary system tablespace
PSAPROLL	Rollback segments
PSAPTEMP	Sort processes
SAP Netweaver Tablespaces
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)
PSAPEL46D/I	Exchange tablespace loads
PSAPES46DD/I	Exchange tablespace sources
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, BRSPACE 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 relative file number.

The naming conventions are as follows:

·        Directory: <SAPDATA_HOME>/sapdata<n>/<tablespace suffix>_<file number>

·        File: <tablespace suffix>.data<file number>

<tablespace suffix> is the second half of the tablespace name, for example, UNDO for the tablespace PSAPUNDO.

<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.

For example, the first data file for PSAPUNDO is called:

·        Directory: <SAPDATA_HOME>/sapdata<n>/undo_1

·        File: undo.data1