10.

7 Installing SAP R/3

Contributed by Holger Kipp. Original version converted to SGML by Valentino Vaschetto. Installations of SAP Systems using FreeBSD will not be supported by the SAP support team -they only offer support for certified platforms.

10.7.1 Preface
This document describes a possible way of installing a SAP R/3 System with Oracle Database for Linux onto a FreeBSD machine, including the installation of FreeBSD and Oracle. Two different configurations will be described:

SAP R/3 4.6B (IDES) with Oracle 8.0.5 on FreeBSD 4.3-STABLE SAP R/3 4.6C with Oracle 8.1.7 on FreeBSD 4.5-STABLE

Even though this document tries to describe all important steps in a greater detail, it is not intended as a replacement for the Oracle andSAP R/3 installation guides. Please see the documentation that comes with the SAP R/3 Linux edition for SAP and Oracle specific questions, as well as resources from Oracle and SAP OSS.

10.7.2 Software
The following CD-ROMs have been used for SAP installations: 10.7.2.1 SAP R/3 4.6B, Oracle 8.0.5
Name KERNEL RDBMS EXPORT1 EXPORT2 EXPORT3 EXPORT4 EXPORT5 EXPORT6 Number 51009113 51007558 51010208 51010209 51010210 51010211 51010212 51010213 Description SAP Kernel Oracle / Installation / AIX, Linux, Solaris Oracle / RDBMS 8.0.5.X / Linux IDES / DB-Export / Disc 1 of 6 IDES / DB-Export / Disc 2 of 6 IDES / DB-Export / Disc 3 of 6 IDES / DB-Export / Disc 4 of 6 IDES / DB-Export / Disc 5 of 6 IDES / DB-Export / Disc 6 of 6

Additionally, we used the Oracle 8 Server (Pre-production version 8.0.5 for Linux, Kernel Version 2.0.33) CD which is not really necessary, and FreeBSD 4.3-STABLE (it was only a few days past 4.3 RELEASE). 10.7.2.2 SAP R/3 4.6C SR2, Oracle 8.1.7
Name KERNEL RDBMS EXPORT1 EXPORT1 EXPORT1 Number 51014004 51012930 51013953 51013953 51013953 Description SAP Kernel Oracle / SAP Kernel Version 4.6D / DEC, Linux Oracle 8.1.7/ RDBMS / Linux Release 4.6C SR2 / Export / Disc 1 of 4 Release 4.6C SR2 / Export / Disc 2 of 4 Release 4.6C SR2 / Export / Disc 3 of 4

Name EXPORT1 LANG1

Number 51013953 51013954

Description Release 4.6C SR2 / Export / Disc 4 of 4 Release 4.6C SR2 / Language / DE, EN, FR / Disc 1 of 3

Depending on the languages you would like to install, additional language CDs might be necessary. Here we are just using DE and EN, so the first language CD is the only one needed. As a little note, the numbers for all four EXPORT CDs are identical. All three language CDs also have the same number (this is different from the 4.6B IDES release CD numbering). At the time of writing this installation is running on FreeBSD 4.5STABLE (20.03.2002).

10.7.3 SAP Notes

The following notes should be read before installing SAP R/3 and proved to be useful during installation: 10.7.3.1 SAP R/3 4.6B, Oracle 8.0.5
Number 0171356 0201147 0373203 0072984 0130581 0144978 0162266 Title SAP Software on Linux: Essential Comments INST: 4.6C R/3 Inst. on UNIX - Oracle Update / Migration Oracle 8.0.5 --> 8.0.6/8.1.6 LINUX Release of Digital UNIX 4.0B for Oracle R3SETUP step DIPGNTAB terminates Your system has not been installed correctly Questions and tips for R3SETUP on Windows NT / W2K

10.7.3.2 SAP R/3 4.6C, Oracle 8.1.7

Number 0015023 0045619 0171356 0195603 0212876 0300900 0377187 0387074 0387077 0387078 Title Initializing table TCPDB (RSXP0004) (EBCDIC) R/3 with several languages or typefaces SAP Software on Linux: Essential Comments RedHat 6.1 Enterprise version: Known problems The new archiving tool SAPCAR Linux: Released DELL Hardware RedHat 6.2: important remarks INST: R/3 4.6C SR2 Installation on UNIX INST: R/3 4.6C SR2 Inst. on UNIX - Oracle SAP Software on UNIX: OS Dependencies 4.6C SR2

10.7.4 Hardware Requirements

The following equipment is sufficient for the installation of a SAP R/3 System. For production use, a more exact sizing is of course needed:
Component Processor Memory 4.6B 2 x 800MHz Pentium III 1GB ECC 4.6C 2 x 800MHz Pentium III 2GB ECC

Component Hard Disk Space

4.6B 50-60GB (IDES)

4.6C 50-60GB (IDES)

For use in production, Xeon Processors with large cache, high-speed disk access (SCSI, RAID hardware controller), USV and ECC-RAM is recommended. The large amount of hard disk space is due to the preconfigured IDES System, which creates 27 GB of database files during installation. This space is also sufficient for initial production systems and application data. 10.7.4.1 SAP R/3 4.6B, Oracle 8.0.5 The following off-the-shelf hardware was used: a dual processor board with 2 800 MHz Pentium III processors, Adaptec 29160 Ultra160 SCSI adapter (for accessing a 40/80 GB DLT tape drive and CDROM), Mylex AcceleRAID (2 channels, firmware 6.00-1-00 with 32 MB RAM). To the Mylex RAID controller are attached two 17 GB hard disks (mirrored) and four 36 GB hard disks (RAID level 5). 10.7.4.2 SAP R/3 4.6C, Oracle 8.1.7 For this installation a Dell PowerEdge 2500 was used: a dual processor board with two 1000 MHz Pentium III processors (256 kB Cache), 2 GB PC133 ECC SDRAM, PERC/3 DC PCI RAID Controller with 128 MB, and an EIDE DVD-ROM drive. To the RAID controller are attached two 18 GB hard disks (mirrored) and four 36 GB hard disks (RAID level 5).

10.7.5 Installation of FreeBSD

