Contents
1 Support 3
2 Preparation 3
2.1 ServicePacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 More memory than 4GB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3 Required packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.4 SAP required TCP/IP port numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.5 Swap partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.6 SuSE SAP-init package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1 Support
You can get software support for running SAP on SuSE Linux:
2 Preparation
2.1 ServicePacks
It is recommended to install available Service-Packs promptly.
NOTE: Not every kernel or glibc available via a SuSE Service-Pack is approved by SAP.
Please check the SuSE website 3 for packages officially approved by SAP. The list includes links to the latest
certified kernel and glibc versions.
After succesful registration on the SuSE maintenance web 4 , you can request to be mailed the password from
our support website5 .
Depending on your setup, you may require multiple swap partitions. Keep in mind that the Linux kernel
allows only 8 swap partitions of up to 2GB each. (R3SETUP will inform you about the required size).
The package suse-sapinit contains a runlevel script for starting and stopping R/3 including the database
and sets some system-parameters to recommended values. E.g. by changing the files /etc/sysctl.conf,
/etc/sysconfig/kernel and /etc/sysconfig/sapr3. To start an instance with SAPSID LNX, you
would add the following lines:
#/etc/sysconfig/sapr3
SAPCONFIG="_1"
SAP_SAPSID_1="LNX"
rcsapr3 start
rcsapr3 stop
If automatic control of starting R/3 is desired, you have to activate the service by insserv /etc/init.d/sapr3
or the YaST2-runlevel-editor. If you do that the SAP system will be started automatically by starting runlevel
3 or 5.
• Version
The database software has to be SAP DB release 7.3.0, at least build 28. You will need to order the
appropriate CD separately. During the installation you should edit the R3SETUP command file, which
you intend to use (usually: DATABASE.R3S). Search for this file in the installation directory and ex-
change the CD label string SAPDB:7205000:RDBMS: with the content of the file LABEL.ASC from
your current SAP DB CD (release 7.3.0, at least build 28).
• installation with SAPINST
The database software has to be SAP DB release 7.3.0, at least build 28. Probably you need to order the
appropriate CD separately. During the installation SAPINST will query for the RDBMS CD; here you
should enter the path to the current SAP DB CD (release 7.3.0, at least build 28).
• SAP Notes
Please also refere to the available SAP notes, e.g. 387075, 171356.
8 http://sdb.suse.de/cgi-bin/sdbsearch_en.cgi?stichwort=sapdb
• Version
For SAP Release <= 4.6 install DB2 Version V7, if you want to use Version V8 then you have to make an
DB-Upgrade from V7 to V8. Since SAP Release 4.7 you can user both V7 or V8.
• SAP Notes
Please refere to the available SAP notes.
• Version
The following Oracle versions are affected (under SLES 8):
1. Oracle 8.1.7
2. Oracle 9.x
• SAP Note
Please notice the SAP notes 575308 (Oracle 8.1.7), 557255 (Oracle 9.2) and 580772 (Oracle 9.2).
• Oracle Installation
1. Oracle8.1.7
The following are required for a new installation:
Installation 8.1.7
Notice: If your Oracle version is older than 8.1.7 then you must first apply BugFix 1467074 prior
to continuing with the installation; with the 8.1.7.4 installation you must reapply this BugFix.
• Version
The database software has to be Informix release 9.30. For installing an SAP release <= 4.6, you need
to order the appropriate CD separately, e.g for SAP R/3 Enterprise. During the installation you should
edit the R3SETUP command file, which you intend to use (mostly: DATABASE.R3S). Search for this file
in the installation directory and exchange the CD label string with the content of the file LABEL.ASC
from your current informix CD.
• SAP Notes
Please also refere to the available SAP notes, e.g. 591280, 171356.
-------------------------snip-------------------------
# /../
# sample configuration to bind raw devices
# to block devices
#
# The format of this file is:
# raw<N>:<blockdev>
#
# example:
# ---------
# raw1:hdb1
#
# this means: bind /dev/raw1 to /dev/hdb1
#
# ...
raw1:hdb1
[...]
-------------------------snip-------------------------
Raw1 corresponds to the raw character device /dev/raw/raw1 and will be bound to the /dev/hdb1 block
device.
To ensure that at restart the raw character devices are bound, make runlevel link with ”insserv /etc/init.d/raw”
Commands:
rcraw status - shows the status of the raw character devices
rcraw start - binds the raw character devices using /etc/raw
At least you must set the correct permissions of the raw character devices:
chown sqdlnx:sapsys /dev/raw/raw1
replace sqdlnx with your correct db-admin.
11 http://sdb.suse.de/cgi-bin/sdbsearch_en.cgi?stichwort=informix
-------------------platin.ini---------------------
# @INCLUDE = http://sapguiconfig/platin.ini
LNX : conn=/H/sapr3.company.com/S/3200&expert=true
-------------------platin.ini---------------------
Where you will have to modify sapr3.company.com to match your application server’s hostnam e
and set 3200 to your service number.
The GUI is started with:
guilogon