Note 355771 - Oracle: Explanation of the new tablespace layout

Note Language: English Version: 32 Validity: Valid from 26.06.2006

Summary

Symptom

New technical and company requirements, for example, the requirement to

save several SAP systems in one database (MCOD), made a change of the
former tablespace layout necessary.

More Terms

Layout tablespace, tablespace concept

MCOD, Multiple Components One Database

Cause and Prerequisites

Reasons for implementing the new tablespace layout.

Solution

Prerequisites and support from SAP tools

Your system must meet the following requirements so you can use the new
tablespace layout:
1. The SAP kernel must be compatible with MCOD.
Releases as of SAP Basis Release 4.6C SR2 with SAP Kernel 4.6D fulfill
this requirement.
For more information, see http://service.sap.com/mcod/
2. Locally maintained tablespaces (LMTS)
Releases as of Oracle database Release 8i fulfill this prerequisite.

With SAP R/3 4.6C SR2 and EBP 2.0 / SAP CRM 2.0C SR1, the new tablespace
layout is optional (see Note 389132).

As of SAP Web Application Server Release 6.10 and above, it is a standard

setting. As of this release, the classic layout is no longer available
after a new installation or system copy.

For further questions and information regarding the support of the new
tablespace layout by SAP tools SAPINST/R3SETUP/R3UP , see Note
617444.
For questions regarding the function the schema ID, see Note 617444.
For questions regarding the conversion to the new tablespace concept using
BR*Tools, see Notes 646681 and 541538.

The classic tablespace layout

The classic tablespace layout contains the following tablespaces:

o SYSTEM - (Oracle Dictionary)

02.11.2007 Page 1 of 6
 Note 355771 - Oracle: Explanation of the new tablespace layout

o PSAPTEMP - (Standard tablespace for sort operations)

o PSAPROLL - (Standard tablespace for rollback segments)

o PSAPBTABD/I - (Standard tablespace for frequently changed data)

o PSAPSTABD/I - (Standard tablespace for rarely changed data)

o PSAPPOOLD/I - (Standard tablespace for SAP pool tables)

o PSAPPROTD/I - (Standard tablespace for log information)

o PSAPLOADD/I - (Standard tablespace for SAP loads (executables))

o PSAPSOURCED/I - (Standard tablespace for SAP sources (ABAP))

o PSAPDOCUD/I - (Standard tablespace for documentation tables)

o PSAPCLUD/I - (Standard tablespace for SAP cluster data)

o PSAPDDICD/I - (Standard tablespace for the SAP data dictionary)

o PSAPUSER1D/I - (Standard tablespace for data customers)

o PSAPEL<REL>D/I - (Standard tablespace for release load programs)

o PSAPES<REL>D/I - (Standard tablespace for release source programs)

Advantages of the classic tablespace concept

o Logical division of data according to its purpose (system data,

metadata, transaction data ...)

o Distribution across several physical disk drives and the related

influence on the I/O rate and I/O tuningoptions

o Smaller reorganizational units: Depending on the system

requirements and the size of the system, it was still possible or
necessary to create additional tablespaces (mostly for large or
heavily used tables whose access represented a bottleneck with
regard to the I/O load).

The new tablespace layout

The new tablespace layout contains the following tablespaces:

o SYSTEM (tablespace for the Oracle dictionary)

o SYSAUX (additional tablespace as of Oracle database 10g)

o PSAPTEMP (default tablespace for database sort operations)

o PSAPUNDO/PSAPROLL (default tablespace for segment undo/rollback)

o PSAP<SCHEMA_ID> (default tablespace for all SAP objects of the ABAP

02.11.2007 Page 2 of 6
 Note 355771 - Oracle: Explanation of the new tablespace layout

stack)

o PSAP<SCHEMA_ID>DB (default tablespace for all SAP objects of the

Java stack)

o PSAP<SCHEMA_ID>USR (default tablespace for all customer objects)

o PSAP<SCHEMA_ID><REL> (default tablespace for release-dependent

data)

o PSAP<SCHEMA_ID<NAME> (Additional tablespace for example, for large

tables)

Advantages of the new tablespace concept

o Advances in the hard disk and memory technology

o Advances in the Oracle technology: As of Oracle8i, locally

managed tablespaces (LMTS) allow efficient management of segments
(tables and indexes) of varying sizes and different growth phases
in a single tablespace.

o Simplified Oracle database administration: A reduction in the

number of tablespaces reduces the administrative effort involved ->
simpler tablespace layout

o On smaller SAP Systems (demo/test/small customer systems) with a

relatively low workload, you can also maintain the new tablespace
concept during production operation, which means that you can take
full advantage of the low level of administration required due to
the lower number of tablespaces.

o The application-specific assignment between an SAP-application