First you have to install FreeBSD. There are several ways to do this, for more information read the Section 2.13. 10.7.5.1 Disk Layout To keep it simple, the same disk layout both for the SAP R/3 46B and SAP R/3 46C SR2 installation was used. Only the device names changed, as the installations were on different hardware (/dev/da and /dev/amr respectively, so if using an AMI MegaRAID, one will see /dev/amr0s1a instead of /dev/da0s1a):
File system
/dev/da0s1a /dev/da0s1b /dev/da0s1e /dev/da0s1f /dev/da1s1e /dev/da1s1f /dev/da1s1g

Size 1 GB 6 GB 2 GB 8 GB 45 GB 2 GB 2 GB

Mounted on
/

swap
/var /usr /compat/linux/oracle /compat/linux/sapmnt /compat/linux/usr/sap

Configure and initialize the two logical drives with the Mylex or PERC/3 RAID software beforehand. The software can be started during the BIOS boot phase.

Please note that this disk layout differs slightly from the SAP recommendations, as SAP suggests mounting the Oracle subdirectories (and some others) separately -- we decided to just create them as real subdirectories for simplicity. 10.7.5.2 make
world

and a New Kernel

Download the latest -STABLE sources. Rebuild world and your custom kernel after configuring your kernel configuration file. Here you should also include the kernel parameters which are required for both SAP R/3 and Oracle.

10.7.6 Installing the Linux Environment

10.7.6.1 Installing the Linux Base System First the linux_base port needs to be installed (as root):
# cd /usr/ports/emulators/linux_base-fc4 # make install distclean

10.7.6.2 Installing Linux Development Environment The Linux development environment is needed, if you want to install Oracle on FreeBSD according to the Section 10.6:
# cd /usr/ports/devel/linux_devtools # make install distclean

The Linux development environment has only been installed for the SAP R/3 46B IDES installation. It is not needed, if the Oracle DB is not relinked on the FreeBSD system. This is the case if you are using the Oracle tarball from a Linux system. 10.7.6.3 Installing the Necessary RPMs To start the R3SETUP program, PAM support is needed. During the first SAP Installation on FreeBSD 4.3-STABLE we tried to install PAM with all the required packages and finally forced the installation of the PAM package, which worked. For SAP R/3 4.6C SR2 we directly forced the installation of the PAM RPM, which also works, so it seems the dependent packages are not needed:
# rpm -i --ignoreos --nodeps --root /compat/linux --dbpath /var/lib/rpm \ pam-0.68-7.i386.rpm

For Oracle 8.0.5 to run the intelligent agent, we also had to install the RedHat Tcl package tcl-8.0.5-30.i386.rpm (otherwise the relinking during Oracle installation will not work). There are some other issues regarding relinking of Oracle, but that is a Oracle Linux issue, not FreeBSD specific. 10.7.6.4 Some Additional Hints

It might also be a good idea to add linprocfs to /etc/fstab, for more information, see the linprocfs(5) manual page. Another parameter to set is kern.fallback_elf_brand=3 which is done in the file /etc/sysctl.conf.

10.7.7 Creating the SAP R/3 Environment

10.7.7.1 Creating the Necessary File Systems and Mountpoints For a simple installation, it is sufficient to create the following file systems:
mount point
/compat/linux/oracle /compat/linux/sapmnt /compat/linux/usr/sap

size in GB 45 GB 2 GB 2 GB

It is also necessary to created some links. Otherwise the SAP Installer will complain, as it is checking the created links:
# ln -s /compat/linux/oracle /oracle # ln -s /compat/linux/sapmnt /sapmnt # ln -s /compat/linux/usr/sap /usr/sap

Possible error message during installation (here with System PRD and the SAP R/3 4.6C SR2 installation):
INFO 2002-03-19 16:45:36 R3LINKS_IND_IND SyLinkCreate:200 Checking existence of symbolic link /usr/sap/PRD/SYS/exe/dbg to /sapmnt/PRD/exe. Creating if it does not exist...

WARNING 2002-03-19 16:45:36 R3LINKS_IND_IND SyLinkCreate:400 Link /usr/sap/PRD/SYS/exe/dbg exists but it points to file /compat/linux/sapmnt/PRD/exe instead of /sapmnt/PRD/exe. The program cannot go on as long as this link exists at this location. Move the link to another location.

ERROR 2002-03-19 16:45:36 R3LINKS_IND_IND Ins_SetupLinks:0 can not setup link '/usr/sap/PRD/SYS/exe/dbg' with content '/sapmnt/PRD/exe'

10.7.7.2 Creating Users and Directories

SAP R/3 needs two users and three groups. The user names depend on the SAP system ID (SID) which consists of three letters. Some of these SIDs are reserved by SAP (for example SAP and NIX. For a complete list please see the SAP documentation). For the

IDES installation we used IDS, for the 4.6C SR2 installation PRD, as that system is

intended for production use. We have therefore the following groups (group IDs might differ, these are just the values we used with our installation):
group ID 100 101 102 group name dba sapsys oper description Data Base Administrator SAP System Data Base Operator

For a default Oracle installation, only group dba is used. As oper group, one also uses group dba (see Oracle and SAP documentation for further information). We also need the following users:
user ID 1000 1002 user name idsadm/prdadm oraids/oraprd generic name sidadm orasid group sapsys dba additional groups oper oper description SAP Administrator Oracle Administrator

Adding the users with adduser(8) requires the following (please note shell and home directory) entries for SAP Administrator:
Name: sidadm Password: ****** Fullname: SAP Administrator SID Uid: 1000 Gid: 101 (sapsys) Class: Groups: sapsys dba HOME: /home/sidadm Shell: bash (/compat/linux/bin/bash)

and for Oracle Administrator:

Name: orasid Password: ****** Fullname: Oracle Administrator SID Uid: 1002 Gid: 100 (dba) Class: Groups: dba HOME: /oracle/sid Shell: bash (/compat/linux/bin/bash)

This should also include group oper in case you are using both groups dba and oper.

10.7.7.3 Creating Directories These directories are usually created as separate file systems. This depends entirely on your requirements. We choose to create them as simple directories, as they are all located on the same RAID 5 anyway: First we will set owners and rights of some directories (as user root):
# chmod 775 /oracle # chmod 777 /sapmnt # chown root:dba /oracle # chown sidadm:sapsys /compat/linux/usr/sap # chmod 775 /compat/linux/usr/sap

