Date: Sat, 20 Apr 2002 01:29:17 +0200 (CEST) From: Holger Kipp <hk@alogis.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: docs/37263: Updated chapter in Handbook: Installing SAP R/3 Message-ID: <200204192329.g3JNTHj00893@firewall.solit-ag.de>
next in thread | raw e-mail | index | archive | help
>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
< <contrib>Original version converted to SGML by </contrib>
---
> <contrib>Converted to SGML by </contrib>
941c941
< <title>Installing SAP R/3</title>
---
> <title>Installing SAP R/3 (4.6B - IDES)</title>
956,967c956,960
< <application>SAP R/3-System</application>
< with <application>Oracle Database</application>
< for Linux onto a FreeBSD machine, including the installation
< of FreeBSD and <application>Oracle</application>. Two different
< configurations will be described:</para>
<
< <itemizedlist>
< <listitem><para><application>SAP R/3 4.6B (IDES)</application> with
< <application>Oracle 8.0.5</application> on FreeBSD 4.3-STABLE</para></listitem>
< <listitem><para><application>SAP R/3 4.6C</application> with
< <application>Oracle 8.1.7</application> on FreeBSD 4.5-STABLE</para></listitem>
< </itemizedlist>
---
> <application>SAP R/3 4.6B IDES-System</application>
> with <application>Oracle 8.0.5</application>
> for Linux onto a FreeBSD 4.3 machine, including the installation
> of FreeBSD 4.3-STABLE and
> <application>Oracle 8.0.5</application>.</para>
980d972
<
987a980,1022
> <informaltable>
> <tgroup cols=3>
> <thead>
> <row>
> <entry>Name</entry> <entry>Number</entry> <entry>Description</entry>
> </row>
> </thead>
> <tbody>
> <row>
> <entry>KERNEL</entry> <entry>51009113</entry> <entry>SAP Kernel Oracle /
> Installation / AIX, Linux, Solaris</entry>
> </row>
> <row>
> <entry>RDBMS</entry> <entry>51007558</entry> <entry>Oracle / RDBMS 8.0.5.X /
> Linux</entry>
> </row>
> <row>
> <entry>EXPORT1</entry> <entry>51010208</entry> <entry>IDES / DB-Export / Disc
> 1 of 6</entry>
> </row>
> <row>
> <entry>EXPORT2</entry> <entry>51010209</entry> <entry>IDES / DB-Export / Disc
> 2 of 6</entry>
> </row>
> <row>
> <entry>EXPORT3</entry> <entry>51010210</entry> <entry>IDES / DB-Export /
> Disc3 of 6</entry>
> </row>
> <row>
> <entry>EXPORT4</entry> <entry>51010211</entry> <entry>IDES / DB-Export /
> Disc4 of 6</entry>
> </row>
> <row>
> <entry>EXPORT5</entry> <entry>51010212</entry> <entry>IDES / DB-Export /
> Disc5 of 6</entry>
> </row>
> <row>
> <entry>EXPORT6</entry> <entry>51010213</entry> <entry>IDES / DB-Export /
> Disc6 of 6</entry>
> </row>
> </tbody>
> </tgroup>
> </informaltable>
989,1095c1024,1028
< <sect3 id="software-46b">
< <title>SAP R/3 4.6B, Oracle 8.0.5</title>
<
< <informaltable>
< <tgroup cols=3>
< <thead>
< <row>
< <entry>Name</entry> <entry>Number</entry> <entry>Description</entry>
< </row>
< </thead>
< <tbody>
< <row>
< <entry>KERNEL</entry> <entry>51009113</entry> <entry>SAP Kernel Oracle /
< Installation / AIX, Linux, Solaris</entry>
< </row>
< <row>
< <entry>RDBMS</entry> <entry>51007558</entry> <entry>Oracle / RDBMS 8.0.5.X /
< Linux</entry>
< </row>
< <row>
< <entry>EXPORT1</entry> <entry>51010208</entry> <entry>IDES / DB-Export /
< Disc 1 of 6</entry>
< </row>
< <row>
< <entry>EXPORT2</entry> <entry>51010209</entry> <entry>IDES / DB-Export /
< Disc 2 of 6</entry>
< </row>
< <row>
< <entry>EXPORT3</entry> <entry>51010210</entry> <entry>IDES / DB-Export /
< Disc 3 of 6</entry>
< </row>
< <row>
< <entry>EXPORT4</entry> <entry>51010211</entry> <entry>IDES / DB-Export /
< Disc 4 of 6</entry>
< </row>
< <row>
< <entry>EXPORT5</entry> <entry>51010212</entry> <entry>IDES / DB-Export /
< Disc 5 of 6</entry>
< </row>
< <row>
< <entry>EXPORT6</entry> <entry>51010213</entry> <entry>IDES / DB-Export /
< Disc 6 of 6</entry>
< </row>
< </tbody>
< </tgroup>
< </informaltable>
<
< <para>Additionally, I used the <application>Oracle 8
< Server</application> (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).</para>
<
< </sect3>
< <sect3 id="software-46c">
< <title>SAP R/3 4.6C SR2, Oracle 8.1.7</title>
<
< <informaltable>
< <tgroup cols=3>
< <thead>
< <row>
< <entry>Name</entry> <entry>Number</entry> <entry>Description</entry>
< </row>
< </thead>
< <tbody>
< <row>
< <entry>KERNEL</entry> <entry>51014004</entry> <entry>SAP Kernel Oracle /
< SAP Kernel Version 4.6D / DEC, Linux</entry>
< </row>
< <row>
< <entry>RDBMS</entry> <entry>51012930</entry> <entry>Oracle 8.1.7/ RDBMS /
< Linux</entry>
< </row>
< <row>
< <entry>EXPORT1</entry> <entry>51013953</entry> <entry>Release 4.6C SR2 / Export
< / Disc 1 of 4</entry>
< </row>
< <row>
< <entry>EXPORT1</entry> <entry>51013953</entry> <entry>Release 4.6C SR2 / Export
< / Disc 2 of 4</entry>
< </row>
< <row>
< <entry>EXPORT1</entry> <entry>51013953</entry> <entry>Release 4.6C SR2 / Export
< / Disc 3 of 4</entry>
< </row>
< <row>
< <entry>EXPORT1</entry> <entry>51013953</entry> <entry>Release 4.6C SR2 / Export
< / Disc 4 of 4</entry>
< </row>
< <row>
< <entry>LANG1</entry> <entry>51013954</entry> <entry>Release 4.6C SR2 /
< Language / DE, EN, FR / Disc 1 of 3</entry>
< </row>
< </tbody>
< </tgroup>
< </informaltable>
<
< <para>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).</para>
<
< </sect3>
<
---
> <para>Additionally, I used the <application>Oracle 8
> Server</application> (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).</para>
1105,1201c1038,1076
< <sect3 id="sap-notes-46b">
< <title>SAP R/3 4.6B, Oracle 8.0.5</title>
<
< <informaltable>
< <tgroup cols="2">
< <thead>
< <row>
< <entry>Number</entry>
< <entry>Title</entry>
< </row>
< </thead>
< <tbody>
< <row>
< <entry>0171356</entry> <entry>SAP Software on Linux: Essential
< Comments</entry>
< </row>
< <row>
< <entry>0201147</entry> <entry>INST: 4.6C R/3 Inst. on UNIX -
< Oracle</entry>
< </row>
< <row>
< <entry>0373203</entry> <entry>Update / Migration Oracle 8.0.5 -->
< 8.0.6/8.1.6 LINUX</entry>
< </row>
< <row>
< <entry>0072984</entry> <entry>Release of Digital UNIX 4.0B for
< Oracle</entry>
< </row>
< <row>
< <entry>0130581</entry> <entry>R3SETUP step DIPGNTAB terminates</entry>
< </row>
< <row>
< <entry>0144978</entry> <entry>Your system has not been installed
< correctly</entry>
< </row>
< <row>
< <entry>0162266</entry> <entry>Questions and tips for R3SETUP on Windows
< NT / W2K</entry>
< </row>
< </tbody>
< </tgroup>
< </informaltable>
< </sect3>
<
< <sect3 id="sap-notes-46c">
< <title>SAP R/3 4.6C, Oracle 8.1.7</title>
<
< <informaltable>
< <tgroup cols="2">
< <thead>
< <row>
< <entry>Number</entry>
< <entry>Title</entry>
< </row>
< </thead>
< <tbody>
< <row>
< <entry>0015023</entry> <entry>Initializing table TCPDB (RSXP0004)
< (EBCDIC)</entry>
< </row>
< <row>
< <entry>0045619</entry> <entry>R/3 with several languages or
< typefaces</entry>
< </row>
< <row>
< <entry>0171356</entry> <entry>SAP Software on Linux: Essential
< Comments</entry>
< </row>
< <row>
< <entry>0195603</entry> <entry>RedHat 6.1 Enterprise version:
< Known problems</entry>
< </row>
< <row>
< <entry>0212876</entry> <entry>The new archiving tool SAPCAR</entry>
< </row>
< <row>
< <entry>0300900</entry> <entry>Linux: Released DELL Hardware</entry>
< </row>
< <row>
< <entry>0377187</entry> <entry>RedHat 6.2: important remarks</entry>
< </row>
< <row>
< <entry>0387074</entry> <entry>INST: R/3 4.6C SR2 Installation on
< UNIX</entry>
< </row>
< <row>
< <entry>0387077</entry> <entry>INST: R/3 4.6C SR2 Inst. on UNIX -
< Oracle</entry>
< </row>
< <row>
< <entry>0387078</entry> <entry>SAP Software on UNIX: OS Dependencies
< 4.6C SR2</entry>
< </row>
< </tbody>
< </tgroup>
< </informaltable>
< </sect3>
---
> <informaltable>
> <tgroup cols="2">
> <thead>
> <row>
> <entry>Number</entry>
> <entry>Title</entry>
> </row>
> </thead>
> <tbody>
> <row>
> <entry>0171356</entry> <entry>SAP Software auf Linux: grundlegenden
> Anmerkungen</entry>
> </row>
> <row>
> <entry>0201147</entry> <entry>INST: 4.6C R/3 Inst. on UNIX -
> Oracle</entry>
> </row>
> <row>
> <entry>0373203</entry> <entry>Update / Migration Oracle 8.0.5 -->
> 8.0.6/8.1.6 LINUX</entry>
> </row>
> <row>
> <entry>0072984</entry> <entry>Release of Digital UNIX 4.0B for
> Oracle</entry>
> </row>
> <row>
> <entry>0130581</entry> <entry>R3SETUP step DIPGNTAB terminates</entry>
> </row>
> <row>
> <entry>0144978</entry> <entry>Your system has not been installed
> correctly</entry>
> </row>
> <row>
> <entry>0162266</entry> <entry>Questions and tips for R3SETUP on Windows
> NT / W2K</entry>
> </row>
> </tbody>
> </tgroup>
> </informaltable>
1208,1210c1083,1084
< <para>The following equipment is sufficient for the installation
< of a <application>SAP R/3 System</application>. For production
< use, a more exact sizing is of course needed:</para>
---
> <para>The following equipment is sufficient for a
> <application>SAP R/3 System</application> (4.6B):</para>
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. </para>
<
< <sect3 id="hardware-46b">
< <title>SAP R/3 4.6B, Oracle 8.0.5</title>
<
< <para>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).</para>
< </sect3>
<
< <sect3 id="hardware-46c">
< <title>SAP R/3 4.6C, Oracle 8.1.7</title>
<
< <para>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).</para>
< </sect3>
---
> 27 GB of database files during installation. Usually after
> installation it is then necessary to extend some
> tablespaces.</para>
>
> <para>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).</para>
1274c1133
< <title>Installation of FreeBSD</title>
---
> <title>Installation of FreeBSD 4.3-STABLE</title>
1276,1288c1135,1150
< <para>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).</para>
<
< <sect3 id="disk-layout">
< <title>Disk Layout</title>
<
< <para>To keep it simple, the same disk layout both for the
< <application>SAP R/3 46B-</application> and <application>SAP R/3 46C
< SR2-</application>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):</para>
---
> <para>First I installed FreeBSD 4.3 stable. I did the
> default-installation via FTP.</para>
>
> <sect3 id="install-via-ftp">
> <title>Installation via FTP</title> <para>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).</para>
>
> <screen>&prompt.root; <userinput>dd if=kern.flp of=/dev/fd0</userinput>
> &prompt.root; <userinput>dd if=mfsroot.flp of=/dev/fd0</userinput> </screen>
>
> <para>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:</para>
1347,1350c1209,1212
< <para>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.</para>
---
> <para>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.</para>
1365,1367c1227,1230
< FreeBSD, I had my own script located in /etc/cvsup. To set
< up <application>CVSup</application> for FreeBSD 4.3+ do
< the following as user <username>root</username>:</para>
---
> FreeBSD, I had my own script located in /etc/cvsup. Setting
> up <application>CVSup</application> for FreeBSD 4.3 is quite
> easy. As user
> <username>root</username> do the following:</para>
1400,1406c1263,1273
< <para>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 <hostid>troubadix</hostid>, the natural
< name for the config file also is
< <filename>TROUBADIX</filename>:</para>
---
> <para>The first thing to do is to install the sources.
> As user root, do the following:</para>
>
> <screen>&prompt.root; <userinput>cd /usr/src</userinput>
> &prompt.root; <userinput>make world</userinput> </screen>
>
> <para>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 <hostid>troubadix</hostid>, the natural name for the
> config file also is <filename>troubadix</filename>:</para>
1418,1434c1285,1297
< below which are required for both <application>SAP R/3</application>
< and <application>Oracle</application>. To create and install
< the new kernel together with all other FreeBSD programms, do the
< following (or something similar) as user
< <username>root</username>:</para>
<
< <screen>&prompt.root; <userinput>cd /usr/src</userinput>
< &prompt.root; <userinput>make buildworld</userinput>
< &prompt.root; <userinput>make buildkernel KERNCONF=TROUBADIX</userinput>
< &prompt.root; <userinput>make installkernel KERNCONF=TROUBADIX</userinput>
< &prompt.root; <userinput>make installworld</userinput>
< &prompt.root; <userinput>mergemaster</userinput>
< &prompt.root; <userinput>reboot</userinput></screen>
<
< <para>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.</para>
---
> below Creating the new kernel then requires:</para>
>
> <screen>&prompt.root; <userinput>cd /usr/src/sys/i386/conf</userinput>
> &prompt.root; <userinput>config TROUBADIX</userinput>
> &prompt.root; <userinput>cd /usr/src/sys/compile/TROUBADIX</userinput>
> &prompt.root; <userinput>make depend</userinput>
> &prompt.root; <userinput>make</userinput>
> &prompt.root; <userinput>make install</userinput> </screen>
>
>
> <para>After <command>make install</command> finished
> successfully, one should reboot the computer to have the new
> kernel available.</para>
1442,1447c1305,1313
< <para>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.</para>
---
> <para>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):</para>
>
> <itemizedlist>
> <listitem><para>ftp7.de.FreeBSD.org/pub/FreeBSD/distfiles/rpm</para></listitem>
> <listitem><para>ftp.redhat.com/pub/redhat/linux/6.1/en/os/i386/RedHat/RPMS</para></listitem>
> </itemizedlist>
1451,1454c1317
< <para>First the Linux base-system needs to be installed (as
< <username>root</username>). For <application>SAP R/3
< IDES</application> on FreeBSD 4.3-STABLE, I used:</para>
<
---
> <para>First the Linux base-system needs to be installed (as root):
1456,1462c1319
< &prompt.root; <userinput>make package</userinput> </screen>
<
< <para>For <application>SAP R/3 4.6C SR2</application> on FreeBSD 4.5-STABLE
< the slightly newer <filename>linux_base-62</filename> was used instead:</para>
<
< <screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_base-62</userinput>
< &prompt.root; <userinput>make package</userinput> </screen>
---
> &prompt.root; <userinput>make package</userinput> </screen></para>
1469,1471c1326
< <para>The Linux development is needed, if you want to install
< <application>Oracle</application> on FreeBSD according to the
< corresponding description in the handbook:</para>
---
> <para>Next, the Linux development is needed:</para>
1476,1481d1330
< <para>Linux Development has only been installed for the <application>SAP
< R/3 46B IDES-</application> installation. It is not needed, if
< the <application>Oracle DB</application> is not relinked on the
< FreeBSD system. This is the case, if one is using the
< <application>Oracle</application> tarball from a linux system.</para>
<
1489,1495c1338,1356
< <para>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 <application>SAP R/3 4.6C SR2</application> I
< directly forced the installation of pam rpm, which also
< works, so it seems the dependend packages are not needed:</para>
---
> <para>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.</para>
>
> <para>Anyway, here is the list of packages I installed:</para>
>
> <itemizedlist>
> <listitem><para>cracklib-2.7-5.i386.rpm</para></listitem>
> <listitem><para>cracklib-dicts-2.7-5.i386.rpm</para></listitem>
> <listitem><para>pwdb-0.60-1.i386.rpm</para></listitem>
> <listitem><para>pam-0.68-7.i386.rpm</para></listitem>
> </itemizedlist>
>
> <para>I installed these packages with the following
> command:</para>
1496a1358,1360
> <screen>&prompt.root; <userinput>rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm <package_name></userinput> </screen>
>
> <para>except for the pam package, which I forced with</para>
1501c1365
< <para>For <application>Oracle 8.0.5</application> to run the
---
> <para>For <application>Oracle</application> to run the
1512,1519d1375
<
< <sect3 id="linuxprocandfallbackelfbrand">
< <title>Some additional hints</title>
< <para>It might also be a good idea to add <filename>linprocfs</filename>
< to <filename>/etc/fstab</filename>. See <command>man linprocfs</command>.
< Another parameter to set is <emphasis>kern.fallback_elf_brand=3</emphasis>
< which is done in file <filename>/etc/sysctl.conf</filename>.
< </sect3>
1556,1558c1412,1413
< <para>It is also necessary to created some links. Otherwise
< the SAP-Installer will complain, as it is checking the
< created links:</para>
---
> <para>I also created some links, so FreeBSD will also find the
> correct path:</para>
1563,1581d1417
<
< <para>Possible error message during installation (here with
< System <emphasis>PRD</emphasis> and the
< <application>SAP R/3 4.6C SR2</application>
< installation):</para>
<
< <screen>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'</screen>
1594,1596c1430
< installation I used <emphasis>IDS</emphasis>, for the
< 4.6C SR2 installation <emphasis>PRD</emphasis>, as that system
< is intended for production use. We have
---
> installation I used <emphasis>IDS</emphasis>. We have
1652c1486
< <entry>idsadm/prdadm</entry>
---
> <entry>idsadm</entry>
1660c1494
< <entry>oraids/oraprd</entry>
---
> <entry>oraids</entry>
1674c1508
< <programlisting>Name: <sid>adm
---
> <programlisting>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)</programlisting>
---
> HOME: /home/idsadm /home/<sid>adm
> Shell: /bin/sh</programlisting>
1686c1520
< <programlisting>Name: ora<sid>
---
> <programlisting>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)</programlisting>
---
> HOME: /oracle/IDS /oracle/<sid>
> Shell: /bin/sh</programlisting>
1711c1545
< <para>First we will set owners and rights of some directories (as
---
> <para>First we will set owners and right of some directories (as
1717,1718c1551,1552
< &prompt.root; <userinput>chown <sid>adm:sapsys /compat/linux/usr/sap</userinput>
< &prompt.root; <userinput>chmod 775 /compat/linux/usr/sap</userinput> </screen>
---
> &prompt.root; <userinput>chown idsadm:sapsys /compat/linux/usr/sap</userinput>
> &prompt.root; <userinput>chmow 775 /compat/linux/usr/sap</userinput> </screen>
1720,1723c1554,1555
< <para>Second we will create directories as user
< <username>ora<sid></username>. These
< will all be subdirectories of
< <filename>/oracle/<SID></filename>:</para>
---
> <para>Second we will create directories as user ora<sid>. These
> will all be subdirectories of /oracle/IDS:</para>
1725,1726c1557
< <screen>&prompt.root; <userinput>su - ora<sid></userinput>
< &prompt.root; <userinput>cd /oracle/<SID></userinput>
---
> <screen>&prompt.root; <userinput>su - oraids</userinput>
1732,1743d1562
< <para>For the <application>Oracle 8.1.7-</application>installation
< some additional directories are needed:</para>
<
< <screen>&prompt.root; <userinput>su - ora<sid></userinput>
< &prompt.root; <userinput>cd /oracle</userinput>
< &prompt.root; <userinput>mkdir 805_32</userinput>
< &prompt.root; <userinput>mkdir client stage</userinput>
< &prompt.root; <userinput>mkdir client/80x_32</userinput>
< &prompt.root; <userinput>mkdir stage/817_32</userinput>
< &prompt.root; <userinput>cd /oracle/<SID></userinput>
< &prompt.root; <userinput>mkdir 817_32</userinput></screen>
<
1745c1564
< <username><sid>adm</username>:</para>
---
> <username>idsadm</username> (<sid>adm):</para>
1747c1566
< <screen>&prompt.root; <userinput>su - <sid>adm</userinput>
---
> <screen>&prompt.root; <userinput>su - idsadm</userinput>
1749c1568
< &prompt.root; <userinput>mkdir <SID></userinput>
---
> &prompt.root; <userinput>mkdir IDS</userinput>
1768,1774c1587,1591
< <programlisting>
< 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</programlisting>
---
> <programlisting>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</programlisting>
1797,1802d1613
< <para>Create the links like this:</para>
<
< <screen>&prompt.root; <userinput>cd /compat/linux/usr/share/locale</userinput>
< &prompt.root; <userinput>ln -s de_DE de_DE.ISO-8859-1</userinput>
< &prompt.root; <userinput>ln -s en_US en_US.ISO-8859-1</userinput></screen>
<
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</programlisting></para>
---
> 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</programlisting></para>
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 <application>SAP</application>
< and <application>Oracle</application>, therefore choose a larger
< number of shared memory pages.
< <note><para>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
< <emphasis>ORA-27102: out of memory</emphasis> and
< <emphasis>Linux Error: 12: Cannot allocate memory</emphasis>
< might happen.</para></note>
---
> HP-UX-section (32-bit) for further information.
1865c1664
< <programlisting>/oracle/<SID>/sapreorg/<cd-name></programlisting>
---
> <programlisting>/oracle/IDS/sapreorg/<cd-name></programlisting>
1871,1878c1670,1672
< <filename>EXPORT6</filename> for the 4.6B/IDES-installation, and
< <filename>KERNEL</filename>, <filename>RDBMS</filename>,
< <filename>DISK1</filename>, <filename>DISK2</filename>,
< <filename>DISK3</filename>, <filename>DISK4</filename> and
< <filename>LANG</filename> 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:</para>
---
> <filename>EXPORT6</filename>. All the
> filenames should be in capital letters, otherwise use the -g
> option for mounting. So use the following commands:</para>
1881c1675
< &prompt.root; <userinput>cp -R /mnt/* /oracle/<SID>/sapreorg/<cd-name></userinput>
---
> &prompt.root; <userinput>cp -R /mnt/* /oracle/IDS/sapreorg/<cd-name></userinput>
1890c1684
< <screen>&prompt.root; <userinput>cd /oracle/<SID>/sapreorg</userinput>
---
> <screen>&prompt.root; <userinput>cd /oracle/IDS/sapreorg</userinput>
1897c1691
< <screen>&prompt.root; /oracle/<SID>/sapreorg/KERNEL/UNIX/INSTTOOL.SH</screen>
---
> <para><filename>/oracle/IDS/sapreorg/KERNEL/UNIX/INSTTOOL.SH</filename></para>
1899,1915c1693,1699
< <para>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
< <filename>CENTRDB.R3S</filename> 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.</para>
<
< <para>The newer <application>SAP 4.6C SR2-</application>release
< comes with four EXPORT-CDs. The parameter-file that controls
< the installation-steps is <filename>CENTRAL.R3S</filename>.
< 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.</para>
---
> <para>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.</para>
1918,1919c1702,1703
< <sect3 id="startr3setup-46B">
< <title>Start R3SETUP 4.6B</title>
---
> <sect3 id="startr3setup">
> <title>Start R3SETUP</title>
1925,1934d1708
< <para>During and after installation, SAP requires
< <command>hostname</command> to return the computer name
< only, not the fully qualified domain name. So either
< set the hostname accordingly, or set an alias with
< <command>alias hostname='hostname -s'</command> for
< both <username>oraids</username> and
< <username>idsadm</username>. It is also possible to
< adjust the installed profile- and login-scripts of
< both users.</para>
<
2116c1890
< indicated the correct key (6_LOCATION, then 7_LOCATION
---
> indicated the correct key (6_LOCATI ON, then 7_LOCATION
2124,2278d1897
<
< <sect3 id="startr3setup-46C">
< <title>Start R3SETUP 4.6C SR2</title>
<
< <para>Make sure LD_LIBRARY_PATH is set correctly. This is a
< different value from the 4.6B installation with
< <application>Oracle 8.0.5</application>:</para>
<
< <screen>&prompt.root; <userinput>export LD_LIBRARY_PATH=/sapmnt/PRD/exe:/oracle/PRD/817_32/lib</userinput></screen>
<
< <para>During and after installation, SAP requires
< <command>hostname</command> to return the computer name
< only, not the fully qualified domain name. So either
< set the hostname accordingly, or set an alias with
< <command>alias hostname='hostname -s'</command> for
< <username>oraprd</username>, <username>prdadm</username>
< and (at least during installation phase)
< <username>root</username>. It is also possible to
< adjust the profile- and login-scripts of
< both users that are installed during
< <application>SAP-</application>installation.</para>
<
< <para>Start R3SETUP as user root from installation
< directory:</para>
<
< <screen>&prompt.root; <userinput>cd /oracle/PRD/sapreorg/install</userinput>
< &prompt.root; <userinput>./R3SETUP -f CENTRAL.R3S</userinput> </screen>
<
< <para>The script then asks some questions (defaults in brackets,
< followed by actual input):</para>
<
< <informaltable>
< <tgroup cols="3">
< <thead>
< <row>
< <entry>Question</entry>
< <entry>Default</entry>
< <entry>Input</entry>
< </row>
< </thead>
< <tbody>
< <row>
< <entry>Enter SAP System ID</entry>
< <entry>[C11]</entry>
< <entry>PRD<ret></entry>
< </row>
< <row>
< <entry>Enter SAP Instance Number</entry>
< <entry>[00]</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Enter SAPMOUNT Directory</entry>
< <entry>[/sapmnt]</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Enter name of SAP central host</entry>
< <entry>[majestix]</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Enter Database System ID</entry>
< <entry>[PRD]</entry>
< <entry>PRD<ret></entry>
< </row>
< <row>
< <entry>Enter name of SAP db host</entry>
< <entry>[majestix]</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Select character set</entry>
< <entry>[1] (WE8DEC)</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Enter Oracle server version (2) Oracle 8.1.7</entry>
< <entry> </entry>
< <entry>2<ret></entry>
< </row>
< <row>
< <entry>Extract Oracle Client archive</entry>
< <entry>[1] (Yes, extract)</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Enter path to KERNEL CD</entry>
< <entry>[/sapcd]</entry>
< <entry>/oracle/PRD/sapreorg/KERNEL</entry>
< </row>
< <row>
< <entry>Enter amount of RAM for SAP + DB</entry>
< <entry>2044</entry>
< <entry>1800<ret> (in Megabytes)</entry>
< </row>
< <row>
< <entry>Service Entry Message Server</entry>
< <entry>[3600]</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Enter Group-ID of sapsys</entry>
< <entry>[100]</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Enter Group-ID of oper</entry>
< <entry>[101]</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Enter Group-ID of dba</entry>
< <entry>[102]</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Enter User-ID of <username>oraprd</username></entry>
< <entry>[1002]</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Enter User-ID of <username>prdadm</username></entry>
< <entry>[1000]</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>LDAP support</entry>
< <entry> </entry>
< <entry>3<ret> (no support)</entry>
< </row>
< <row>
< <entry>Installation step completed</entry>
< <entry>[1] (continue)</entry>
< <entry><ret></entry>
< </row>
< <row>
< <entry>Choose installation service</entry>
< <entry>[1] (DB inst,file)</entry>
< <entry><ret></entry>
< </row>
< </tbody>
< </tgroup>
< </informaltable>
<
< <para>So far, creation of users gives an error during
< installation in phases OSUSERDBSID_IND_ORA (for creating
< user <username>ora<sid></username>) and
< OSUSERSIDADM_IND_ORA (creating user
< <username><sid>adm</username>).</para>
<
< <para>Apart from some problems mentioned below, everything
< should go straight through up to the point where the Oracle
< database software needs to be installed.</para>
< </sect3>
2364,2370d1982
< <sect2 id="installingoracle817">
< <title>Installing the Oracle 8.1.7 linux tarball</title>
< <para>Take the tarball <filename>oracle81732.tgz</filename> you
< produced from the installation directory on a linux system
< and untar it to <filename>/oracle/<SID>/817_32/</filename></para>
< </sect2>
<
2438,2439c2050
< <literal>dipgntab</literal> during the 4.6B
< installation.</para>
---
> <literal>dipgntab</literal>.</para>
2446c2057
< <username>ora<sid></username> as follows:</para>
---
> <username>oraids</username> (ora<sid>) as follows:</para>
2453,2463d2063
<
< <sect3 id="mnlstables">
< <title>Updating MNLS Tables</title>
< <para>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.</para>
< <note><para>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.</para></note>
< </sect3>
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):</para>
---
> installation:</para>
2701,2728d2300
< <sect3 id="restartr3setup">
< <title>Restart R3SETUP after fixing a problem</title>
< <para>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.</para>
<
< <para>To restart R3SETUP, just start it with the corresponding
< <emphasis>R3S-</emphasis>file:
< <screen>&prompt.root; <userinput>./R3SETUP -f CENTRDB.R3S</userinput></screen>
< for 4.6B, or with
< <screen>&prompt.root; <userinput>./R3SETUP -f CENTRAL.R3S</userinput></screen>
< for 4.6C, no matter whether the error occured
< with <filename>CENTRAL.R3s</filename> or
< <filename>DATABASE.R3S</filename>.</para>
<
< <note><para>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.</para>
< <para>Don't forget to also start the oracle listener again
< (as user <username>ora<sid></username> with
< <command>umask 0; lsnrctl start</command>) if it was also
< stopped (for example due to a reboot of the system).</para></note>
< </sect3>
<
2732,2739c2304,2306
< <para>If R3SETUP complains at this stage, edit the
< template file R3SETUP used at that time
< (<filename>CENTRDB.R3S</filename> (4.6B) or either
< <filename>CENTRAL.R3S</filename> or
< <filename>DATABASE.R3S</filename> (4.6C)).
< Locate [OSUSERSIDADM_IND_ORA] or search for the
< only <emphasis>STATUS=ERROR</emphasis>-entry
< and edit the following values:</para>
---
> <para>If R3SETUP complains at this stage, edit file
> CENTRDB.R3S. Locate [OSUSERSIDADM_IND_ORA] and edit the
> following values:</para>
2741c2308
< <programlisting>HOME=/home/<sid>adm (was empty)
---
> <programlisting>HOME=/home/idsadm (was empty)
2745c2312,2314
< <para>Then you can restart R3SETUP again.</para>
---
> <para>Then you can restart R3SETUP with:</para>
>
> <screen>&prompt.root; <userinput>./R3SETUP -f CENTRDB.R3S</userinput></screen>
2751,2760c2320,2322
< <para>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
< (<filename>CENTRDB.R3S</filename> (4.6B) or either
< <filename>CENTRAL.R3S</filename> or
< <filename>DATABASE.R3S</filename> (4.6C)).
< Locate [OSUSERDBSID_IND_ORA] or search for the
< only <emphasis>STATUS=ERROR</emphasis>-entry
< and edit the following value in that section:</para>
---
> <para>Possibly R3SETUP also complains at this stage. Just edit
> CENTRDB.R3S. Locate [OSUSERDBSID_IND_ORA] and edit the
> following value in that section:</para>
2764c2326,2328
< <para>Then restart R3SETUP.</para>
---
> <para>Then just restart R3SETUP again:</para>
>
> <screen>&prompt.root; <userinput>./R3SETUP -f CENTRDB.R3S</userinput></screen>
2813c2377
< <para>Restart the SAP system. Now you can connect to the
---
> <para>Restart the SAP system. Now one can connect to the
2822,2850d2385
< <sect3 id="ora-00001">
< <title>ORA-00001</title>
< <para>This error only happened with
< <application>Oracle 8.1.7</application> 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
< <emphasis>ORA-00001</emphasis>.</para>
<
< <para>Find them with <command>ipcs -a</command> and remove them
< with <command>ipcrm</command>.</para>
< </sect3>
<
< <sect3 id="ora-00445pmon">
< <title>ORA-00445 (background process PMON did not start)</title>
< <para>This error happened with <application>Oracle 8.1.7</application>.
< This error is reported if the Database is started with the usual
< startsap-script (for example <filename>startsap_majestix_00</filename>)
< as user <username>prdadm</username>.</para>
< <para>A possible workaround is to start the database as user
< <username>oraprd</username> instead with <command>svrmgrl</command>:
<
< <screen>&prompt.user; <userinput>svrmgrl</userinput>
< SVRMGR> <userinput>connect internal;</userinput>
< SVRMGR> <userinput>startup</userinput>;
< SVRMGR> <userinput>exit</userinput></screen>
<
< </sect3>
<
2852c2387
< <title>ORA-12546 (start Listener with Correct Permissions)</title>
---
> <title>ORA-12546. Start Listener with Correct Permissions</title>
2859c2394
< <para>Otherwise you might get ORA-12546 as the sockets will not
---
> <para>Otherwise one might get ORA-12546 as the sockets will not
2863,2872d2397
< <sect3 id="ora-27102">
< <title>ORA-27102 (out of memory)</title>
<
< <para>This error happend whilst trying to use values for
< <emphasis>MAXDSIZ</emphasis> and <emphasis>DFLDSIZ</emphasis>
< greater than 1GB (1024x1024x1024>.</para>
< <para>Additionally, I got <emphasis>Linux Error 12: Cannot allocate memory</emphasis>
< with values greater than 1 GB.</para>
< </sect3>
<
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
< <para>the following paths were used:</para>
---
> <para>the following path were used:</para>
2891c2416
< /usr/sap/D00</programlisting>
---
> /usr/sap/D00i</programlisting>
2907,2908c2432
< this behavior. I did not encounter any of these problems with
< the <application>SAP 4.6C-</application>Installation.</para>
---
> this behavior.</para>
2914,2922c2438
< <para>During installation of <application>SAP 4.6C</application>,
< 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.</para>
<
< <para>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
---
> <para>Set STATUS of the offending step from ERROR to OK (file
2933,2935d2448
< <para>Here the same restrictions apply: Make sure by looking
< through the logfiles, that this error is not caused by some
< previous problems.</para>
2937,2938c2450
< <para>If you can confirm that it is the correct SAP-Note, just
< set STATUS of the offending step from ERROR to OK (file
---
> <para>Set STATUS of the offending step from ERROR to OK (file
2943,2983d2454
< </sect3>
<
< <sect3 id="sigactionsig31">
< <title>sigaction sig31: File size limit exceeded</title>
<
< <para>This error occured during start of SAP-processes
< <emphasis>disp+work</emphasis>. 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.</para>
<
< <para>To check whether the SAP processes did start properly,
< have a look at the process status with
< <command>ps ax | grep <SID></command>, 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 <filename>/usr/sap/<SID>/DVEBMGS<nr>/work/</filename>.
< The files to look at are <filename>dev_ms</filename> and
< <filename>dev_disp</filename>.</para>
<
< <para>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:</para>
<
< <programlisting># larger value for 46C production systems:
< options SHMMAXPGS=393216
< # smaller value sufficient for 46B:
< #options SHMMAXPGS=262144</programlisting>
<
< </sect3>
<
< <sect3 id="saposcolfails">
< <title>Start of saposcol failed.</title>
< <para>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).</para>
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204192329.g3JNTHj00893>