PERFORCE change 186105 for review
Rene Ladan
rene at FreeBSD.org
Mon Nov 22 14:01:47 UTC 2010
http://p4web.freebsd.org/@@186105?ac=10
Change 186105 by rene at rene_acer on 2010/11/22 14:01:34
Pre-7.X cleanup of Handbook (from bcr@):
- remove "rene" comments, they are on the DocIdeaList on the wiki now
- Bye bye SAP-on-FreeBSD section
Affected files ...
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#13 edit
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#22 edit
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml#9 edit
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mac/chapter.sgml#9 edit
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mail/chapter.sgml#4 edit
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml#9 edit
Differences ...
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#13 (text+ko) ====
@@ -2124,7 +2124,7 @@
<para>In older FreeBSD releases, the default value of <varname>kern.maxfiles</varname>
is derived from the <option>maxusers</option> option in your
- kernel configuration file. <!--rene last sentence still relevant?--> <varname>kern.maxfiles</varname> grows
+ kernel configuration file. <varname>kern.maxfiles</varname> grows
proportionally to the value of <option>maxusers</option>. When
compiling a custom kernel, it is a good idea to set this kernel
configuration option according to the uses of your system. From
@@ -2148,7 +2148,7 @@
<filename>/boot/defaults/loader.conf</filename> file for some hints)
or as described elsewhere in this document.</para>
- <para>In older releases, <!--rene how old?-->the system will auto-tune
+ <para>In older releases, the system will auto-tune
<literal>maxusers</literal> for you if you explicitly set it to
<literal>0</literal><footnote>
<para>The auto-tuning algorithm sets
@@ -2228,7 +2228,7 @@
use.</para>
<para><varname>kern.ipc.nmbclusters</varname> loader tunable should
- be used to tune this at boot time. Only older versions of &os;<!--rene: how old?-->
+ be used to tune this at boot time. Only older versions of &os;
will require you to use the <literal>NMBCLUSTERS</literal> kernel
&man.config.8; option.</para>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#22 (text+ko) ====
@@ -2124,7 +2124,7 @@
<maketarget>installworld</maketarget>. If your old version of
<command>mergemaster</command> does not support <option>-p</option>,
use the new version in the source tree when running for the first
- time:</para><!--rene: how old is this mergemaster?-->
+ time:</para>
<screen>&prompt.root; <userinput>cd /usr/src/usr.sbin/mergemaster</userinput>
&prompt.root; <userinput>./mergemaster.sh -p</userinput></screen>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml#9 (text+ko) ====
@@ -1200,2028 +1200,6 @@
</sect2>
</sect1>
-<![ IGNORE [ rene@ commented this section out in his axing of FreeBSD < 7
- He thinks it is useful in itself, but also that it needs to be updated to
- modern versions by someone with the appropriate resources. An alternative
- would be to convert it into an article. (all up to the 3 closing brackets)
- <sect1 id="sapr3">
- <sect1info>
- <authorgroup>
- <author>
- <firstname>Holger</firstname>
- <surname>Kipp</surname>
- <contrib>Contributed by </contrib>
- </author>
- </authorgroup>
- <!-- holger.kipp at alogis.com -->
- <authorgroup>
- <author>
- <firstname>Valentino</firstname>
- <surname>Vaschetto</surname>
- <contrib>Original version converted to SGML by </contrib>
- </author>
- </authorgroup>
- </sect1info>
-
- <title>Installing &sap.r3;</title>
-
- <indexterm>
- <primary>applications</primary>
- <secondary><application>SAP R/3</application></secondary>
- </indexterm>
-
- <para>Installations of <application>&sap;</application> Systems using FreeBSD will not be
- supported by the &sap; support team — they only offer support
- for certified platforms.</para>
-
- <sect2 id="preface">
- <title>Preface</title>
-
- <para>This document describes a possible way of installing a
- <application>&sap.r3; 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.r3; 4.6B (IDES)</application> with
- <application>&oracle; 8.0.5</application> on FreeBSD 4.3-STABLE</para>
- </listitem>
-
- <listitem>
- <para><application>&sap.r3; 4.6C</application> with
- <application>&oracle; 8.1.7</application> on FreeBSD 4.5-STABLE</para>
- </listitem>
- </itemizedlist>
-
- <para>Even though this document tries to describe all important
- steps in a greater detail, it is not intended as a replacement
- for the <application>&oracle;</application> and
- <application>&sap.r3;</application> installation guides.</para>
-
- <para>Please see the documentation that comes with the
- <application>&sap.r3;</application>
- Linux edition for <application>&sap;</application> and
- <application>&oracle;</application> specific questions, as well
- as resources from <application>&oracle;</application> and
- <application>&sap; OSS</application>.</para>
- </sect2>
-
- <sect2 id="software">
- <title>Software</title>
-
- <para>The following CD-ROMs have been used for <application>&sap;</application> installations:</para>
-
- <sect3 id="software-46b">
- <title>&sap.r3; 4.6B, &oracle; 8.0.5</title>
-
- <informaltable frame="none" pgwide="1">
- <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, we 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
- FreeBSD 4.3-STABLE (it was only a few days past 4.3
- RELEASE).</para>
-
- </sect3>
- <sect3 id="software-46c">
- <title>&sap.r3; 4.6C SR2, &oracle; 8.1.7</title>
-
- <informaltable frame="none" pgwide="1">
- <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 you would like to install, additional
- language CDs might be necessary. Here we are just using DE and EN, so
- the first language CD is the only one needed. As a little note, the
- numbers for all four EXPORT CDs are identical. All three language CDs
- also have the same number (this is different from the 4.6B IDES
- release CD numbering). At the time of writing this installation is
- running on FreeBSD 4.5-STABLE (20.03.2002).</para>
- </sect3>
- </sect2>
-
- <sect2 id="sap-notes">
- <title>&sap; Notes</title>
-
- <para>The following notes should be read before installing
- <application>&sap.r3;</application> and proved to be useful
- during installation:</para>
-
- <sect3 id="sap-notes-46b">
- <title>&sap.r3; 4.6B, &oracle; 8.0.5</title>
-
- <informaltable frame="none" pgwide="1">
- <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.r3; 4.6C, &oracle; 8.1.7</title>
-
- <informaltable frame="none" pgwide="1">
- <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>
- </sect2>
-
- <sect2 id="hardware-requirements">
- <title>Hardware Requirements</title>
-
- <para>The following equipment is sufficient for the installation
- of a <application>&sap.r3; System</application>. For production
- use, a more exact sizing is of course needed:</para>
-
- <informaltable frame="none" pgwide="1">
- <tgroup cols="3">
- <thead>
- <row>
- <entry>Component</entry>
- <entry>4.6B</entry>
- <entry>4.6C</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Processor</entry>
- <entry>2 x 800MHz &pentium; III</entry>
- <entry>2 x 800MHz &pentium; III</entry>
- </row>
-
- <row>
- <entry>Memory</entry>
- <entry>1GB ECC</entry>
- <entry>2GB ECC</entry>
- </row>
-
- <row>
- <entry>Hard Disk Space</entry>
- <entry>50-60GB (IDES)</entry>
- <entry>50-60GB (IDES)</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>For use in production, &xeon; Processors with large cache,
- high-speed disk access (SCSI, RAID hardware controller), USV
- and ECC-RAM is recommended. The large amount of hard disk
- space is due to the preconfigured IDES System, which creates
- 27 GB of database files during installation. This space is
- also sufficient for initial production systems and application
- data.</para>
-
- <sect3 id="hardware-46b">
- <title>&sap.r3; 4.6B, &oracle; 8.0.5</title>
-
- <para>The following off-the-shelf hardware was used: a dual processor
- board with 2 800 MHz &pentium; III processors, &adaptec; 29160 Ultra160
- SCSI adapter (for accessing a 40/80 GB DLT tape drive and CDROM),
- &mylex; &acceleraid; (2 channels, firmware 6.00-1-00 with 32 MB RAM).
- To the &mylex; RAID controller are attached two 17 GB hard disks
- (mirrored) and four 36 GB hard disks (RAID level 5).</para>
- </sect3>
-
- <sect3 id="hardware-46c">
- <title>&sap.r3; 4.6C, &oracle; 8.1.7</title>
-
- <para>For this installation a &dell; &poweredge; 2500 was used: a
- dual processor board with two 1000 MHz &pentium; III processors
- (256 kB Cache), 2 GB PC133 ECC SDRAM, PERC/3 DC PCI RAID Controller
- with 128 MB, and an EIDE DVD-ROM drive. To the RAID controller are
- attached two 18 GB hard disks (mirrored) and four 36 GB hard disks
- (RAID level 5).</para>
- </sect3>
- </sect2>
-
- <sect2 id="installation">
- <title>Installation of FreeBSD</title>
-
- <para>First you have to install FreeBSD. There are several ways to do
- this, for more information read the <xref
- linkend="install-diff-media">.</para>
-
- <sect3 id="disk-layout">
- <title>Disk Layout</title>
-
- <para>To keep it simple, the same disk layout both for the
- <application>&sap.r3; 46B</application> and <application>&sap.r3; 46C
- SR2</application> installation was used. Only the device names
- changed, as the installations were on different hardware (<filename>/dev/da</filename>
- and <filename>/dev/amr</filename> respectively, so if using an AMI &megaraid;, one will see
- <filename>/dev/amr0s1a</filename> instead of <filename>/dev/da0s1a</filename>):</para>
-
- <informaltable frame="none" pgwide="1">
- <tgroup cols="4">
- <thead>
- <row>
- <entry>File system</entry>
- <entry>Size</entry>
- <entry>Mounted on</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><filename>/dev/da0s1a</filename></entry>
- <entry>1 GB</entry>
- <entry><filename>/</filename></entry>
- </row>
-
- <row>
- <entry><filename>/dev/da0s1b</filename></entry>
- <entry>6 GB</entry>
- <entry>swap</entry>
- </row>
-
- <row>
- <entry><filename>/dev/da0s1e</filename></entry>
- <entry>2 GB</entry>
- <entry><filename>/var</filename></entry>
- </row>
-
- <row>
- <entry><filename>/dev/da0s1f</filename></entry>
- <entry>8 GB</entry>
- <entry><filename>/usr</filename></entry>
- </row>
-
- <row>
- <entry><filename>/dev/da1s1e</filename></entry>
- <entry>45 GB</entry>
- <entry><filename>/compat/linux/oracle</filename></entry>
- </row>
-
- <row>
- <entry><filename>/dev/da1s1f</filename></entry>
- <entry>2 GB</entry>
- <entry><filename>/compat/linux/sapmnt</filename></entry>
- </row>
-
- <row>
- <entry><filename>/dev/da1s1g</filename></entry>
- <entry>2 GB</entry>
- <entry><filename>/compat/linux/usr/sap</filename></entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>Configure and initialize the two logical drives
- with the &mylex; or PERC/3 RAID software beforehand.
- The software can be started during the
- <acronym>BIOS</acronym> boot phase.</para>
-
- <para> Please note that this disk layout differs slightly from
- the &sap; recommendations, as &sap; suggests mounting the
- <application>&oracle;</application> subdirectories (and some others) separately — we
- decided to just create them as real subdirectories for
- simplicity.</para>
- </sect3>
-
- <sect3 id="makeworldandnewkernel">
- <title><command>make world</command> and a New Kernel</title>
-
- <para>Download the latest -STABLE sources. Rebuild world and your
- custom kernel after configuring your kernel configuration file.
- Here you should also include the
- <link linkend="kerneltuning">kernel parameters</link>
- which are required for both <application>&sap.r3;</application>
- and <application>&oracle;</application>.</para>
- </sect3>
- </sect2>
-
- <sect2 id="installingthelinuxenviornment">
- <title>Installing the Linux Environment</title>
-
- <sect3 id="installinglinuxbase-system">
- <title>Installing the Linux Base System</title>
-
- <para>First the <link linkend="linuxemu-libs-port">linux_base</link>
- port needs to be installed (as <username>root</username>):</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_base-fc4</userinput>
-&prompt.root; <userinput>make install distclean</userinput></screen>
-
- </sect3>
-
-
- <sect3 id="installinglinuxdevelopment">
- <title>Installing Linux Development Environment</title>
-
- <para>The Linux development environment is needed, if you want to install
- <application>&oracle;</application> on FreeBSD according to the
- <xref linkend="linuxemu-oracle">:</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports/devel/linux_devtools</userinput>
-&prompt.root; <userinput>make install distclean</userinput></screen>
-
- <para>The Linux development environment has only been installed for the <application>&sap.r3;
- 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 you are using the
- <application>&oracle;</application> tarball from a Linux system.</para>
-
- </sect3>
-
-
- <sect3 id="installingnecessaryrpms">
- <title>Installing the Necessary RPMs</title>
- <indexterm><primary>RPMs</primary></indexterm>
-
- <para>To start the <command>R3SETUP</command> program, PAM support is needed.
- During the first <application>&sap;</application> Installation on FreeBSD 4.3-STABLE we
- tried to install PAM with all the required packages and
- finally forced the installation of the PAM package, which
- worked. For <application>&sap.r3; 4.6C SR2</application> we
- directly forced the installation of the PAM RPM, which also
- works, so it seems the dependent packages are not needed:</para>
-
-
-<screen>&prompt.root; <userinput>rpm -i --ignoreos --nodeps --root /compat/linux --dbpath /var/lib/rpm \
-pam-0.68-7.i386.rpm</userinput></screen>
-
- <para>For <application>&oracle; 8.0.5</application> to run the
- intelligent agent, we also had to install the RedHat Tcl package
- <filename>tcl-8.0.5-30.i386.rpm</filename> (otherwise the
- relinking during <application>&oracle;</application> installation
- will not work). There are some other issues regarding
- relinking of <application>&oracle;</application>, but that is
- a <application>&oracle;</application> Linux issue, not FreeBSD specific.</para>
-
- </sect3>
-
- <sect3 id="linuxprocandfallbackelfbrand">
- <title>Some Additional Hints</title>
-
- <para>It might also be a good idea to add <literal>linprocfs</literal>
- to <filename>/etc/fstab</filename>, for more information, see the &man.linprocfs.5; manual page.
- Another parameter to set is <literal>kern.fallback_elf_brand=3</literal>
- which is done in the file <filename>/etc/sysctl.conf</filename>.</para>
- </sect3>
- </sect2>
-
- <sect2 id="creatingsapr3env">
- <title>Creating the &sap.r3; Environment</title>
-
- <sect3 id="filesystemsandmountpoints">
- <title>Creating the Necessary File Systems and Mountpoints</title>
-
- <para>For a simple installation, it is sufficient to create the
- following file systems:</para>
-
- <informaltable frame="none" pgwide="1">
- <tgroup cols="2">
- <thead>
- <row>
- <entry>mount point</entry>
- <entry>size in GB</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><filename>/compat/linux/oracle</filename></entry>
- <entry>45 GB</entry>
- </row>
-
- <row>
- <entry><filename>/compat/linux/sapmnt</filename></entry>
- <entry>2 GB</entry>
- </row>
-
- <row>
- <entry><filename>/compat/linux/usr/sap</filename></entry>
- <entry>2 GB</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>It is also necessary to created some links. Otherwise
- the <application>&sap;</application> Installer will complain, as it is checking the
- created links:</para>
-
- <screen>&prompt.root; <userinput>ln -s /compat/linux/oracle /oracle</userinput>
-&prompt.root; <userinput>ln -s /compat/linux/sapmnt /sapmnt</userinput>
-&prompt.root; <userinput>ln -s /compat/linux/usr/sap /usr/sap</userinput></screen>
-
- <para>Possible error message during installation (here with
- System <emphasis>PRD</emphasis> and the
- <application>&sap.r3; 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>
- </sect3>
-
- <sect3 id="creatingusersanddirectories">
- <title>Creating Users and Directories</title>
-
- <para><application>&sap.r3;</application> needs two users and
- three groups. The user names depend on the
- <application>&sap;</application> system ID (SID) which consists
- of three letters. Some of these SIDs are reserved
- by <application>&sap;</application> (for example
- <literal>SAP</literal> and <literal>NIX</literal>. For a
- complete list please see the <application>&sap;</application> documentation). For the IDES
- installation we used <literal>IDS</literal>, for the
- 4.6C SR2 installation <literal>PRD</literal>, as that system
- is intended for production use. We have
- therefore the following groups (group IDs might differ, these
- are just the values we used with our installation):</para>
-
- <informaltable frame="none" pgwide="1">
- <tgroup cols="3">
- <thead>
- <row>
- <entry>group ID</entry>
- <entry>group name</entry>
- <entry>description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>100</entry>
- <entry>dba</entry>
- <entry>Data Base Administrator</entry>
- </row>
- <row>
- <entry>101</entry>
- <entry>sapsys</entry>
- <entry>&sap; System</entry>
- </row>
- <row>
- <entry>102</entry>
- <entry>oper</entry>
- <entry>Data Base Operator</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>For a default <application>&oracle;</application> installation, only group
- <groupname>dba</groupname> is used. As
- <groupname>oper</groupname> group, one also uses group
- <groupname>dba</groupname> (see <application>&oracle;</application> and
- <application>&sap;</application> documentation for further information).</para>
-
- <para>We also need the following users:</para>
-
- <informaltable frame="none" pgwide="1">
- <tgroup cols="6">
- <thead>
- <row>
- <entry>user ID</entry>
- <entry>user name</entry>
- <entry>generic name</entry>
- <entry>group</entry>
- <entry>additional groups</entry>
- <entry>description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>1000</entry>
- <entry>idsadm/prdadm</entry>
- <entry><replaceable>sid</replaceable>adm</entry>
- <entry>sapsys</entry>
- <entry>oper</entry>
- <entry>&sap; Administrator</entry>
- </row>
- <row>
- <entry>1002</entry>
- <entry>oraids/oraprd</entry>
- <entry>ora<replaceable>sid</replaceable></entry>
- <entry>dba</entry>
- <entry>oper</entry>
- <entry>&oracle; Administrator</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>Adding the users with &man.adduser.8;
- requires the following (please note shell and home
- directory) entries for <quote>&sap; Administrator</quote>:</para>
-
- <programlisting>Name: <replaceable>sid</replaceable>adm
-Password: ******
-Fullname: SAP Administrator <replaceable>SID</replaceable>
-Uid: 1000
-Gid: 101 (sapsys)
-Class:
-Groups: sapsys dba
-HOME: /home/<replaceable>sid</replaceable>adm
-Shell: bash (/compat/linux/bin/bash)</programlisting>
-
- <para>and for <quote>&oracle; Administrator</quote>:</para>
-
- <programlisting>Name: ora<replaceable>sid</replaceable>
-Password: ******
-Fullname: Oracle Administrator <replaceable>SID</replaceable>
-Uid: 1002
-Gid: 100 (dba)
-Class:
-Groups: dba
-HOME: /oracle/<replaceable>sid</replaceable>
-Shell: bash (/compat/linux/bin/bash)</programlisting>
-
- <para>This should also include group
- <groupname>oper</groupname> in case you are using both
- groups <groupname>dba</groupname> and
- <groupname>oper</groupname>.</para>
-
- </sect3>
-
- <sect3 id="creatingdirectories">
- <title>Creating Directories</title>
-
- <para>These directories are usually created as separate
- file systems. This depends entirely on your requirements. We
- choose to create them as simple directories, as they are all
- located on the same RAID 5 anyway:</para>
-
- <para>First we will set owners and rights of some directories (as
- user <username>root</username>):</para>
-
- <screen>&prompt.root; <userinput>chmod 775 /oracle</userinput>
-&prompt.root; <userinput>chmod 777 /sapmnt</userinput>
-&prompt.root; <userinput>chown root:dba /oracle</userinput>
-&prompt.root; <userinput>chown <replaceable>sid</replaceable>adm:sapsys /compat/linux/usr/sap</userinput>
-&prompt.root; <userinput>chmod 775 /compat/linux/usr/sap</userinput></screen>
-
- <para>Second we will create directories as user
- <username>ora<replaceable>sid</replaceable></username>. These
- will all be subdirectories of
- <filename>/oracle/<replaceable>SID</replaceable></filename>:</para>
-
- <screen>&prompt.root; <userinput>su - ora<replaceable>sid</replaceable></userinput>
-&prompt.root; <userinput>cd /oracle/<replaceable>SID</replaceable></userinput>
-&prompt.root; <userinput>mkdir mirrlogA mirrlogB origlogA origlogB</userinput>
-&prompt.root; <userinput>mkdir sapdata1 sapdata2 sapdata3 sapdata4 sapdata5 sapdata6</userinput>
-&prompt.root; <userinput>mkdir saparch sapreorg</userinput>
-&prompt.root; <userinput>exit</userinput></screen>
-
- <para>For the <application>&oracle; 8.1.7</application> installation
- some additional directories are needed:</para>
-
- <screen>&prompt.root; <userinput>su - ora<replaceable>sid</replaceable></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/<replaceable>SID</replaceable></userinput>
-&prompt.root; <userinput>mkdir 817_32</userinput></screen>
-
- <note><para>The directory <filename>client/80x_32</filename> is used
- with exactly this name. Do not replace the <emphasis>x</emphasis>
- with some number or anything.</para></note>
-
- <para>In the third step we create directories as user
- <username><replaceable>sid</replaceable>adm</username>:</para>
-
- <screen>&prompt.root; <userinput>su - <replaceable>sid</replaceable>adm</userinput>
-&prompt.root; <userinput>cd /usr/sap</userinput>
-&prompt.root; <userinput>mkdir <replaceable>SID</replaceable></userinput>
-&prompt.root; <userinput>mkdir trans</userinput>
-&prompt.root; <userinput>exit</userinput></screen>
- </sect3>
-
- <sect3 id="entriesinslashetcslashservices">
- <title>Entries in <filename>/etc/services</filename></title>
-
- <para><application>&sap.r3;</application> requires some entries in file
- <filename>/etc/services</filename>, which will not be set
- correctly during installation under FreeBSD. Please add the
- following entries (you need at least those entries
- corresponding to the instance number — in this case,
- <literal>00</literal>. It will do no harm adding all
- entries from <literal>00</literal> to
- <literal>99</literal> for <literal>dp</literal>,
- <literal>gw</literal>, <literal>sp</literal> and
- <literal>ms</literal>). If you are going to use a <application>SAProuter</application>
- or need to access <application>&sap;</application> OSS, you also need <literal>99</literal>,
- as port 3299 is usually used for the <application>SAProuter</application> process on the
- target system:</para>
-
- <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<replaceable>SID</replaceable> 3600/tcp # SAP Message Server. 3600 + Instance-Number
-sapgw00s 4800/tcp # SAP Secure Gateway 4800 + Instance-Number</programlisting>
- </sect3>
-
- <sect3 id="necessarylocales">
- <title>Necessary Locales</title>
- <indexterm><primary>locale</primary></indexterm>
-
- <para><application>&sap;</application> requires at least two locales that are not part of
- the default RedHat installation. &sap; offers the required
- RPMs as download from their FTP server (which is only
- accessible if you are a customer with OSS access). See note
- 0171356 for a list of RPMs you need.</para>
-
- <para>It is also possible to just create appropriate links
- (for example from <emphasis>de_DE</emphasis> and
- <emphasis>en_US</emphasis> ), but we would not recommend this
- for a production system (so far it worked with the IDES
- system without any problems, though). The following locales
- are needed:</para>
-
- <programlisting>de_DE.ISO-8859-1
-en_US.ISO-8859-1</programlisting>
-
- <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>
-
- <para>If they are not present, there will be some problems
- during the installation. If these are then subsequently
- ignored (by setting the <literal>STATUS</literal> of the offending steps to
- <literal>OK</literal> in file <filename>CENTRDB.R3S</filename>), it will be impossible to log onto
- the <application>&sap;</application> system without some additional effort.</para>
- </sect3>
-
- <sect3 id="kerneltuning">
- <title>Kernel Tuning</title>
- <indexterm><primary>kernel tuning</primary></indexterm>
-
- <para><application>&sap.r3;</application> systems need a lot of resources. We therefore
- added the following parameters to the kernel configuration file:</para>
-
- <programlisting># Set these for memory pigs (SAP and Oracle):
-options MAXDSIZ="(1024*1024*1024)"
-options DFLDSIZ="(1024*1024*1024)"
-# System V options needed.
-options SYSVSHM #SYSV-style shared memory
-options SHMMAXPGS=262144 #max amount of shared mem. pages
-#options SHMMAXPGS=393216 #use this for the 46C inst.parameters
-options SHMMNI=256 #max number of shared memory ident if.
-options SHMSEG=100 #max shared mem.segs per process
-options SYSVMSG #SYSV-style message queues
-options MSGSEG=32767 #max num. of mes.segments in system
-options MSGSSZ=32 #size of msg-seg. MUST be power of 2
-options MSGMNB=65535 #max char. per message queue
-options MSGTQL=2046 #max amount of msgs in system
-options SYSVSEM #SYSV-style semaphores
-options SEMMNU=256 #number of semaphore UNDO structures
-options SEMMNS=1024 #number of semaphores in system
-options SEMMNI=520 #number of semaphore identifiers
-options SEMUME=100 #number of UNDO keys</programlisting>
-
- <para>The minimum values are specified in the documentation that
- comes from &sap;. As there is no description for Linux, see the
- HP-UX section (32-bit) for further information. As the system
- for the 4.6C SR2 installation has more main memory, the shared
- segments can be larger both for <application>&sap;</application>
- and <application>&oracle;</application>, therefore choose a larger
- number of shared memory pages.</para>
-
- <note><para>With the default installation of FreeBSD on &i386;,
- leave <literal>MAXDSIZ</literal> and <literal>DFLDSIZ</literal> at 1 GB maximum. Otherwise, strange
- errors like <errorname>ORA-27102: out of memory</errorname> and
- <errorname>Linux Error: 12: Cannot allocate memory</errorname>
- might happen.</para></note>
- </sect3>
- </sect2>
-
- <sect2 id="installingsapr3">
- <title>Installing &sap.r3;</title>
-
- <sect3 id="preparingsapcdroms">
- <title>Preparing &sap; CDROMs</title>
-
- <para>There are many CDROMs to mount and unmount during the
- installation. Assuming you have enough CDROM drives, you
- can just mount them all. We decided to copy the CDROMs
- contents to corresponding directories:</para>
-
- <programlisting>/oracle/<replaceable>SID</replaceable>/sapreorg/<replaceable>cd-name</replaceable></programlisting>
-
- <para>where <replaceable>cd-name</replaceable> was one of <filename>KERNEL</filename>,
- <filename>RDBMS</filename>, <filename>EXPORT1</filename>,
- <filename>EXPORT2</filename>, <filename>EXPORT3</filename>,
- <filename>EXPORT4</filename>, <filename>EXPORT5</filename> and
- <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 <option>-g</option> option for mounting. So use the following
- commands:</para>
-
- <screen>&prompt.root; <userinput>mount_cd9660 -g /dev/cd0a /mnt</userinput>
-&prompt.root; <userinput>cp -R /mnt/* /oracle/<replaceable>SID</replaceable>/sapreorg/<replaceable>cd-name</replaceable></userinput>
-&prompt.root; <userinput>umount /mnt</userinput></screen>
- </sect3>
-
- <sect3 id="runningtheinstall-script">
- <title>Running the Installation Script</title>
-
- <para>First you have to prepare an <filename class="directory">install</filename> directory:</para>
-
- <screen>&prompt.root; <userinput>cd /oracle/<replaceable>SID</replaceable>/sapreorg</userinput>
-&prompt.root; <userinput>mkdir install</userinput>
-&prompt.root; <userinput>cd install</userinput></screen>
-
- <para>Then the installation script is started, which will copy nearly
- all the relevant files into the <filename class="directory">install</filename> directory:</para>
-
>>> TRUNCATED FOR MAIL (1000 lines) <<<
More information about the p4-projects
mailing list