Second we will create directories as user orasid. These will all be subdirectories of /oracle/SID:
# su - orasid # cd /oracle/SID # mkdir mirrlogA mirrlogB origlogA origlogB # mkdir sapdata1 sapdata2 sapdata3 sapdata4 sapdata5 sapdata6 # mkdir saparch sapreorg # exit

For the Oracle 8.1.7 installation some additional directories are needed:
# su - orasid # cd /oracle # mkdir 805_32 # mkdir client stage # mkdir client/80x_32 # mkdir stage/817_32 # cd /oracle/SID # mkdir 817_32

Note: The directory client/80x_32 is used with exactly this name. Do not replace the x with some number or anything. In the third step we create directories as user sidadm:
# su - sidadm # cd /usr/sap # mkdir SID # mkdir trans # exit

10.7.7.4 Entries in /etc/services

SAP R/3 requires some entries in file /etc/services, which will not be set correctly

during installation under FreeBSD. Please add the following entries (you need at least those entries corresponding to the instance number -- in this case, 00. It will do no harm adding all entries from 00 to 99 for dp, gw, sp and ms). If you are going to use a SAProuter or need to access SAP OSS, you also need 99, as port 3299 is usually used for the SAProuter process on the target system:
sapdp00 sapgw00 sapsp00 sapms00 3200/tcp # SAP Dispatcher. 3300/tcp # SAP Gateway. 3400/tcp # 3500/tcp # 3200 + Instance-Number 3300 + Instance-Number 3400 + Instance-Number 3500 + Instance-Number 3600 + Instance-Number 4800 + Instance-Number

sapmsSID 3600/tcp # SAP Message Server. sapgw00s 4800/tcp # SAP Secure Gateway

10.7.7.5 Necessary Locales

SAP requires at least two locales that are not part of the default RedHat installation. SAP offers the required RPMs as download from their FTP server (which is

only accessible if you are a customer with OSS access). See note 0171356 for a list of RPMs you need. It is also possible to just create appropriate links (for example from de_DE and en_US ), but we would not recommend this for a production system (so far it worked with the IDES system without any problems, though). The following locales are needed:
de_DE.ISO-8859-1 en_US.ISO-8859-1

Create the links like this:

# cd /compat/linux/usr/share/locale # ln -s de_DE de_DE.ISO-8859-1 # ln -s en_US en_US.ISO-8859-1

If they are not present, there will be some problems during the installation. If these are then subsequently ignored (by setting the STATUS of the offending steps to OK in file CENTRDB.R3S), it will be impossible to log onto the SAP system without some additional effort. 10.7.7.6 Kernel Tuning
SAP R/3 systems need a lot of resources. We therefore added the following parameters to

the kernel configuration file:

# Set these for memory pigs (SAP and Oracle):

options MAXDSIZ="(1024*1024*1024)" options DFLDSIZ="(1024*1024*1024)" # System V options needed. options SYSVSHM #SYSV-style shared memory options SHMMAXPGS=262144 #max amount of shared mem. pages #options SHMMAXPGS=393216 #use this for the 46C inst.parameters options SHMMNI=256 #max number of shared memory ident if. options SHMSEG=100 #max shared mem.segs per process options SYSVMSG #SYSV-style message queues options MSGSEG=32767 #max num. of mes.segments in system options MSGSSZ=32 #size of msg-seg. MUST be power of 2 options MSGMNB=65535 #max char. per message queue options MSGTQL=2046 #max amount of msgs in system options SYSVSEM #SYSV-style semaphores options SEMMNU=256 #number of semaphore UNDO structures options SEMMNS=1024 #number of semaphores in system options SEMMNI=520 #number of semaphore identifiers options SEMUME=100 #number of UNDO keys

The minimum values are specified in the documentation that comes from SAP. As there is no description for Linux, see the HP-UX section (32-bit) for further information. As the system for the 4.6C SR2 installation has more main memory, the shared segments can be larger both for SAP and Oracle, therefore choose a larger number of shared memory pages. Note: With the default installation of FreeBSD on i386, leave MAXDSIZ and DFLDSIZ at 1 GB maximum. Otherwise, strange errors like ORA27102: out of memory and Linux Error: 12: Cannot allocate memory might happen.

10.7.8 Installing SAP R/3

10.7.8.1 Preparing SAP CDROMs There are many CDROMs to mount and unmount during the installation. Assuming you have enough CDROM drives, you can just mount them all. We decided to copy the CDROMs contents to corresponding directories:
/oracle/SID/sapreorg/cd-name

where cd-name was one of KERNEL, RDBMS, EXPORT1, EXPORT2, EXPORT3, EXPORT4, EXPORT5 and EXPORT6 for the 4.6B/IDES installation, and KERNEL, RDBMS, DISK1, DISK2, DISK3, DISK4 and LANG for the

4.6C SR2 installation. All the filenames on the mounted CDs should be in capital letters, otherwise use the -g option for mounting. So use the following commands:
# mount_cd9660 -g /dev/cd0a /mnt # cp -R /mnt/* /oracle/SID/sapreorg/cd-name # umount /mnt

10.7.8.2 Running the Installation Script First you have to prepare an install directory:
# cd /oracle/SID/sapreorg # mkdir install # cd install

Then the installation script is started, which will copy nearly all the relevant files into the install directory:
# /oracle/SID/sapreorg/KERNEL/UNIX/INSTTOOL.SH

The IDES installation (4.6B) comes with a fully customized SAP R/3 demonstration system, so there are six instead of just three EXPORT CDs. At this point the installation template CENTRDB.R3S is for installing a standard central instance (R/3 and database), not the IDES central instance, so one needs to copy the corresponding CENTRDB.R3S from the EXPORT1 directory, otherwise R3SETUP will only ask for three EXPORT CDs. The newer SAP 4.6C SR2 release comes with four EXPORT CDs. The parameter file that controls the installation steps isCENTRAL.R3S. Contrary to earlier releases there are no separate installation templates for a central instance with or without database.SAP is using a separate template for database installation. To restart the installation later it is however sufficient to restart with the original file. During and after installation, SAP requires hostname to return the computer name only, not the fully qualified domain name. So either set the hostname accordingly, or set an alias with alias hostname='hostname -s' for both orasid and sidadm (and for root at least during installation steps performed as root). It is also possible to adjust the installed .profile and .login files of both users that are installed during SAP installation. 10.7.8.3 Start R3SETUP 4.6B Make sure LD_LIBRARY_PATH is set correctly:
# export LD_LIBRARY_PATH=/oracle/IDS/lib:/sapmnt/IDS/exe:/oracle/805_32/lib

