diff --git a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml index 75d293cc11..392c73f6c5 100644 --- a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml @@ -477,7 +477,7 @@ disco.example.com 7115-70839-20412 &prompt.root; cd /usr/X11R6/lib/X11/fonts/X &prompt.root; mkfontdir &prompt.root; cd ../MathType1 -&prompt.root; mkfontdir +&prompt.root; mkfontdir Now add the new font directories to your font path: @@ -915,10 +915,6 @@ export PATH - - - - @@ -933,12 +929,12 @@ export PATH Valentino Vaschetto - Converted to SGML by + Original version converted to SGML by - Installing SAP R/3 (4.6B - IDES) + Installing SAP R/3 applications @@ -953,11 +949,23 @@ export PATH Preface This document describes a possible way of installing a - SAP R/3 4.6B IDES-System - with Oracle 8.0.5 - for Linux onto a FreeBSD 4.3 machine, including the installation - of FreeBSD 4.3-STABLE and - Oracle 8.0.5. + 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 @@ -975,8 +983,11 @@ export PATH Software - The following CDROMs have been used for - SAP-installation: + The following CD-ROMs have been used for SAP-installations: + + + SAP R/3 4.6B, Oracle 8.0.5 + @@ -994,28 +1005,28 @@ export PATH Linux - EXPORT1 51010208 IDES / DB-Export / Disc - 1 of 6 + EXPORT1 51010208 IDES / DB-Export / + Disc 1 of 6 - EXPORT2 51010209 IDES / DB-Export / Disc - 2 of 6 + EXPORT2 51010209 IDES / DB-Export / + Disc 2 of 6 EXPORT3 51010210 IDES / DB-Export / - Disc3 of 6 + Disc 3 of 6 EXPORT4 51010211 IDES / DB-Export / - Disc4 of 6 + Disc 4 of 6 EXPORT5 51010212 IDES / DB-Export / - Disc5 of 6 + Disc 5 of 6 EXPORT6 51010213 IDES / DB-Export / - Disc6 of 6 + Disc 6 of 6 @@ -1024,8 +1035,61 @@ export PATH Additionally, I 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 - of course FreeBSD 4.3 stable (it was only a few days past 4.3 + of course FreeBSD 4.3-STABLE (it was only a few days past 4.3 RELEASE). + + + + SAP R/3 4.6C SR2, Oracle 8.1.7 + + + + + + Name Number Description + + + + + KERNEL 51014004 SAP Kernel Oracle / + SAP Kernel Version 4.6D / DEC, Linux + + + RDBMS 51012930 Oracle 8.1.7/ RDBMS / + Linux + + + EXPORT1 51013953 Release 4.6C SR2 / Export + / Disc 1 of 4 + + + EXPORT1 51013953 Release 4.6C SR2 / Export + / Disc 2 of 4 + + + EXPORT1 51013953 Release 4.6C SR2 / Export + / Disc 3 of 4 + + + EXPORT1 51013953 Release 4.6C SR2 / Export + / Disc 4 of 4 + + + LANG1 51013954 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're 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.5-STABLE (20.03.2002). + @@ -1035,6 +1099,9 @@ export PATH SAP R/3 or proved to be useful during installation: + + SAP R/3 4.6B, Oracle 8.0.5 + @@ -1045,8 +1112,8 @@ export PATH - 0171356 SAP Software auf Linux: grundlegenden - Anmerkungen + 0171356 SAP Software on Linux: Essential + Comments 0201147 INST: 4.6C R/3 Inst. on UNIX - @@ -1074,14 +1141,69 @@ export PATH + + + SAP R/3 4.6C, Oracle 8.1.7 + + + + + + Number + Title + + + + + 0015023 Initializing table TCPDB (RSXP0004) + (EBCDIC) + + + 0045619 R/3 with several languages or + typefaces + + + 0171356 SAP Software on Linux: Essential + Comments + + + 0195603 RedHat 6.1 Enterprise version: + Known problems + + + 0212876 The new archiving tool SAPCAR + + + 0300900 Linux: Released DELL Hardware + + + 0377187 RedHat 6.2: important remarks + + + 0387074 INST: R/3 4.6C SR2 Installation on + UNIX + + + 0387077 INST: R/3 4.6C SR2 Inst. on UNIX - + Oracle + + + 0387078 SAP Software on UNIX: OS Dependencies + 4.6C SR2 + + + + + Hardware-Requirements - The following equipment is sufficient for a - SAP R/3 System (4.6B): + 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: @@ -1104,7 +1226,7 @@ export PATH 2GB ECC - Hard Disc Space + Hard Disk Space 50-60GB (IDES) 50-60GB (IDES) @@ -1113,41 +1235,52 @@ export PATH For use in production, Xeon-Processors with large cache, - high-speed disc access (SCSI, RAID hardware controller), USV - and ECC-RAM is recommended. The large amount of Hard disc + 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. Usually after - installation it is then necessary to extend some - tablespaces. + 27 GB of database files during installation. This space is + also sufficient for initial production systems and application + data. - I used a dual processor board with 2 800MHz Pentium III - processors, Adaptec 29160 Ultra160 SCSI adapter (for accessing - a 40/80 GB DLT tape drive and CDROM), Mylex AcelleRAID (2 - channels, firmware 6.00-1-00 with 32MB RAM). To the Mylex - Raid-controller are attached two 17GB hard discs (mirrored) - and four 36GB hard discs (RAID level 5). + + SAP R/3 4.6B, Oracle 8.0.5 + The following off-the-shelf hardware was used: a dual processor + board with 2 800MHz 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 32MB RAM). + To the Mylex Raid-controller are attached two 17GB hard disks + (mirrored) and four 36GB hard disks (RAID level 5). + + + + SAP R/3 4.6C, Oracle 8.1.7 + + For this installation a DELL PowerEdge 2500 was used: a + dual processor board with two 1000MHz Pentium III processors + (256kB Cache), 2GB PC133 ECC SDRAM, PERC/3 DC PCI Raid Controller + with 128MB, and an EIDE DVD-ROM drive. To the RAID-controller are + attached two 18GB hard disks (mirrored) and four 36GB hard disks + (RAID level 5). + - Installation of FreeBSD 4.3-STABLE + Installation of FreeBSD - First I installed FreeBSD 4.3 stable. I did the - default-installation via FTP. + First you have to install FreeBSD. There are several ways to do + this (FreeBSD 4.3 was installed via FTP, FreeBSD 4.5 directly from + release-CD). - - Installation via FTP Get the diskimages - kern.flp and mfsroot.flp and put them on floppy disks (I got - mine from ftp7.de.FreeBSD.org. Please choose the appropriate - mirror). + + Disk Layout - &prompt.root; dd if=kern.flp of=/dev/fd0 -&prompt.root; dd if=mfsroot.flp of=/dev/fd0 - - Do not forget to use different disks for the two images, - then boot from the floppy with the kern.flp-image on it - and follow instructions. I used the following 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): @@ -1206,128 +1339,68 @@ export PATH - I had to configure and initialize the two logical drives - with the Mylex software beforehand. It is located on the - board itself and can be started during the boot phase of the - PC. + 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 - I decided to just create them as real subdirectories for simplicity. - - - Get the Latest STABLE Sources - - For FreeBSD 4.3 stable onwards, it is quite easy to get - the latest stable sources. With the older versions of - FreeBSD, I had my own script located in /etc/cvsup. Setting - up CVSup for FreeBSD 4.3 is quite - easy. As user - root do the following: - - &prompt.root; cp /etc/defaults/make.conf /etc/make.conf -&prompt.root; vi /etc/make.conf - - The file /etc/make.conf requires the - following entries to be active: - - SUP_UPDATE= yes -SUP= /usr/local/bin/cvsup -SUPFLAGS= -g -L 2 -SUPHOST= cvsup8.FreeBSD.org -SUPFILE= /usr/share/examples/cvsup/stable-supfile -PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile -DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile - - Change the SUPHOST-value - appropriately. The supfiles in - /usr/share/examples/cvsup should be - fine. If you do not want to load all the docfiles, leave the - corresponding DOCSUPFILE-entry - inactive. Starting cvsup - to get the latest stable-sources is then very easy: - - &prompt.root; cd /usr/src -&prompt.root; make update - - - - <command>make world</command> and a New Kernel - The first thing to do is to install the sources. - As user root, do the following: - - &prompt.root; cd /usr/src -&prompt.root; make world - - If this goes through, one can then continue creating and - configuring the new kernel. Usually this is where to - customize the kernel configuration file. As the computer is - named troubadix, the natural name for the - config file also is troubadix: - - &prompt.root; cd /usr/src/sys/i386/conf -&prompt.root; cp GENERIC TROUBADIX -&prompt.root; vi TROUBADIX - - At this stage one can define the drivers to use and not - to use, etc. See the appropriate documentation or have a - look at file LINT for some additional - explanations. - - One can then also include the parameters as described - below Creating the new kernel then requires: - - &prompt.root; cd /usr/src/sys/i386/conf -&prompt.root; config TROUBADIX -&prompt.root; cd /usr/src/sys/compile/TROUBADIX -&prompt.root; make depend -&prompt.root; make -&prompt.root; make install - - - After make install finished - successfully, one should reboot the computer to have the new - kernel available. - + 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. Installing the Linux Environment - I had some trouble downloading the required RPM-files (for - 4.3 stable, 2nd May 2001), so you might try one of the - following locations (if all the others fail and the following - are not out of date): - - - ftp7.de.FreeBSD.org/pub/FreeBSD/distfiles/rpm - ftp.redhat.com/pub/redhat/linux/6.1/en/os/i386/RedHat/RPMS - + During the first installation with FreeBSD 4.3-STABLE I had some + trouble downloading the required RPM-files (for 4.3 stable, 2nd May + 2001), but with FreeBSD 4.5-STABLE, everything went very smooth. + Should you encounter some problems, try to download those files by + hand. For a list of RPM-Mirrors and required files, see the + corresponding makefile. Installing Linux Base-system - First the Linux base-system needs to be installed (as - root): + + First the linux_base + port needs to be installed (as root). This is + currently linux_base-6. + &prompt.root; cd /usr/ports/emulators/linux_base -&prompt.root; make package +&prompt.root; make package + Installing Linux Development - Next, the Linux development is needed: + The Linux development is needed, if you want to install + Oracle on FreeBSD according to the + corresponding description in the handbook: &prompt.root; cd /usr/ports/devel/linux_devtools -&prompt.root; make package +&prompt.root; make package + + Linux Development 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. @@ -1336,44 +1409,35 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile Installing Necessary RPMs RPMs - To start the R3SETUP-Program, pam support is needed. As - this also requires some other packages, I ended up - installing several packages. After that, pam still - complained about a missing package, so I forced the - installation and it worked. I wonder if the other packages - are really needed or if it would have been sufficient to - install the pam-package. + To start the R3SETUP-Program, pam support is needed. + During the first SAP-Installation on FreeBSD 4.3-STABLE I + 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 I + directly forced the installation of pam rpm, which also + works, so it seems the dependend packages are not needed: - Anyway, here is the list of packages I installed: - - - cracklib-2.7-5.i386.rpm - cracklib-dicts-2.7-5.i386.rpm - pwdb-0.60-1.i386.rpm - pam-0.68-7.i386.rpm - - - I installed these packages with the following - command: - - &prompt.root; rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm <package_name> - - except for the pam package, which I forced with &prompt.root; rpm -i --ignoreos --nodeps --root /compat/linux --dbpath /var/lib/rpm \ - pam-0.68-7.i386.rpm + pam-0.68-7.i386.rpm - For Oracle to run the - intelligent agent, I also had to install the following - RedHat Tcl package (as is stated in the FreeBSD Handbook): + For Oracle 8.0.5 to run the + intelligent agent, I also had to install the RedHat Tcl package tcl-8.0.5-30.i386.rpm (otherwise the relinking during Oracle install will not work). There are some other issues regarding relinking of Oracle, but that is - a Oracle-Linux issue, not FreeBSD specific as far as I - understand it. + a Oracle-Linux issue, not FreeBSD specific. + + + Some additional hints + It might also be a good idea to add linprocfs + to /etc/fstab. See man linprocfs. + Another parameter to set is kern.fallback_elf_brand=3 + which is done in file /etc/sysctl.conf. + @@ -1410,12 +1474,32 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile - I also created some links, so FreeBSD will also find the - correct path: + It is also necessary to created some links. Otherwise + the SAP-Installer will complain, as it is checking the + created links: &prompt.root; ln -s /compat/linux/oracle /oracle &prompt.root; ln -s /compat/linux/sapmnt /sapmnt -&prompt.root; ln -s /compat/linux/usr/sap /usr/sap +&prompt.root; 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' @@ -1428,7 +1512,9 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile by SAP (for example SAP and NIX. For a complete list please see the SAP documentation). For the IDES - installation I used IDS. We have + installation I 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 I used with my installation): @@ -1484,7 +1570,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile 1000 - idsadm + idsadm/prdadm <sid>adm sapsys oper @@ -1492,7 +1578,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile 1002 - oraids + oraids/oraprd ora<sid> dba oper @@ -1506,27 +1592,27 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile requires the following (please note shell and home directory) entries for SAP-Administrator: - Name: idsadm <sid>adm + Name: <sid>adm Password: ****** -Fullname: SAP IDES Administrator +Fullname: SAP Administrator <SID> Uid: 1000 Gid: 101 (sapsys) Class: Groups: sapsys dba -HOME: /home/idsadm /home/<sid>adm -Shell: /bin/sh +HOME: /home/<sid>adm +Shell: bash (/compat/linux/bin/bash) and for Database-Administrator: - Name: oraids ora<sid> + Name: ora<sid> Password: ****** -Fullname: Oracle IDES Administrator +Fullname: Oracle Administrator <SID> Uid: 1002 Gid: 100 (dba) Class: Groups: dba -HOME: /oracle/IDS /oracle/<sid> -Shell: /bin/sh +HOME: /oracle/<sid> +Shell: bash (/compat/linux/bin/bash) This should also include group oper in case you are using both @@ -1543,32 +1629,51 @@ Shell: /bin/sh choose to create them as simple directories, as they are all located on the same RAID 5 anyway: - First we will set owners and right of some directories (as + First we will set owners and rights of some directories (as user root): &prompt.root; chmod 775 /oracle &prompt.root; chmod 777 /sapmnt &prompt.root; chown root:dba /oracle -&prompt.root; chown idsadm:sapsys /compat/linux/usr/sap -&prompt.root; chmow 775 /compat/linux/usr/sap +&prompt.root; chown <sid>adm:sapsys /compat/linux/usr/sap +&prompt.root; chmod 775 /compat/linux/usr/sap - Second we will create directories as user ora<sid>. These - will all be subdirectories of /oracle/IDS: + Second we will create directories as user + ora<sid>. These + will all be subdirectories of + /oracle/<SID>: - &prompt.root; su - oraids + &prompt.root; su - ora<sid> +&prompt.root; cd /oracle/<SID> &prompt.root; mkdir mirrlogA mirrlogB origlogA origlogB &prompt.root; mkdir sapdata1 sapdata2 sapdata3 sapdata4 sapdata5 sapdata6 &prompt.root; mkdir saparch sapreorg -&prompt.root; exit +&prompt.root; exit + + For the Oracle 8.1.7-installation + some additional directories are needed: + + &prompt.root; su - ora<sid> +&prompt.root; cd /oracle +&prompt.root; mkdir 805_32 +&prompt.root; mkdir client stage +&prompt.root; mkdir client/80x_32 +&prompt.root; mkdir stage/817_32 +&prompt.root; cd /oracle/<SID> +&prompt.root; mkdir 817_32 + + The directory client/80x_32 is used + with exactly this name. Don't replace the x + with some number or anything. In the third step we create directories as user - idsadm (<sid>adm): + <sid>adm: - &prompt.root; su - idsadm + &prompt.root; su - <sid>adm &prompt.root; cd /usr/sap -&prompt.root; mkdir IDS +&prompt.root; mkdir <SID> &prompt.root; mkdir trans -&prompt.root; exit +&prompt.root; exit @@ -1583,13 +1688,18 @@ Shell: /bin/sh entries from 00 to 99 for dp, gw, sp and - ms): + 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 3200/tcp # SAP Dispatcher. 3200 + Instance-Number + +sapdp00 3200/tcp # SAP Dispatcher. 3200 + Instance-Number sapgw00 3300/tcp # SAP Gateway. 3300 + Instance-Number sapsp00 3400/tcp # 3400 + Instance-Number sapms00 3500/tcp # 3500 + Instance-Number -sapmsIDS 3600/tcp # SAP Message Server. 3600 + Instance-Number +sapms<SID> 3600/tcp # SAP Message Server. 3600 + Instance-Number +sapgw00s 4800/tcp # SAP Secure Gateway 4800 + Instance-Number @@ -1612,9 +1722,15 @@ sapmsIDS 3600/tcp # SAP Message Server. 3600 + Instance-Number de_DE.ISO-8859-1 en_US.ISO-8859-1 + Create the links like this: + + &prompt.root; cd /compat/linux/usr/share/locale +&prompt.root; ln -s de_DE de_DE.ISO-8859-1 +&prompt.root; 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 (eg by setting the status of the offending steps to + 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. @@ -1624,13 +1740,15 @@ en_US.ISO-8859-1 kernel tuning SAP R/3 Systems need a lot of resources. I therefore - added the following parameters to my kernel config-file: + added the following parameters to my kernel config-file: # Set these for memory pigs (SAP and Oracle): options MAXDSIZ="(1024*1024*1024)" -options DFLDSIZ="(1024*1024*1024)" # System V options needed. +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 @@ -1642,12 +1760,21 @@ 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 indentifiers -options SEMUME=100 #number of UNDO keys +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. - + 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. + + With the default installation of FreeBSD 4.5 on x386, + leave MAXDSIZ and DFLDSIZ at 1GB maximum. Otherwise, strange + errors like ORA-27102: out of memory and + Linux Error: 12: Cannot allocate memory + might happen. @@ -1657,61 +1784,89 @@ options SEMUME=100 #number of UNDO keys Preparing SAP CDROMs - There are lots of CDROMs to mount and unmount during + There are many CDROMs to mount and unmount during the installation. Assuming you have enough CDROM-drives, you can just mount them all. I decided to copy the CDROM contents to corresponding directories: - /oracle/IDS/sapreorg/<cd-name> + /oracle/<SID>/sapreorg/<cd-name> where <cd-name> was one of KERNEL, RDBMS, EXPORT1, EXPORT2, EXPORT3, EXPORT4, EXPORT5 and - EXPORT6. All the - filenames should be in capital letters, otherwise use the -g - option for mounting. So use the following commands: + 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: &prompt.root; mount_cd9660 -g /dev/cd0a /mnt -&prompt.root; cp -R /mnt/* /oracle/IDS/sapreorg/<cd-name> -&prompt.root; umount /mnt +&prompt.root; cp -R /mnt/* /oracle/<SID>/sapreorg/<cd-name> +&prompt.root; umount /mnt Running the install-script - First we need to prepare an install-directory: + First you have to prepare an install-directory: - &prompt.root; cd /oracle/IDS/sapreorg + &prompt.root; cd /oracle/<SID>/sapreorg &prompt.root; mkdir install -&prompt.root; cd install +&prompt.root; cd install Then the install-script is started, which will copy nearly all the relevant files into the install-directory: - /oracle/IDS/sapreorg/KERNEL/UNIX/INSTTOOL.SH + &prompt.root; /oracle/<SID>/sapreorg/KERNEL/UNIX/INSTTOOL.SH - As this is an IDES-Installation with a fully customized - SAP R/3 Demo-System, we have six instead of just three + The IDES-Installation (4.6B) comes with a fully customized + SAP R/3 Demo-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 an IDES central instance, so copy - the corresponding CENTRDB.R3S from the EXPORT1 directory, - otherwise R3SETUP will only ask for three EXPORT-CDs. + 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 is CENTRAL.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 DB-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 ora<sid> and + <sid>adm (and for + root at least during installation + steps performed as root). It is also + possible to adjust the installed profile- and login-scripts of + both users that are installed during + SAP-installation. - - Start R3SETUP + + Start R3SETUP 4.6B Make sure LD_LIBRARY_PATH is set correctly: - &prompt.root; export LD_LIBRARY_PATH=/oracle/IDS/lib:/sapmnt/IDS/exe:/oracle/805_32/lib + &prompt.root; export LD_LIBRARY_PATH=/oracle/IDS/lib:/sapmnt/IDS/exe:/oracle/805_32/lib - Start R3SETUP as user root from installation - directory: + Start R3SETUP as root from + installation directory: &prompt.root; cd /oracle/IDS/sapreorg/install -&prompt.root; ./R3SETUP -f CENTRDB.R3S +&prompt.root; ./R3SETUP -f CENTRDB.R3S The script then asks some questions (defaults in brackets, followed by actual input): @@ -1880,15 +2035,15 @@ options SEMUME=100 #number of UNDO keys - If I had not copied the CDs to the different locations, + If you had not copied the CDs to the different locations, then the SAP-Installer cannot find the CD needed (identified by the LABEL.ASC-File on CD) and would - then ask you to insert / mount the CD and confirm or enter + 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 my case, it requested EXPORT4 again (but - indicated the correct key (6_LOCATI ON, then 7_LOCATION + indicated the correct key (6_LOCATION, then 7_LOCATION etc.), so one can just continue with entering the correct values. Do not get irritated. @@ -1896,6 +2051,148 @@ options SEMUME=100 #number of UNDO keys should go straight through up to the point where the Oracle database software needs to be installed. + + + 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: + + &prompt.root; export LD_LIBRARY_PATH=/sapmnt/PRD/exe:/oracle/PRD/817_32/lib + + Start R3SETUP as user root from installation directory: + + &prompt.root; cd /oracle/PRD/sapreorg/install +&prompt.root; ./R3SETUP -f CENTRAL.R3S + + The script then asks some questions (defaults in brackets, + followed by actual input): + + + + + + Question + Default + Input + + + + + Enter SAP System ID + [C11] + PRD<ret> + + + Enter SAP Instance Number + [00] + <ret> + + + Enter SAPMOUNT Directory + [/sapmnt] + <ret> + + + Enter name of SAP central host + [majestix] + <ret> + + + Enter Database System ID + [PRD] + PRD<ret> + + + Enter name of SAP db host + [majestix] + <ret> + + + Select character set + [1] (WE8DEC) + <ret> + + + Enter Oracle server version (2) Oracle 8.1.7 + + 2<ret> + + + Extract Oracle Client archive + [1] (Yes, extract) + <ret> + + + Enter path to KERNEL CD + [/sapcd] + /oracle/PRD/sapreorg/KERNEL + + + Enter amount of RAM for SAP + DB + 2044 + 1800<ret> (in Megabytes) + + + Service Entry Message Server + [3600] + <ret> + + + Enter Group-ID of sapsys + [100] + <ret> + + + Enter Group-ID of oper + [101] + <ret> + + + Enter Group-ID of dba + [102] + <ret> + + + Enter User-ID of oraprd + [1002] + <ret> + + + Enter User-ID of prdadm + [1000] + <ret> + + + LDAP support + + 3<ret> (no support) + + + Installation step completed + [1] (continue) + <ret> + + + Choose installation service + [1] (DB inst,file) + <ret> + + + + + + So far, creation of users gives an error during + installation in phases OSUSERDBSID_IND_ORA (for creating + user ora<sid>) and + OSUSERSIDADM_IND_ORA (creating user + <sid>adm). + + Apart from some problems mentioned below, everything + should go straight through up to the point where the Oracle + database software needs to be installed. + @@ -1946,7 +2243,7 @@ options SEMUME=100 #number of UNDO keys &prompt.root; export ORACLE_TERM=xterm &prompt.root; export ORACLE_HOME=/oracle/IDS &prompt.root; cd /ORACLE_HOME/orainst_sap -&prompt.root; ./orainst +&prompt.root; ./orainst Confirm all Screens with Enter until the software is installed, except that one has to deselect the @@ -1961,7 +2258,7 @@ options SEMUME=100 #number of UNDO keys from an Oracle 8.0.5 PreProduction release, after the first attempt at getting the version from the RDBMS-CD working, - failed, and finding / accessing the correct RPMs was a + failed, and finding and accessing the correct RPMs was a nightmare at that time. @@ -1981,6 +2278,13 @@ options SEMUME=100 #number of UNDO keys + + 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/ + + Continue with SAP R/3 Installation @@ -2000,10 +2304,9 @@ options SEMUME=100 #number of UNDO keys 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 from EXPORT1 to - EXPORT6 (remember, it is an IDES system, otherwise it would - only be EXPORT1 to EXPORT3) with R3load into the - database. + 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 @@ -2048,20 +2351,32 @@ options SEMUME=100 #number of UNDO keys At this point I had a few problems with - dipgntab. + dipgntab during the 4.6B + installation. Listener Start the Oracle-Listener as user - oraids (ora<sid>) as follows: + ora<sid> as follows: - umask 0; lsnrctl start + &prompt.user; umask 0; lsnrctl start Otherwise you might get ORA-12546 as the sockets will not have the correct permissions. See SAP note 072984. + + + 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. + If you don't need MNLS, it is still necessary to check + table TCPDB and initializing it if this hasn't been done. See + SAP note 0015023 and 0045619 for further information. + @@ -2070,22 +2385,21 @@ options SEMUME=100 #number of UNDO keys Request SAP R/3 License Key - This is needed, as the temporary license is only valid for - four weeks. Do not forget to enter the correct Operating System: - (X) Other: FreeBSD 4.3 Stable. First get - the hardware key. Log on as user idsadm and - call saplicense: + 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: &prompt.root; /sapmnt/IDS/exe/saplicense -get - Calling saplicense without options - gives a list of options. Upon receiving the license key, it can - be installed using + Calling saplicense without options gives + a list of options. Upon receiving the license key, it can be + installed using &prompt.root; /sapmnt/IDS/exe/saplicense -install - You are then required to enter the following - values: + You are then required to enter the following values: SAP SYSTEM ID = <SID, 3 chars> CUSTOMER KEY = <hardware key, 11 chars> @@ -2149,13 +2463,11 @@ LICENSE KEY = <license key, 24 chars> Edit init<sid>.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 + 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, I changed the following - values: + brbackup, I changed the following values: compress = hardware archive_function = copy_delete_save @@ -2173,7 +2485,7 @@ tape_address_rew = /dev/sa0 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 one needs to + are then deleted. This prevents lots of trouble if you need to recover the database, and one of the archive-tapes has gone bad. @@ -2192,9 +2504,7 @@ tape_address_rew = /dev/sa0 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 + hardware compression), the value is slightly lower than the actual value. tape_address The non-rewindable @@ -2208,7 +2518,7 @@ tape_address_rew = /dev/sa0 Configuration Issues after Installation The following SAP-parameters should be tuned after - installation: + installation (examples for IDES 46B, 1GB memory): @@ -2299,34 +2609,73 @@ tape_address_rew = /dev/sa0 Problems During Installation + + Restart R3SETUP after fixing a problem + + R3SETUP stops if it encounters an error. If you have + looked at the corresponding logfiles and fixed the error, + you have to start R3SETUP again, usually selecting REPEAT + as option for the last step R3SETUP complained about. + + To restart R3SETUP, just start it with the corresponding + R3S-file: + &prompt.root; ./R3SETUP -f CENTRDB.R3S + for 4.6B, or with + &prompt.root; ./R3SETUP -f CENTRAL.R3S + for 4.6C, no matter whether the error occured + with CENTRAL.R3s or + DATABASE.R3S. + + 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. + Don't forget to also start the oracle listener again (as + ora<sid> with + umask 0; lsnrctl start) if it was also + stopped (for example due to a necessary reboot of the + system). + + + OSUSERSIDADM_IND_ORA During R3SETUP - If R3SETUP complains at this stage, edit file - CENTRDB.R3S. Locate [OSUSERSIDADM_IND_ORA] and edit the - following values: + If R3SETUP complains at this stage, edit the + template file R3SETUP used at that time + (CENTRDB.R3S (4.6B) or either + CENTRAL.R3S or + DATABASE.R3S (4.6C)). + Locate [OSUSERSIDADM_IND_ORA] or search for the + only STATUS=ERROR-entry + and edit the following values: - HOME=/home/idsadm (was empty) + HOME=/home/<sid>adm (was empty) STATUS=OK (had status ERROR) - Then you can restart R3SETUP with: - - &prompt.root; ./R3SETUP -f CENTRDB.R3S + Then you can restart R3SETUP again. OSUSERDBSID_IND_ORA During R3SETUP - Possibly R3SETUP also complains at this stage. Just edit - CENTRDB.R3S. Locate [OSUSERDBSID_IND_ORA] and edit the - following value in that section: + 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 just restart R3SETUP again: - - &prompt.root; ./R3SETUP -f CENTRDB.R3S + Then restart R3SETUP. @@ -2364,57 +2713,97 @@ Sat May 5 14:23:22 2001 *** 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): + 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 - + abap/set_etct_env_at_new_mode = 0 +install/collate/active = 0 +rscp/TCP0B = TCP0B - Restart the SAP system. Now one can connect to the + Restart the SAP system. Now you can connect to the system, even though country-specific 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 SAP system can be - restarted. + removed from DEFAULT.PFL and the SAP + system can be restarted. + + + + + ORA-00001 + This error only happened with + Oracle 8.1.7 on FreeBSD 4.5. + 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. + + + + 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 example + startsap_majestix_00) as user + prdadm. + + A possible workaround is to start the database as user + oraprd instead + with svrmgrl: + + &prompt.user; svrmgrl +SVRMGR> connect internal; +SVRMGR> startup; +SVRMGR> exit - ORA-12546. Start Listener with Correct Permissions + ORA-12546 (start Listener with Correct Permissions) Start the Oracle Listener as user oraids with the following commands: &prompt.root; umask 0; lsnrctl start - Otherwise one might get ORA-12546 as the sockets will not + Otherwise you might get ORA-12546 as the sockets will not have the correct permissions. See SAP note 0072984. + + ORA-27102 (out of memory) + + This error happend whilst trying to use values for + MAXDSIZ and DFLDSIZ + greater than 1GB (1024x1024x1024). Additionally, I got + Linux Error 12: Cannot allocate memory. + + [DIPGNTAB_IND_IND] During R3SETUP In general, see SAP note 0130581 (R3SETUP step - DIPGNTAB - terminates). During this specific installation, for some - reasons the installation process was not using the proper - SAP system name "IDS", but the empty string "" instead. This - lead to some minor problems with accessing directories, as - the paths are generated dynamically using <sid> (in - this case IDS). So instead of accessing: + DIPGNTAB terminates). During the + IDES-specific installation, for some reasons the installation + process was not using the proper SAP system name "IDS", but + the empty string "" instead. This lead 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 path were used: + the following paths were used: /usr/sap//SYS/... -/usr/sap/D00i +/usr/sap/D00 To continue with the installation, I created a link and an additional directory: @@ -2427,16 +2816,25 @@ drwxr-xr-x 3 idsadm sapsys 512 May 5 11:20 D00 drwxr-x--x 5 idsadm sapsys 512 May 5 11:35 IDS lrwxr-xr-x 1 root sapsys 7 May 5 11:35 SYS -> IDS/SYS drwxrwxr-x 2 idsadm sapsys 512 May 5 13:00 tmp -drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans +drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans I also found SAP notes (0029227 and 0008401) describing - this behavior. + this behavior. I did not encounter any of these problems with + the SAP 4.6C-Installation. [RFCRSWBOINI_IND_IND] During R3SETUP - Set STATUS of the offending step from ERROR to OK (file + 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 @@ -2447,12 +2845,56 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans [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. - Set STATUS of the offending step from ERROR to OK (file + 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. - See SAP note 0162266 for further information. + RADDBDIF from transaction SE38. + + + + sigaction sig31: File size limit exceeded + + This error occured 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 won't 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 can't connect to the SAP-System, + look at the corresponding logfiles which can be found + at /usr/sap/<SID>/DVEBMGS<nr>/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 + + + + + Start of saposcol failed. + There are some problems with 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 doesn't collect all the data (many calls will + just return 0, for example for CPU useage).