IBM V7.2 - Manual (Page 29)

Configuring a Two Host System 23
chfs -a size=14000000 /db2/TS1/sapdata6
chfs -a size=14000000 /db2/TS1/sapdata7
chfs -a size=14000000 /db2/TS1/log_dir
chfs -a size=14000000 /db2/TS1/db2ts1/NODE0000
Mount the file systems:
mount /usr/sap
mount /db2/TS1/db2ts1/NODE0000
mount /db2/TS1/sapdata1
mount /db2/TS1/sapdata2
mount /db2/TS1/sapdata3
mount /db2/TS1/sapdata4
mount /db2/TS1/sapdata5
mount /db2/TS1/sapdata6
mount /db2/TS1/sapdata7
mount /db2/TS1/log_dir
Change ownership of the file systems to the SAP administrative user and DB2 instance
owner respectively (users ts1adm in group sapsys and user db2ts1 and group
dbts1adm in this example):
chown ts1adm:sapsys /usr/sap
chown db2ts1:dbts1adm /db2/TS1/sapdata1
chown db2ts1:dbts1adm /db2/TS1/sapdata2
chown db2ts1:dbts1adm /db2/TS1/sapdata3
chown db2ts1:dbts1adm /db2/TS1/sapdata4
chown db2ts1:dbts1adm /db2/TS1/sapdata5
chown db2ts1:dbts1adm /db2/TS1/sapdata6
chown db2ts1:dbts1adm /db2/TS1/sapdata7
chown db2ts1:dbts1adm /db2/TS1/log_dir
6. Install DB2 on both the Primary and Backup server if this is not already done.
Further information on installing DB2 can be found in the DB2 UDB
documentation.
7. Install the SAP R/3 system as Central Instance (database server and SAP
application server on the same system) on the Primary server from the SAP CDs
as described in the SAP installation guide with the R3Setup program. Name the
SAP system TS1 and use 00 as system number. Before running R3Setup modify
the file DBSIZE.TPL in the installation directory as follows: replace
PSAPTEMP=0;0;32;4;@Z_SAPDATAPATH=SAPDATAT@
with
PSAPTEMP=1800;1;8;4;@Z_SAPDATAPATH=SAPDATA7@
This change will cause the temporary tablespace PSAPTEMP to be created as a
DMS tablespace with one container in
/db2/TS1/sapdata7 . By default, an
SMS tablespace is created.
The R3Setup program will create the DB2 instance db2ts1 and the database
TS1. It will also update the database configuration to set the log path to