Start R3SETUP as root from installation directory:

# cd /oracle/IDS/sapreorg/install # ./R3SETUP -f CENTRDB.R3S

The script then asks some questions (defaults in brackets, followed by actual input):

Question Enter SAP System ID Enter SAP Instance Number Enter SAPMOUNT Directory Enter name of SAP central host Enter name of SAP db host Select character set Enter Oracle server version (1) Oracle 8.0.5, (2) Oracle 8.0.6, (3) Oracle 8.1.5, (4) Oracle 8.1.6 Extract Oracle Client archive Enter path to KERNEL CD Enter path to RDBMS CD Enter path to EXPORT1 CD Directory to copy EXPORT1 CD Enter path to EXPORT2 CD Directory to copy EXPORT2 CD Enter path to EXPORT3 CD Directory to copy EXPORT3 CD Enter path to EXPORT4 CD Directory to copy EXPORT4 CD Enter path to EXPORT5 CD Directory to copy EXPORT5 CD Enter path to EXPORT6 CD Directory to copy EXPORT6 CD Enter amount of RAM for SAP + DB Service Entry Message Server Enter Group-ID of sapsys Enter Group-ID of oper Enter Group-ID of dba

Default [C11] [00] [/sapmnt] [troubadix.domain.de] [troubadix] [1] (WE8DEC) IDSEnter Enter Enter Enter Enter Enter 1Enter

Input

[1] (Yes, extract) [/sapcd] [/sapcd] [/sapcd] [/oracle/IDS/sapreorg/CD4_DIR] [/sapcd] [/oracle/IDS/sapreorg/CD5_DIR] [/sapcd] [/oracle/IDS/sapreorg/CD6_DIR] [/sapcd] [/oracle/IDS/sapreorg/CD7_DIR] [/sapcd] [/oracle/IDS/sapreorg/CD8_DIR] [/sapcd] [/oracle/IDS/sapreorg/CD9_DIR]

Enter /oracle/IDS/sapreorg/KERNEL /oracle/IDS/sapreorg/RDBMS /oracle/IDS/sapreorg/EXPORT1 Enter /oracle/IDS/sapreorg/EXPORT2 Enter /oracle/IDS/sapreorg/EXPORT3 Enter /oracle/IDS/sapreorg/EXPORT4 Enter /oracle/IDS/sapreorg/EXPORT5 Enter /oracle/IDS/sapreorg/EXPORT6 Enter 850Enter (in Megabytes)

[3600] [101] [102] [100]

Enter Enter Enter Enter

Question Enter User-ID of sidadm Enter User-ID of orasid Number of parallel procs

Default [1000] [1002] [2] Enter Enter Enter

Input

If you had not copied the CDs to the different locations, then the SAP installer cannot find the CD needed (identified by the LABEL.ASCfile on the CD) and would then ask you to insert and mount the CD and confirm or enter the mount path. The CENTRDB.R3S might not be error free. In our case, it requested EXPORT4 CD again but indicated the correct key (6_LOCATION, then 7_LOCATION etc.), so one can just continue with entering the correct values. Apart from some problems mentioned below, everything should go straight through up to the point where the Oracle database software needs to be installed. 10.7.8.4 Start R3SETUP 4.6C SR2 Make sure LD_LIBRARY_PATH is set correctly. This is a different value from the 4.6B installation with Oracle 8.0.5:
# export LD_LIBRARY_PATH=/sapmnt/PRD/exe:/oracle/PRD/817_32/lib

Start R3SETUP as user root from installation directory:

# cd /oracle/PRD/sapreorg/install # ./R3SETUP -f CENTRAL.R3S

The script then asks some questions (defaults in brackets, followed by actual input):
Question Enter SAP System ID Enter SAP Instance Number Enter SAPMOUNT Directory Enter name of SAP central host Enter Database System ID Enter name of SAP db host Select character set Enter Oracle server version (2) Oracle 8.1.7 Extract Oracle Client archive Enter path to KERNEL CD Enter amount of RAM for SAP + DB Service Entry Message Server Enter Group-ID of sapsys Enter Group-ID of oper Enter Group-ID of dba Enter User-ID of oraprd Enter User-ID of prdadm Default [C11] [00] [/sapmnt] [majestix] [PRD] [majestix] [1] (WE8DEC) [1] (Yes, extract) [/sapcd] 2044 [3600] [100] [101] [102] [1002] [1000] Input PRDEnter Enter Enter Enter PRDEnter Enter Enter 2Enter Enter /oracle/PRD/sapreorg/KERNEL 1800Enter (in Megabytes) Enter Enter Enter Enter Enter Enter

Question LDAP support Installation step completed Choose installation service

Default [1] (continue) [1] (DB inst,file)

Input 3Enter (no support) Enter Enter

So far, creation of users gives an error during installation in phases OSUSERDBSID_IND_ORA (for creating user orasid) and OSUSERSIDADM_IND_ORA (creating user sidadm). Apart from some problems mentioned below, everything should go straight through up to the point where the Oracle database software needs to be installed.

10.7.9 Installing Oracle 8.0.5

Please see the corresponding SAP Notes and Oracle Readmes regarding Linux and Oracle DB for possible problems. Most if not all problems stem from incompatible libraries. For more information on installing Oracle, refer to the Installing Oracle chapter. 10.7.9.1 Installing the Oracle 8.0.5 with orainst If Oracle 8.0.5 is to be used, some additional libraries are needed for successfully relinking, as Oracle 8.0.5 was linked with an old glibc (RedHat 6.0), but RedHat 6.1 already uses a new glibc. So you have to install the following additional packages to ensure that linking will work:
compat-libs-5.2-2.i386.rpm compat-glibc-5.2-2.0.7.2.i386.rpm compat-egcs-5.2-1.0.3a.1.i386.rpm compat-egcs-c++-5.2-1.0.3a.1.i386.rpm compat-binutils-5.2-2.9.1.0.23.1.i386.rpm

