IBM V7.2 User Manual

Page 16

Overview of Standard SAP R/3 System Installation with DB2 UDB

Overview of standard SAP R/3 system installation with DB2 UDB

A SAP R/3 system is identified by a three character system identifier and a
two digit system number between 00 and 96.

The following information about the directory structure applies to a Central System
consisting of the SAP R/3 central instance and database instance installed on a
single host. We do not consider the installation of dialog instances on additional
systems. We will further assume that the transport host is installed on the same host
as the central instance.

The base directories required for the SAP R/3 central instance are /usr/sap for the
general SAP R/3 software, and /usr/sap/trans, which contains SAP R/3 software for
the transport of objects between SAP R/3 systems. The SAP R/3 software and
configuration files are installed in the directory /usr/sap/. The directory is
owned by the user adm, which belongs to the group sapsys. For each R/3
system there is one DB2 instance db2 that contains the SAP R/3 database
and an administration database ADM for managing backup images and
log files. The db2 directory is owned by the user db2, which belongs to
the group dbadm. dbadm is the SYSADM_GROUP of the DB2 instance.

This results in the following directory structure:

SAP software

/usr/sap

trans

DB2 instance

/db2/

db2/NODE0000
log_dir
log_archive
log_retrieve
sapdata1
sapdata2
sapdata3
sapdata4
sapdata5
sapdata6
sapdatat
sqllib

By default all the tablespaces are database-managed storage (DMS), except for the
temporary tablespace PSAPTEMP which is system-managed storage (SMS). If you
want to use the split mirror copy of the database to take a backup, you should create
PSAPTEMP as a DMS tablespace. With DB2 UDB V7.2, you cannot take backups
of split mirror database copies unless all the tablespaces are DMS.