table and a Oracle tablespace is less clearly defined with every
new SAP release. Therefore, this argument for the logical division
of tablespaces became less important and does not always have to be
taken into account.

o Fine-tuning at tablespace level: Fine-tuning at tablespace level:

As of a particular system size or I/O load, we recommend that you
page out large or frequently used tables and indexes to seperate
tablespaces. As a result, the I/O is distributed across several
disks and you achieve higher performance and greater throughput.
This applies equally to the old and the new tablespace layout.
However, the distribution of I/O is generally no longer an issue,
thanks to advances in disk technology and storage systems. If you,
for example, use a large EMC storage as back-end storage (with the
latest HA technology), you can no longer allocate data to separate
tablespaces and therefore to separate physical disks to improve
performance by distributing the I/O, because this storage system
does not allow management and activation of individual disks. If
you are using this technology, there is therefore no need to
allocate tables (data) and indexes (index data) to separate
tablespaces.

02.11.2007 Page 3 of 6
 Note 355771 - Oracle: Explanation of the new tablespace layout

o Multiple Components in One Database (MCOD): For MCOD systems for

which the data of several SAP systems is stored in a single Oracle
database, the new concept helps to retain the overview of the
tablespaces. Each SAP system in a MCOD database has its own data
tablespaces.

Consequences of using the new tablespace layout

o A tablespace backup is now practically the same as a full database

backup, which means that the same detailed allocation of individual
tablespaces is no longer possible for online backups. You should
therefore check and, if necessary, adjust backup strategies that
are based on several tablespace backups (for example, incremental
backups using RMAN).

o Recommended: Tablespaces that are also created should comply with

the 'PSAP<SCHEMA_ID><NAME>' naming convention so that the
tablespace relationship to a database schema can already be
recognized by the tablespace name.

Additional recommendations for the new tablespace layout

The recommendation to page out large or frequently used segments singally

into seperate tablespaces is valid whether you use a system with the
classic or with the new tablespace layout.

Paging out segments to seperate tablespaces has the following advantages:

o Option of a detailed performance analysis on table or index level

o Tablespace reorganization (for exampe after archiving) requires

less time and effort:
When you archive data, free space is created in a tablespace.
However, the size of a tablespace initially remains the same. By
reorganizing a tablespace, the size of the tablespace can be
decreased. The space that is freed by this process is then
available to the filesystem. The smaller the tablespace that you
want the reorganize and the smaller the number of objects in the
tablespace, the less time and effort is required for the
reorganization.

Name additional tablespaces in accordance with the name convention

mentioned above: PSAP<SCHEMA_ID><NAME>
In this way, the tablespace relationship to a database schema can be
recognized more easily.

The earlier you determine the tablespace layout and the earlier you
determine which segments are to be paged out into seperate tablespaces, the
less time and effort is required to convert the tablespace layout.

Change to the new tablespace layout in the database

You can use BR*Tools (see Notes 646681, 541538) to convert SAP
installations with the classic tablespace layout and the database schema
'SAPR3' to the new layout if all SAP requirements (see above) are met. As
a result of this conversion, the 'SAPR3' SAP database schema remains

02.11.2007 Page 4 of 6
 Note 355771 - Oracle: Explanation of the new tablespace layout

unchanged. SAP proposes 'SR3' as Schema_ID. The result after the change
then appears as follows:

Schema ID = 'SR3'
Schema = 'SAPR3'
Tablespace names:
SYSTEM - (Oracle tablespace)
PSAPTEMP - (Oracle tablespace)
PSAPUNDO/PSAPROLL - (Oracle tablespace)
PSAPSR3 - (standard tablespace for ABAP stack SAP objects)
PSAPSR3DB - (standard tablespace for JAVA stack SAP objects)
PSAPSR3USR - (standard tablespace for customer objects)
PSAPSR3<REL> - (standard tablespace for releaseabh. objects)
PSAPSR3<NAME> - (additional non standard tablespace(s)
for SAP objects of customer objects)

Header Data
Release Status: Released for Customer
Released on: 26.06.2006 13:32:14
Priority: Recommendations/additional info
Category: Installation information

Main Component BC-DB-ORA Oracle

Additional Components:
BC-DB-ORA-DBA Database Administration with Oracle

The note is not release-dependent.

Related Notes
Number Short Text
646681 Reorganizing tables with BRSPACE
617444 Separate SCHEMA ID for database schema and tablespace name
548016 Conversion to Unicode
541538 FAQ: Reorganizations
502989 SAPinst: Missing BW tablespaces

Attributes

02.11.2007 Page 5 of 6
 Note 355771 - Oracle: Explanation of the new tablespace layout

Attribute Value
Database system ORACLE
weitere Komponenten BC-DB-ORA-DBA

02.11.2007 Page 6 of 6