See the corresponding SAP Notes or Oracle Readmes for further information. If this is no option (at the time of installation we did not have enough time to check this), one could use the original binaries, or use the relinked binaries from an original RedHat system. For compiling the intelligent agent, the RedHat Tcl package must be installed. If you cannot get tcl-8.0.3-20.i386.rpm, a newer one like tcl-8.0.530.i386.rpm for RedHat 6.1 should also do. Apart from relinking, the installation is straightforward:
# su - oraids # export TERM=xterm # export ORACLE_TERM=xterm # export ORACLE_HOME=/oracle/IDS # cd $ORACLE_HOME/orainst_sap

# ./orainst

Confirm all screens with Enter until the software is installed, except that one has to deselect the Oracle On-Line Text Viewer, as this is not currently available for Linux. Oracle then wants to relink with i386-glibc20-linux-gcc instead of the available gcc, egcs ori386-redhat-linux-gcc . Due to time constrains we decided to use the binaries from an Oracle 8.0.5 PreProduction release, after the first attempt at getting the version from the RDBMS CD working, failed, and finding and accessing the correct RPMs was a nightmare at that time. 10.7.9.2 Installing the Oracle 8.0.5 Pre-production Release for Linux (Kernel 2.0.33) This installation is quite easy. Mount the CD, start the installer. It will then ask for the location of the Oracle home directory, and copy all binaries there. We did not delete the remains of our previous RDBMS installation tries, though. Afterwards, Oracle Database could be started with no problems.

10.7.10 Installing the Oracle 8.1.7 Linux Tarball

Take the tarball oracle81732.tgz you produced from the installation directory on a Linux system and untar it to/oracle/SID/817_32/.

10.7.11 Continue with SAP R/3 Installation

First check the environment settings of users idsamd (sidadm) and oraids (orasid). They should now both have the files .profile,.login and .cshrc which are all using hostname. In case the system's hostname is the fully qualified name, you need to changehostname to hostname -s within all three files. 10.7.11.1 Database Load Afterwards, R3SETUP can either be restarted or continued (depending on whether exit was chosen or not). R3SETUP then creates the tablespaces and loads the data (for 46B IDES, from EXPORT1 to EXPORT6, for 46C from DISK1 to DISK4) with R3load into the database. When the database load is finished (might take a few hours), some passwords are requested. For test installations, one can use the well known default passwords (use different ones if security is an issue!):
Question Enter Password for sapr3 Confirum Password for sapr3 Enter Password for sys Confirm Password for sys Input sapEnter sapEnter change_on_installEnter change_on_installEnter

Question Enter Password for system Confirm Password for system

Input managerEnter managerEnter

At this point We had a few problems with dipgntab during the 4.6B installation. 10.7.11.2 Listener Start the Oracle Listener as user orasid as follows:
% umask 0; lsnrctl start

Otherwise you might get the error ORA-12546 as the sockets will not have the correct permissions. See SAP Note 072984. 10.7.11.3 Updating MNLS Tables If you plan to import non-Latin-1 languages into the SAP system, you have to update the Multi National Language Support tables. This is described in the SAP OSS Notes 15023 and 45619. Otherwise, you can skip this question during SAP installation. Note: If you do not need MNLS, it is still necessary to check the table TCPDB and initializing it if this has not been done. See SAP note 0015023 and 0045619 for further information.

10.7.12 Post-installation Steps

10.7.12.1 Request SAP R/3 License Key You have to request your SAP R/3 License Key. This is needed, as the temporary license that was installed during installation is only valid for four weeks. First get the hardware key. Log on as user idsadm and call saplicense:
# /sapmnt/IDS/exe/saplicense -get

Calling saplicense without parameters gives a list of options. Upon receiving the license key, it can be installed using:
# /sapmnt/IDS/exe/saplicense -install

You are then required to enter the following values:

SAP SYSTEM ID CUSTOMER KEY = SID, 3 chars = hardware key, 11 chars

INSTALLATION NO = installation, 10 digits EXPIRATION DATE = yyyymmdd, usually "99991231" LICENSE KEY = license key, 24 chars

10.7.12.2 Creating Users

Create a user within client 000 (for some tasks required to be done within client 000, but with a user different from users sap* and ddic). As a user name, We usually choose wartung (or service in English). Profiles required are sap_new and sap_all. For additional safety the passwords of default users within all clients should be changed (this includes users sap* and ddic). 10.7.12.3 Configure Transport System, Profile, Operation Modes, Etc. Within client 000, user different from ddic and sap*, do at least the following:
Task Configure Transport System, e.g. as Stand-Alone Transport Domain Entity Create / Edit Profile for System Maintain Operation Modes and Instances

Transa STMS RZ10 RZ04

These and all the other post-installation steps are thoroughly described in SAP installation guides. 10.7.12.4 Edit initsid.sap (initIDS.sap) The file /oracle/IDS/dbs/initIDS.sap contains the SAP backup profile. Here the size of the tape to be used, type of compression and so on need to be defined. To get this running with sapdba / brbackup, we changed the following values:
compress = hardware archive_function = copy_delete_save cpio_flags = "-ov --format=newc --block-size=128 --quiet" cpio_in_flags = "-iuv --block-size=128 --quiet" tape_size = 38000M tape_address = /dev/nsa0 tape_address_rew = /dev/sa0

Explanations:
compress:

The tape we use is a HP DLT1 which does hardware compression.

archive_function:

This defines the default behavior for saving Oracle archive logs: new logfiles are saved to tape, already saved logfiles are saved again and are then deleted. This prevents lots of trouble if you need to recover the database, and one of the archive-tapes has gone bad.
cpio_flags:

Default is to use -B which sets block size to 5120 Bytes. For DLT Tapes, HP recommends at least 32 K block size, so we used --block-size=128 for 64 K. --format=newc is needed because we have inode numbers greater than 65535. The last option --quiet is needed as otherwise brbackup complains as soon as cpio outputs the numbers of blocks saved.

cpio_in_flags:

