From owner-freebsd-doc Fri Apr 19 16:33:53 2002 Delivered-To: freebsd-doc@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8274C37B4A3 for ; Fri, 19 Apr 2002 16:30:03 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g3JNU3s87652; Fri, 19 Apr 2002 16:30:03 -0700 (PDT) (envelope-from gnats) Received: from firewall.solit-ag.de (firewall.solit-ag.de [212.184.102.1]) by hub.freebsd.org (Postfix) with ESMTP id 4507F37B492 for ; Fri, 19 Apr 2002 16:29:18 -0700 (PDT) Received: (from root@localhost) by firewall.solit-ag.de (8.11.6/8.11.6) id g3JNTHj00893; Sat, 20 Apr 2002 01:29:17 +0200 (CEST) (envelope-from hk) Message-Id: <200204192329.g3JNTHj00893@firewall.solit-ag.de> Date: Sat, 20 Apr 2002 01:29:17 +0200 (CEST) From: Holger Kipp Reply-To: Holger Kipp To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: docs/37263: Updated chapter in Handbook: Installing SAP R/3 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 37263 >Category: docs >Synopsis: Updated chapter in Handbook: Installing SAP R/3 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Fri Apr 19 16:30:03 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Holger Kipp >Release: FreeBSD 4.5-STABLE i386 >Organization: >Environment: System: FreeBSD bsd.intern 4.5-STABLE FreeBSD 4.5-STABLE #11: Tue Mar 12 14:53:30 CET 2002 root@bsd.intern:/usr/obj/usr/src/sys/BSD i386 >Description: I updated section 20.6 in the FreeBSD Handbook (Installing SAP R/3) so it now also contains a description for the installation of SAP 4.6C with Oracle 8.1.7 on FreeBSD 4.5-stable (the other was SAP R/3 4.6B IDES with Oracle 8.0.5 on FreeBSD 4.3-stable). >How-To-Repeat: Install SAP R/3 4.6C SR2 on a freshly installed FreeBSD 4.5-stable and write down everything you had to do, including the problems encountered and what solutions have been found. >Fix: Apply the following diff to doc/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml,v 1.66 2002/03/27 01:16:54 keramida: 936c936 < Original version converted to SGML by --- > Converted to SGML by 941c941 < Installing SAP R/3 --- > Installing SAP R/3 (4.6B - IDES) 956,967c956,960 < 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 < --- > 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. 980d972 < 987a980,1022 > > > > > Name Number Description > > > > > KERNEL 51009113 SAP Kernel Oracle / > Installation / AIX, Linux, Solaris > > > RDBMS 51007558 Oracle / RDBMS 8.0.5.X / > Linux > > > EXPORT1 51010208 IDES / DB-Export / Disc > 1 of 6 > > > EXPORT2 51010209 IDES / DB-Export / Disc > 2 of 6 > > > EXPORT3 51010210 IDES / DB-Export / > Disc3 of 6 > > > EXPORT4 51010211 IDES / DB-Export / > Disc4 of 6 > > > EXPORT5 51010212 IDES / DB-Export / > Disc5 of 6 > > > EXPORT6 51010213 IDES / DB-Export / > Disc6 of 6 > > > > 989,1095c1024,1028 < < SAP R/3 4.6B, Oracle 8.0.5 < < < < < < Name Number Description < < < < < KERNEL 51009113 SAP Kernel Oracle / < Installation / AIX, Linux, Solaris < < < RDBMS 51007558 Oracle / RDBMS 8.0.5.X / < Linux < < < EXPORT1 51010208 IDES / DB-Export / < Disc 1 of 6 < < < EXPORT2 51010209 IDES / DB-Export / < Disc 2 of 6 < < < EXPORT3 51010210 IDES / DB-Export / < Disc 3 of 6 < < < EXPORT4 51010211 IDES / DB-Export / < Disc 4 of 6 < < < EXPORT5 51010212 IDES / DB-Export / < Disc 5 of 6 < < < EXPORT6 51010213 IDES / DB-Export / < Disc 6 of 6 < < < < < < 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 < 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 one 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 (his 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). < < < --- > 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 > RELEASE). 1105,1201c1038,1076 < < SAP R/3 4.6B, Oracle 8.0.5 < < < < < < Number < Title < < < < < 0171356 SAP Software on Linux: Essential < Comments < < < 0201147 INST: 4.6C R/3 Inst. on UNIX - < Oracle < < < 0373203 Update / Migration Oracle 8.0.5 --> < 8.0.6/8.1.6 LINUX < < < 0072984 Release of Digital UNIX 4.0B for < Oracle < < < 0130581 R3SETUP step DIPGNTAB terminates < < < 0144978 Your system has not been installed < correctly < < < 0162266 Questions and tips for R3SETUP on Windows < NT / W2K < < < < < < < < 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 < < < < < --- > > > > > Number > Title > > > > > 0171356 SAP Software auf Linux: grundlegenden > Anmerkungen > > > 0201147 INST: 4.6C R/3 Inst. on UNIX - > Oracle > > > 0373203 Update / Migration Oracle 8.0.5 --> > 8.0.6/8.1.6 LINUX > > > 0072984 Release of Digital UNIX 4.0B for > Oracle > > > 0130581 R3SETUP step DIPGNTAB terminates > > > 0144978 Your system has not been installed > correctly > > > 0162266 Questions and tips for R3SETUP on Windows > NT / W2K > > > > 1208,1210c1083,1084 < 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: --- > The following equipment is sufficient for a > SAP R/3 System (4.6B): 1243c1117 < and ECC-RAM is recommended. The large amount of hard disc --- > and ECC-RAM is recommended. The large amount of Hard disc 1245,1269c1119,1128 < 27 GB of database files during installation. This space is < also sufficient for initial production systems and application < date. < < < 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 discs < (mirrored) and four 36GB hard discs (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 discs (mirrored) and four 36GB hard discs < (RAID level 5). < --- > 27 GB of database files during installation. Usually after > installation it is then necessary to extend some > tablespaces. > > 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). 1274c1133 < Installation of FreeBSD --- > Installation of FreeBSD 4.3-STABLE 1276,1288c1135,1150 < 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). < < < 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): --- > First I installed FreeBSD 4.3 stable. I did the > default-installation via FTP. > > > 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). > > &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: 1347,1350c1209,1212 < Configure and initialize the two logical drives < with the Mylex- or PERC/3 RAID software beforehand. < The software can be started during the < boot phase of the PC. --- > 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. 1365,1367c1227,1230 < FreeBSD, I had my own script located in /etc/cvsup. To set < up CVSup for FreeBSD 4.3+ do < the following as user root: --- > 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: 1400,1406c1263,1273 < After downloading the lastest stable-sources, it is < necessary to recompile world and the custom kernel (here the < necessary steps are only summarized). The first < step is to customize the kernel configuration file. As the < computer is named troubadix, the natural < name for the config file also is < TROUBADIX: --- > 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: 1418,1434c1285,1297 < below which are required for both SAP R/3 < and Oracle. To create and install < the new kernel together with all other FreeBSD programms, do the < following (or something similar) as user < root: < < &prompt.root; cd /usr/src < &prompt.root; make buildworld < &prompt.root; make buildkernel KERNCONF=TROUBADIX < &prompt.root; make installkernel KERNCONF=TROUBADIX < &prompt.root; make installworld < &prompt.root; mergemaster < &prompt.root; reboot < < For older releases of FreeBSD (including 4.3), the necessary < steps to create and install a new kernel are slightly more < complicated and will not be explained here. --- > 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. 1442,1447c1305,1313 < 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. --- > 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 > 1451,1454c1317 < First the Linux base-system needs to be installed (as < root). For SAP R/3 < IDES on FreeBSD 4.3-STABLE, I used: < --- > First the Linux base-system needs to be installed (as root): 1456,1462c1319 < &prompt.root; make package < < For SAP R/3 4.6C SR2 on FreeBSD 4.5-STABLE < the slightly newer linux_base-62 was used instead: < < &prompt.root; cd /usr/ports/emulators/linux_base-62 < &prompt.root; make package --- > &prompt.root; make package 1469,1471c1326 < The Linux development is needed, if you want to install < Oracle on FreeBSD according to the < corresponding description in the handbook: --- > Next, the Linux development is needed: 1476,1481d1330 < 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 one is using the < Oracle tarball from a linux system. < 1489,1495c1338,1356 < 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: --- > 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. > > 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: 1496a1358,1360 > &prompt.root; rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm <package_name> > > except for the pam package, which I forced with 1501c1365 < For Oracle 8.0.5 to run the --- > For Oracle to run the 1512,1519d1375 < < < 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. < 1556,1558c1412,1413 < It is also necessary to created some links. Otherwise < the SAP-Installer will complain, as it is checking the < created links: --- > I also created some links, so FreeBSD will also find the > correct path: 1563,1581d1417 < < 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' 1594,1596c1430 < installation I used IDS, for the < 4.6C SR2 installation PRD, as that system < is intended for production use. We have --- > installation I used IDS. We have 1652c1486 < idsadm/prdadm --- > idsadm 1660c1494 < oraids/oraprd --- > oraids 1674c1508 < Name: <sid>adm --- > Name: idsadm <sid>adm 1676c1510 < Fullname: SAP Administrator <SID> --- > Fullname: SAP IDES Administrator 1681,1682c1515,1516 < HOME: /home/<sid>adm < Shell: bash (/compat/linux/bin/bash) --- > HOME: /home/idsadm /home/<sid>adm > Shell: /bin/sh 1686c1520 < Name: ora<sid> --- > Name: oraids ora<sid> 1688c1522 < Fullname: Oracle Administrator <SID> --- > Fullname: Oracle IDES Administrator 1693,1694c1527,1528 < HOME: /oracle/<sid> < Shell: bash (/compat/linux/bin/bash) --- > HOME: /oracle/IDS /oracle/<sid> > Shell: /bin/sh 1711c1545 < First we will set owners and rights of some directories (as --- > First we will set owners and right of some directories (as 1717,1718c1551,1552 < &prompt.root; chown <sid>adm:sapsys /compat/linux/usr/sap < &prompt.root; chmod 775 /compat/linux/usr/sap --- > &prompt.root; chown idsadm:sapsys /compat/linux/usr/sap > &prompt.root; chmow 775 /compat/linux/usr/sap 1720,1723c1554,1555 < Second we will create directories as user < ora<sid>. These < will all be subdirectories of < /oracle/<SID>: --- > Second we will create directories as user ora<sid>. These > will all be subdirectories of /oracle/IDS: 1725,1726c1557 < &prompt.root; su - ora<sid> < &prompt.root; cd /oracle/<SID> --- > &prompt.root; su - oraids 1732,1743d1562 < 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 < 1745c1564 < <sid>adm: --- > idsadm (<sid>adm): 1747c1566 < &prompt.root; su - <sid>adm --- > &prompt.root; su - idsadm 1749c1568 < &prompt.root; mkdir <SID> --- > &prompt.root; mkdir IDS 1768,1774c1587,1591 < < 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 < sapms<SID> 3600/tcp # SAP Message Server. 3600 + Instance-Number < sapgw00s 4800/tcp # SAP Secure Gateway 4800 + 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 1797,1802d1613 < 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 < 1819,1820c1630 < options DFLDSIZ="(1024*1024*1024)" < # System V options needed. --- > options DFLDSIZ="(1024*1024*1024)" # System V options needed. 1823,1825c1633,1634 < #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 SHMMNI=256 #max number of shared memory ident if. > options SHMSEG=100 #max shared mem.segs per process 1827,1830c1636,1639 < 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 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 1832,1835c1641,1644 < 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 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 1839,1849c1648 < 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. < It looks like there are some problems with linux < programs having more than 1GB of memory, so I had to leave < MAXDSIZ at 1GB maximum. Otherwise, strange errors like < ORA-27102: out of memory and < Linux Error: 12: Cannot allocate memory < might happen. --- > HP-UX-section (32-bit) for further information. 1865c1664 < /oracle/<SID>/sapreorg/<cd-name> --- > /oracle/IDS/sapreorg/<cd-name> 1871,1878c1670,1672 < 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: --- > EXPORT6. All the > filenames should be in capital letters, otherwise use the -g > option for mounting. So use the following commands: 1881c1675 < &prompt.root; cp -R /mnt/* /oracle/<SID>/sapreorg/<cd-name> --- > &prompt.root; cp -R /mnt/* /oracle/IDS/sapreorg/<cd-name> 1890c1684 < &prompt.root; cd /oracle/<SID>/sapreorg --- > &prompt.root; cd /oracle/IDS/sapreorg 1897c1691 < &prompt.root; /oracle/<SID>/sapreorg/KERNEL/UNIX/INSTTOOL.SH --- > /oracle/IDS/sapreorg/KERNEL/UNIX/INSTTOOL.SH 1899,1915c1693,1699 < 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 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. --- > As this is an IDES-Installation with a fully customized > SAP R/3 Demo-System, we have 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. 1918,1919c1702,1703 < < Start R3SETUP 4.6B --- > > Start R3SETUP 1925,1934d1708 < 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 oraids and < idsadm. It is also possible to < adjust the installed profile- and login-scripts of < both users. < 2116c1890 < indicated the correct key (6_LOCATION, then 7_LOCATION --- > indicated the correct key (6_LOCATI ON, then 7_LOCATION 2124,2278d1897 < < < 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 < < 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 < oraprd, prdadm < and (at least during installation phase) < root. It is also possible to < adjust the profile- and login-scripts of < both users that are installed during < SAP-installation. < < 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. < 2364,2370d1982 < < 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/ < < 2438,2439c2050 < dipgntab during the 4.6B < installation. --- > dipgntab. 2446c2057 < ora<sid> as follows: --- > oraids (ora<sid>) as follows: 2453,2463d2063 < < < 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. < 2575c2175 < are then deleted. This prevents lots of trouble if you need to --- > are then deleted. This prevents lots of trouble if one needs to 2610c2210 < installation (examples for IDES 46B, 1GB memory): --- > installation: 2701,2728d2300 < < Restart R3SETUP after fixing a problem < R3SETUP stops if it encounters an error. If you have < looked at the corresponding logfile 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 user ora<sid> with < umask 0; lsnrctl start) if it was also < stopped (for example due to a reboot of the system). < < 2732,2739c2304,2306 < 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: --- > If R3SETUP complains at this stage, edit file > CENTRDB.R3S. Locate [OSUSERSIDADM_IND_ORA] and edit the > following values: 2741c2308 < HOME=/home/<sid>adm (was empty) --- > HOME=/home/idsadm (was empty) 2745c2312,2314 < Then you can restart R3SETUP again. --- > Then you can restart R3SETUP with: > > &prompt.root; ./R3SETUP -f CENTRDB.R3S 2751,2760c2320,2322 < 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: --- > Possibly R3SETUP also complains at this stage. Just edit > CENTRDB.R3S. Locate [OSUSERDBSID_IND_ORA] and edit the > following value in that section: 2764c2326,2328 < Then restart R3SETUP. --- > Then just restart R3SETUP again: > > &prompt.root; ./R3SETUP -f CENTRDB.R3S 2813c2377 < Restart the SAP system. Now you can connect to the --- > Restart the SAP system. Now one can connect to the 2822,2850d2385 < < 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 < < < 2852c2387 < ORA-12546 (start Listener with Correct Permissions) --- > ORA-12546. Start Listener with Correct Permissions 2859c2394 < Otherwise you might get ORA-12546 as the sockets will not --- > Otherwise one might get ORA-12546 as the sockets will not 2863,2872d2397 < < 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 < with values greater than 1 GB. < < 2878c2403 < terminates). During the IDES-specific installation, for some --- > terminates). During this specific installation, for some 2882c2407 < the paths are generated dynamically using <SID> (in --- > the paths are generated dynamically using <sid> (in 2888c2413 < the following paths were used: --- > the following path were used: 2891c2416 < /usr/sap/D00 --- > /usr/sap/D00i 2907,2908c2432 < this behavior. I did not encounter any of these problems with < the SAP 4.6C-Installation. --- > this behavior. 2914,2922c2438 < 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 --- > Set STATUS of the offending step from ERROR to OK (file 2933,2935d2448 < Here the same restrictions apply: Make sure by looking < through the logfiles, that this error is not caused by some < previous problems. 2937,2938c2450 < If you can confirm that it is the correct SAP-Note, just < set STATUS of the offending step from ERROR to OK (file --- > Set STATUS of the offending step from ERROR to OK (file 2943,2983d2454 < < < < 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). >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message