Flags needed for loading data back from tape. Format is recognized

automatically.
tape_size:

This usually gives the raw storage capability of the tape. For security reason (we use hardware compression), the value is slightly lower than the actual value.
tape_address:

The non-rewindable device to be used with cpio. The rewindable device to be used with cpio.

tape_address_rew:

10.7.12.5 Configuration Issues after Installation The following SAP parameters should be tuned after installation (examples for IDES 46B, 1 GB memory):
Name ztta/roll_extension abap/heap_area_dia abap/heap_area_nondia em/initial_size_MB em/blocksize_kB ipc/shm_psize_40 SAP Note 0013026: Name ztta/dynpro_area SAP Note 0157246: Name rdisp/ROLL_MAXFS rdisp/PG_MAXFS 16000 30000 Value 2500000 Value 250000000 300000000 400000000 256 1024 70000000 Value

Note: With the above parameters, on a system with 1 gigabyte of memory, one may find memory consumption similar to:
Mem: 547M Active, 305M Inact, 109M Wired, 40M Cache, 112M Buf, 3492K Free

10.7.13 Problems during Installation

10.7.13.1 Restart R3SETUP after Fixing a Problem stops if it encounters an error. If you have looked at the corresponding logfiles and fixed the error, you have to start R3SETUPagain, usually selecting REPEAT as option for the last step R3SETUP complained about.
R3SETUP

To restart R3SETUP, just start it with the corresponding R3S file:

# ./R3SETUP -f CENTRDB.R3S

for 4.6B, or with

# ./R3SETUP -f CENTRAL.R3S

for 4.6C, no matter whether the error occurred with CENTRAL.R3S or DATABASE.R3S. Note: At some stages, R3SETUP assumes that both database and SAP processes are up and running (as those were steps it already completed). Should errors occur and for example the database could not be started, you have to start both database and SAP by hand after you fixed the errors and before starting R3SETUP again. Do not forget to also start the Oracle listener again (as orasid with umask 0; lsnrctl start) if it was also stopped (for example due to a necessary reboot of the system). 10.7.13.2 OSUSERSIDADM_IND_ORA during R3SETUP If R3SETUP complains at this stage, edit the template file R3SETUP used at that time (CENTRDB.R3S (4.6B) or either CENTRAL.R3S orDATABASE.R3S (4.6C)). Locate [OSUSERSIDADM_IND_ORA] or search for the only STATUS=ERROR entry and edit the following values:
HOME=/home/sidadm (was empty) STATUS=OK (had status ERROR)

Then you can restart R3SETUP again. 10.7.13.3 OSUSERDBSID_IND_ORA during R3SETUP Possibly R3SETUP also complains at this stage. The error here is similar to the one in phase OSUSERSIDADM_IND_ORA. Just edit the template file R3SETUP used at that time (CENTRDB.R3S (4.6B) or either CENTRAL.R3S or DATABASE.R3S (4.6C)). Locate[OSUSERDBSID_IND_ORA] or search for the only STATUS=ERROR entry and edit the following value in that section:
STATUS=OK

Then restart R3SETUP. 10.7.13.4 oraview.vrf

FILE NOT FOUND

during Oracle Installation

You have not deselected Oracle On-Line Text Viewer before starting the installation. This is marked for installation even though this option is currently not

available for Linux. Deselect this product inside the Oracle installation menu and restart installation. 10.7.13.5 TEXTENV_INVALID during R3SETUP, RFC or SAPgui Start If this error is encountered, the correct locale is missing. SAP Note 0171356 lists the necessary RPMs that need be installed (e.g.saplocales-1.0-3, saposcheck-1.01 for RedHat 6.1). In case you ignored all the related errors and set the corresponding STATUSfrom ERROR to OK (in CENTRDB.R3S) every time R3SETUP complained and just restarted R3SETUP, the SAP system will not be properly configured and you will then not be able to connect to the system with a SAPgui, even though the system can be started. Trying to connect with the old Linux SAPgui gave the following messages:
Sat May 5 14:23:14 2001 *** ERROR => no valid userarea given [trgmsgo. 0401] Sat May 5 14:23:22 2001 *** ERROR => ERROR NR 24 occured [trgmsgi. 0410] *** ERROR => Error when generating text environment. [trgmsgi. 0435] *** ERROR => function failed [trgmsgi. 0447] *** ERROR => no socket operation allowed [trxio.c 3363] Speicherzugriffsfehler

This behavior is due to SAP R/3 being unable to correctly assign a locale and also not being properly configured itself (missing entries in some database tables). To be able to connect to SAP, add the following entries to file DEFAULT.PFL (see Note 0043288):
abap/set_etct_env_at_new_mode = 0 install/collate/active = 0 rscp/TCP0B = TCP0B

Restart the SAP system. Now you can connect to the system, even though countryspecific language settings might not work as expected. After correcting country settings (and providing the correct locales), these entries can be removed from DEFAULT.PFL and the SAPsystem can be restarted. 10.7.13.6 ORA-00001 This error only happened with Oracle 8.1.7 on FreeBSD. The reason was that the Oracle database could not initialize itself properly and crashed, leaving semaphores and shared memory on the system. The next try to start the database then returned ORA-00001. Find them with ipcs
-a

and remove them with ipcrm.

10.7.13.7 ORA-00445 (Background Process PMON Did Not Start) This error happened with Oracle 8.1.7. This error is reported if the database is started with the usual startsap script (for examplestartsap_majestix_00) as user prdadm. A possible workaround is to start the database as user oraprd instead with svrmgrl:
% svrmgrl SVRMGR> connect internal; SVRMGR> startup; SVRMGR> exit

10.7.13.8 ORA-12546 (Start Listener with Correct Permissions) Start the Oracle listener as user oraids with the following commands:
# umask 0; lsnrctl start

Otherwise you might get ORA-12546 as the sockets will not have the correct permissions. See SAP Note 0072984. 10.7.13.9 ORA-27102 (Out of Memory) This error happened whilst trying to use values for MAXDSIZ and DFLDSIZ greater than 1 GB (1024x1024x1024). Additionally, we got Linux Error 12: Cannot allocate memory. 10.7.13.10 [DIPGNTAB_IND_IND] during R3SETUP In general, see SAP Note 0130581 (R3SETUP step DIPGNTAB terminates). During the IDES-specific installation, for some reason the installation process was not using the proper SAP system name IDS, but the empty string "" instead. This leads to some minor problems with accessing directories, as the paths are generated dynamically using SID (in this case IDS). So instead of accessing:
/usr/sap/IDS/SYS/... /usr/sap/IDS/DVMGS00

the following paths were used:

/usr/sap//SYS/... /usr/sap/D00

To continue with the installation, we created a link and an additional directory:

# pwd /compat/linux/usr/sap

# ls -l total 4 drwxr-xr-x 3 drwxr-x--x 5 lrwxr-xr-x 1 drwxrwxr-x 2 idsadm sapsys 512 May 5 11:20 D00 idsadm sapsys 512 May 5 11:35 IDS root sapsys 7 May 5 11:35 SYS -> IDS/SYS

idsadm sapsys 512 May 5 13:00 tmp

drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans

We also found SAP Notes (0029227 and 0008401) describing this behavior. We did not encounter any of these problems with the SAP4.6C installation. 10.7.13.11 [RFCRSWBOINI_IND_IND] during R3SETUP During installation of SAP 4.6C, this error was just the result of another error happening earlier during installation. In this case, you have to look through the corresponding logfiles and correct the real problem. If after looking through the logfiles this error is indeed the correct one (check the SAP Notes), you can set STATUS of the offending step from ERROR to OK (file CENTRDB.R3S) and restart R3SETUP. After installation, you have to execute the report RSWBOINS from transaction SE38. See SAP Note 0162266 for additional information about phase RFCRSWBOINI and RFCRADDBDIF. 10.7.13.12 [RFCRADDBDIF_IND_IND] during R3SETUP Here the same restrictions apply: make sure by looking through the logfiles, that this error is not caused by some previous problems. If you can confirm that SAP Note 0162266 applies, just set STATUS of the offending step from ERROR to OK (file CENTRDB.R3S) and restart R3SETUP. After installation, you have to execute the report RADDBDIF from transaction SE38. 10.7.13.13 sigaction sig31: File size limit exceeded This error occurred during start of SAP processes disp+work. If starting SAP with the startsap script, subprocesses are then started which detach and do the dirty work of starting all other SAP processes. As a result, the script itself will not notice if something goes wrong. To check whether the SAP processes did start properly, have a look at the process status with ps ax | grep SID, which will give you a list of all Oracle and SAP processes. If it looks like some processes are missing or if you cannot connect to the SAP system, look at the corresponding logfiles which can be found at /usr/sap/SID/DVEBMGSnr/work/. The files to look at are dev_ms and dev_disp. Signal 31 happens here if the amount of shared memory used by Oracle and SAP exceed the one defined within the kernel configuration file and could be resolved by using a larger value:

# larger value for 46C production systems: options SHMMAXPGS=393216 # smaller value sufficient for 46B: #options SHMMAXPGS=262144

10.7.13.14 Start of saposcol Failed There are some problems with the program saposcol (version 4.6D). The SAP system is using saposcol to collect data about the system performance. This program is not needed to use the SAP system, so this problem can be considered a minor one. The older versions (4.6B) does work, but does not collect all the data (many calls will just return 0, for example for CPU usage).

SAP Installation Procedure on WIN 2k Adv Server

With Compliments by: Bhanu Prakash Pogula Email: bpogula@sify.com
INSTALLING HARD DISK ( IF U ARE TRYING TO LOAD SAP ON A SEPARATE HDD) Connect HDD with cable Win 2000 installation. 1. Go to bios set up by pressing continuously clicking del on start. 2. change the first bootable device to CD. 3. insert the CD and RESTART system. 4. click any key to boot from CD. 5. click ENTER 6. click ENTER again 7. Click on C ( to continue) 8. click on F8 ( to agree) 9. partitions C: 4197Mb, D 12000Mb, E 6000Mb 10. select C drive 11. click ENTER to install 12. click ENTER again to continue automatically restarts, set up continues. 13. click on NEXT 14. click on NEXT 15. click on NEXT 16. key RBDC9-VTRC8-D7972-J97JY-PRVMG 17. click on NEXT 18. TYPE no of concurrent connections 9 19. click on NEXT 20. TYPE COMPUTER NAME 46IDES 21. click on NEXT 22. remove IIS (deselect) 23. click on NEXT 24. enter date & time 25. click on NEXT 26. finish WINDOWS CONFIGURATION Creating partitions for new disk. START PROGRAMMES ADMIN TOOLS COMP MANAGEMENT DISK MANAGEMENT 1. right click on unallocated space. 2. click on CREATE PARTITIONS, 3. click on NEXT 4. click on NEXT 5. type 11320 (partition size)

6. click on NEXT 7. click on NEXT 8. type file system NTFS 9. click on quick format 10. click on NEXT 11. click on FINISH 12. again right click on unallocated space 13. repeat the exercise from point 5 but for complete size note C drive contains operating system E/D drive contain 46C software S drive contains SAP software.. PERFORMANCE MY COMPUTER properties advanced performance optionschange, 1. Select S drive. 2. type initial =1600& max =1652 3. click on SET 4. click on OK 5. click on OK 6. click on OK NETWORK SETTINGS STARTSETTINGS CONTROL PANEL ADD/REMOVE HARD WARE, 1. click on NEXT 2. click on NEXT 3. select ad a new device 4. click on NEXT 5. select (now I want to select from Hardware list) 6. click on NEXT 7. select network adaptors, 8. click on NEXT 9. select MICROSOFT 10. click on NEXT 11. click on NEXT 12. click on FINISH 13. close all windows 14. right click on MY NETWORK PLACES, 15. go to properties, 16. right click on local area connections 17. should be able to see Microsoft loopback adaptor on the screen. 18. select properties 19. select TCP/IP 20. click on properties 21. select ( use the following IP addresses) 22. type IP addresses 198.1.1.1 23. subnet mass 255.255.255.0 24. click on OK 25. select show icon on Task bar 26. click on OK 27. close all windows. HOST FILE CONFIGURATION 1. go to WINDOWS EXPLORER 2. select C drive, WIN NT, system 32 , DRIVERS, etc 3. double click on HOSTS 4. open with note pad 5. go to end of the page 6. type IP address 198.1.1.1 7. press TAB once 8. type 46cides 9. press TAB twice 10. click on SAVE 11. click on EXIT 12. RESTART sytem Software contains three folders 1. 46cides ( a. KERNEL, b. ORACLE 817, c.ORACLE PATCHES 2. DB EXPORT

3.

SAP GUI

ORACLE INSTALLATION 1. 46CIDESoracle 817 NTi386setup run the set up by double clicking 2. click on NEXT 3. source path destination path : S:\oracle\ora81 4. click on NEXT 5. click on NEXT 6. click on NEXT 7. type GLOBAL DATA BASE NAME : ORACLE 8. click on NEXT 9. click on INSTALL 10. click on OK 11. click on EXIT 12. click on YES 13. close all windows 14. start programsadmin tools services 15. select ORACLE SERVICES 16. select all ORACLE releated services ONE BY ONE. ORACLE PATCHES 46CIDES ORACLE PATCHESPATCH DISK1 INSTALL WIN 32 1. set up (double click) 2. click on NEXT 3. click on NEXT 4. click on INSTALL 5. click on INSTALL 6. click on EXIT KERNEL INSTALLATION 46CIDESKERNELNT I386 MMC 1. double click on IMMC 2. click on NEXT 3. I agree 4. click on NEXT 5. click on NEXT 6. click on NEXT 7. click on FINISH 46CIDESKERNELNT I386 NT PATCH 1. double click on R3DLLINS 2. click on Ok 3. close all windows 4. RESTART 46CIDESKERNELNT COMMON 1. double click on R3 SET UP 2. type SAP SYSTEM NAME IND 3. click on NEXT 4. click on NEXT 5. click on NEXT at 85% 6. click on NEXT automatically logs off 7. login and control+alt+del CENTROL INSTANCE Startprogramssap system for IND install CENTRAL INSTANCE 1. click on NEXT 2. type instance no OO, 3. click on NEXT 4. click on NEXT 5. click on NEXT 6. click on NEXT 7. click on NEXT 8. click on NEXT 9. click on NEXT 10. click on NEXT 11. click on NEXT 12. type LOCATION OF KERNEL CD E:\46cides\kernel

13. 14. AAA 15. 16. AAA 17. 18. 19. 20. 21. 22. 23.

click on NEXT password AAA click on NEXT password AAA click on NEXT select NO LDAP SUPPORTS click on NEXT click on NEXT click on NEXT click on NEXT click on EXIT when finished

DATA BASE INSTANCE Start programs SAP set up system for IND install database instance 1. click on NEXT 2. click on NEXT 3. click on NEXT 4. click on NEXT 5. click on NEXT 6. click on NEXT 7. click on NEXT 8. click on NEXT 9. click on NEXT 10. click on NEXT 11. click on NEXT 12. click on NEXT 13. click on NEXT 14. click on NEXT 15. click on NEXT 16. type location of CDS for KERNEL : E:\ 46cides\KERNEL for EXPORT : E:\DBEXPORT 17. click on NEXT 18. password AAA AAA 19. click on NEXT 20. click on NEXT 21. click on NEXT 22. click on NEXT 23. click on EXIT at 32% 24. log off 25. log in 26. user ind adm 27. password AAA 28. OK WINDOWS EXPLORER C:\USERS\IND ADM\INSTALL\R3 SET UP FILE 1. double clik on R# set up file 2. select database R3S 3. open 4. type pass word AAA AAA 5. click on NEXT 6. at 91% password AAA AAA 7. at 93% start MMC 8. click on NEXT 9. at 100% EXIT 10. click on STOP MMC 11. restart system POST INSTALLATION E:\apgui320\gui\windows\win 32\setup(double click) 1. click on NEXT 2. click on INSTALL 3. click on FINISH 4. click on SAP logon

5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.

select NEW type DESCRIPTION : 46CIDES type application server : 46CIDES type system no : 00 start MMC close MMC log in SAP client 000, user sap* password 06071992 txn code SM28 ENTER ( TO CHECK ERROR) RESULT : NO ERROR REPORTED ( in installation)

STMS Description Student Click on SAVE Go to overview transport routes Select display change mode (second icon) Configurationstandard configuration single system ( main menu) Click on Enter Configurationdistributeactivate Click on Enter F3 (to go back) RZ 10 Utilities import profiles of active servers Click on Enter Click on F3 (to go back) Profile click on F4 Select IND DVEMGS0046CIDES Select EXTEND MAINT change Select create paramaeters9 icon) Type paramter name : rdisp/max-wprun-time Type parameter value ; 3000 Copy icon Go back Click Yes CREATE PARAMETER Paramater name : abap\ field exit Value ; YES Select COPY icon, go back YES Create parameter : login/system-client : 800 select copy icongo back yes create parameter :eu/iwb/installed/languages :EN select COPY icon go back YES again go back click on YES click on SAVE click on YES click on ENTER click on ENTER (USER CREATION) TXN : SU01 user : sapuser select : create icon address title first name last name logon data go on clicking ENTER no of times initial password : abc repeat pass word : abc

DEFAULTS Logon language : En Output device ; LP01 Select : Out put immediately & decimal PROFILES Type 1. SAP ALL TYPE 2. SAP NEW SAVE Log off from SAP Login to SAP type user : sapuser new password : abap repeat password : abap password : abc

txn : SALE IMGerror handlingbasic work flow settings Select AUTOMATIC CUSTOMIZING icon Go back Txn 00w4 Select DISPLAY CHANGE MODE icon Create icon CREATE Prefix no System ID Client Click on Save Local object Cancel X CREATE Prefix no System ID Client Click on Save Local object Cancel X TXN SE 38 Program name : Z FIRST CREATE ACCESS KEY : 36687663221261278694 TITLE : DEMO TYPE : EXECUTOR Click on SAVE LOCAL OBJECT Log off from SAP Log into SAP Client : 800 User : sap Pass word : 06071992 RUN txn SU01 for 000 client 978 IND 000

972 IND 800

Log off from SAP Log into SAP Client User Pass word Click on ENTER

: 800 : sap : abc

Enter new password : abap Logoff Stop MMC