sapr3.html

FreeBSD操作系统的详细使用手册

name="INSTALLINGTHEORACLE805PREPRODUCTION">10.7.9.2 Installing the <span
class="TRADEMARK">Oracle</span> 8.0.5 Pre-production Release for Linux (Kernel
2.0.33)</a></h3>

<p>This installation is quite easy. Mount the CD, start the installer. It will then ask
for the location of the <span class="TRADEMARK">Oracle</span> home directory, and copy
all binaries there. We did not delete the remains of our previous RDBMS installation
tries, though.</p>

<p>Afterwards, <b class="APPLICATION"><span class="TRADEMARK">Oracle</span></b> Database
could be started with no problems.</p>
</div>
</div>

<div class="SECT2">
<h2 class="SECT2"><a id="INSTALLINGORACLE817" name="INSTALLINGORACLE817">10.7.10
Installing the <span class="TRADEMARK">Oracle</span> 8.1.7 Linux Tarball</a></h2>

<p>Take the tarball <tt class="FILENAME">oracle81732.tgz</tt> you produced from the
installation directory on a Linux system and untar it to <tt
class="FILENAME">/oracle/<var class="REPLACEABLE">SID</var>/817_32/</tt>.</p>
</div>

<div class="SECT2">
<h2 class="SECT2"><a id="CONTINUEWITHSAPR4INSTALLATION"
name="CONTINUEWITHSAPR4INSTALLATION">10.7.11 Continue with <span
class="TRADEMARK">SAP</span>&nbsp;<span class="TRADEMARK">R/3</span>
Installation</a></h2>

<p>First check the environment settings of users <tt class="USERNAME">idsamd</tt> (<var
class="REPLACEABLE">sid</var>adm) and <tt class="USERNAME">oraids</tt> (ora<var
class="REPLACEABLE">sid</var>). They should now both have the files <tt
class="FILENAME">.profile</tt>, <tt class="FILENAME">.login</tt> and <tt
class="FILENAME">.cshrc</tt> which are all using <tt class="COMMAND">hostname</tt>. In
case the system's hostname is the fully qualified name, you need to change <tt
class="COMMAND">hostname</tt> to <tt class="COMMAND">hostname -s</tt> within all three
files.</p>

<div class="SECT3">
<h3 class="SECT3"><a id="DATABASELOAD" name="DATABASELOAD">10.7.11.1 Database
Load</a></h3>

<p>Afterwards, <tt class="COMMAND">R3SETUP</tt> can either be restarted or continued
(depending on whether exit was chosen or not). <tt class="COMMAND">R3SETUP</tt> then
creates the tablespaces and loads the data (for 46B IDES, from EXPORT1 to EXPORT6, for
46C from DISK1 to DISK4) with <tt class="COMMAND">R3load</tt> into the database.</p>

<p>When the database load is finished (might take a few hours), some passwords are
requested. For test installations, one can use the well known default passwords (use
different ones if security is an issue!):</p>

<div class="INFORMALTABLE"><a id="AEN15013" name="AEN15013"></a>
<table border="0" frame="void" class="CALSTABLE">
<col />
<col />
<thead>
<tr>
<th>Question</th>
<th>Input</th>
</tr>
</thead>

<tbody>
<tr>
<td>Enter Password for sapr3</td>
<td>sap<b class="KEYCAP">Enter</b></td>
</tr>

<tr>
<td>Confirum Password for sapr3</td>
<td>sap<b class="KEYCAP">Enter</b></td>
</tr>

<tr>
<td>Enter Password for sys</td>
<td>change_on_install<b class="KEYCAP">Enter</b></td>
</tr>

<tr>
<td>Confirm Password for sys</td>
<td>change_on_install<b class="KEYCAP">Enter</b></td>
</tr>

<tr>
<td>Enter Password for system</td>
<td>manager<b class="KEYCAP">Enter</b></td>
</tr>

<tr>
<td>Confirm Password for system</td>
<td>manager<b class="KEYCAP">Enter</b></td>
</tr>
</tbody>
</table>
</div>

<p>At this point We had a few problems with <tt class="COMMAND">dipgntab</tt> during the
4.6B installation.</p>
</div>

<div class="SECT3">
<h3 class="SECT3"><a id="LISTENER" name="LISTENER">10.7.11.2 Listener</a></h3>

<p>Start the <b class="APPLICATION"><span class="TRADEMARK">Oracle</span></b> Listener as
user <tt class="USERNAME">ora<var class="REPLACEABLE">sid</var></tt> as follows:</p>

<pre class="SCREEN">
<samp class="PROMPT">%</samp> <kbd class="USERINPUT">umask 0; lsnrctl start</kbd>
</pre>

<p>Otherwise you might get the error <span class="ERRORCODE">ORA-12546</span> as the
sockets will not have the correct permissions. See <span class="TRADEMARK">SAP</span>
Note 072984.</p>
</div>

<div class="SECT3">
<h3 class="SECT3"><a id="MNLSTABLES" name="MNLSTABLES">10.7.11.3 Updating MNLS
Tables</a></h3>

<p>If you plan to import non-Latin-1 languages into the <b class="APPLICATION"><span
class="TRADEMARK">SAP</span></b> system, you have to update the Multi National Language
Support tables. This is described in the <span class="TRADEMARK">SAP</span> OSS Notes
15023 and 45619. Otherwise, you can skip this question during <b
class="APPLICATION"><span class="TRADEMARK">SAP</span></b> installation.</p>

<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> If you do not need MNLS, it is still necessary to check the table TCPDB
and initializing it if this has not been done. See <span class="TRADEMARK">SAP</span>
note 0015023 and 0045619 for further information.</p>
</blockquote>
</div>
</div>
</div>

<div class="SECT2">
<h2 class="SECT2"><a id="POSTINSTALLATIONSTEPS" name="POSTINSTALLATIONSTEPS">10.7.12
Post-installation Steps</a></h2>

<div class="SECT3">
<h3 class="SECT3"><a id="REQUESTSAPR3LICENSEKEY" name="REQUESTSAPR3LICENSEKEY">10.7.12.1
Request <span class="TRADEMARK">SAP</span>&nbsp;<span class="TRADEMARK">R/3</span>
License Key</a></h3>

<p>You have to request your <b class="APPLICATION"><span
class="TRADEMARK">SAP</span>&nbsp;<span class="TRADEMARK">R/3</span></b> License Key.
This is needed, as the temporary license that was installed during installation is only
valid for four weeks. First get the hardware key. Log on as user <tt
class="USERNAME">idsadm</tt> and call <tt class="COMMAND">saplicense</tt>:</p>

<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">/sapmnt/IDS/exe/saplicense -get</kbd>
</pre>

<p>Calling <tt class="COMMAND">saplicense</tt> without parameters gives a list of
options. Upon receiving the license key, it can be installed using:</p>

<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">/sapmnt/IDS/exe/saplicense -install</kbd>
</pre>

<p>You are then required to enter the following values:</p>

<pre class="PROGRAMLISTING">
SAP SYSTEM ID   = <var class="REPLACEABLE">SID, 3 chars</var>
CUSTOMER KEY    = <var class="REPLACEABLE">hardware key, 11 chars</var>
INSTALLATION NO = <var class="REPLACEABLE">installation, 10 digits</var>
EXPIRATION DATE = <var class="REPLACEABLE">yyyymmdd, usually "99991231"</var>
LICENSE KEY     = <var class="REPLACEABLE">license key, 24 chars</var>
</pre>
</div>

<div class="SECT3">
<h3 class="SECT3"><a id="CREATINGUSERS" name="CREATINGUSERS">10.7.12.2 Creating
Users</a></h3>

<p>Create a user within client 000 (for some tasks required to be done within client 000,
but with a user different from users <tt class="USERNAME">sap*</tt> and <tt
class="USERNAME">ddic</tt>). As a user name, We usually choose <tt
class="USERNAME">wartung</tt> (or <tt class="USERNAME">service</tt> in English). Profiles
required are <var class="LITERAL">sap_new</var> and <var class="LITERAL">sap_all</var>.
For additional safety the passwords of default users within all clients should be changed
(this includes users <tt class="USERNAME">sap*</tt> and <tt
class="USERNAME">ddic</tt>).</p>
</div>

<div class="SECT3">
<h3 class="SECT3"><a id="CONFIGTRANSSYSPROFILEOPERMODESETC"
name="CONFIGTRANSSYSPROFILEOPERMODESETC">10.7.12.3 Configure Transport System, Profile,
Operation Modes, Etc.</a></h3>

<p>Within client 000, user different from <tt class="USERNAME">ddic</tt> and <tt
class="USERNAME">sap*</tt>, do at least the following:</p>

<div class="INFORMALTABLE"><a id="AEN15113" name="AEN15113"></a>
<table border="0" frame="void" class="CALSTABLE">
<col />
<col />
<thead>
<tr>
<th>Task</th>
<th>Transaction</th>
</tr>
</thead>

<tbody>
<tr>
<td>Configure Transport System, e.g. as <span class="emphasis"><i
class="EMPHASIS">Stand-Alone Transport Domain Entity</i></span></td>
<td>STMS</td>
</tr>

<tr>
<td>Create / Edit Profile for System</td>
<td>RZ10</td>
</tr>

<tr>
<td>Maintain Operation Modes and Instances</td>
<td>RZ04</td>
</tr>
</tbody>
</table>
</div>

<p>These and all the other post-installation steps are thoroughly described in <b
class="APPLICATION"><span class="TRADEMARK">SAP</span></b> installation guides.</p>
</div>

<div class="SECT3">
<h3 class="SECT3"><a id="EDITINTSIDSAP" name="EDITINTSIDSAP">10.7.12.4 Edit <tt
class="FILENAME">init<var class="REPLACEABLE">sid</var>.sap</tt> (<tt
class="FILENAME">initIDS.sap</tt>)</a></h3>

<p>The file <tt class="FILENAME">/oracle/IDS/dbs/initIDS.sap</tt> contains the <b
class="APPLICATION"><span class="TRADEMARK">SAP</span></b> backup profile. Here the size
of the tape to be used, type of compression and so on need to be defined. To get this
running with <tt class="COMMAND">sapdba</tt> / <tt class="COMMAND">brbackup</tt>, we
changed the following values:</p>

<pre class="PROGRAMLISTING">
compress = hardware
archive_function = copy_delete_save
cpio_flags = "-ov --format=newc --block-size=128 --quiet"
cpio_in_flags = "-iuv --block-size=128 --quiet"
tape_size = 38000M
tape_address = /dev/nsa0
tape_address_rew = /dev/sa0
</pre>

<p>Explanations:</p>

<p><var class="VARNAME">compress</var>: The tape we use is a HP DLT1 which does hardware
compression.</p>

<p><var class="VARNAME">archive_function</var>: This defines the default behavior for
saving <span class="TRADEMARK">Oracle</span> archive logs: new logfiles are saved to
tape, already saved logfiles are saved again and are then deleted. This prevents lots of
trouble if you need to recover the database, and one of the archive-tapes has gone
bad.</p>

<p><var class="VARNAME">cpio_flags</var>: Default is to use <var class="OPTION">-B</var>
which sets block size to 5120&nbsp;Bytes. For DLT Tapes, HP recommends at least 32&nbsp;K
block size, so we used <var class="OPTION">--block-size=128</var> for 64&nbsp;K. <var
class="OPTION">--format=newc</var> is needed because we have inode numbers greater than
65535. The last option <var class="OPTION">--quiet</var> is needed as otherwise <tt
class="COMMAND">brbackup</tt> complains as soon as <tt class="COMMAND">cpio</tt> outputs
the numbers of blocks saved.</p>

<p><var class="VARNAME">cpio_in_flags</var>: Flags needed for loading data back from
tape. Format is recognized automatically.</p>

<p><var class="VARNAME">tape_size</var>: This usually gives the raw storage capability of
the tape. For security reason (we use hardware compression), the value is slightly lower
than the actual value.</p>

<p><var class="VARNAME">tape_address</var>: The non-rewindable device to be used with <tt
class="COMMAND">cpio</tt>.</p>

<p><var class="VARNAME">tape_address_rew</var>: The rewindable device to be used with <tt
class="COMMAND">cpio</tt>.</p>
</div>

<div class="SECT3">
<h3 class="SECT3"><a id="AEN15169" name="AEN15169">10.7.12.5 Configuration Issues after
Installation</a></h3>

<p>The following <b class="APPLICATION"><span class="TRADEMARK">SAP</span></b> parameters
should be tuned after installation (examples for IDES 46B, 1&nbsp;GB memory):</p>

<div class="INFORMALTABLE"><a id="AEN15174" name="AEN15174"></a>
<table border="0" frame="void" class="CALSTABLE">
<col />
<col />
<thead>
<tr>
<th>Name</th>
<th>Value</th>
</tr>
</thead>

<tbody>
<tr>
<td>ztta/roll_extension</td>
<td>250000000</td>
</tr>

<tr>
<td>abap/heap_area_dia</td>
<td>300000000</td>
</tr>

<tr>
<td>abap/heap_area_nondia</td>
<td>400000000</td>
</tr>

<tr>
<td>em/initial_size_MB</td>
<td>256</td>
</tr>

<tr>
<td>em/blocksize_kB</td>
<td>1024</td>
</tr>

<tr>
<td>ipc/shm_psize_40</td>
<td>70000000</td>
</tr>
</tbody>
</table>
</div>

<p><span class="TRADEMARK">SAP</span> Note 0013026:</p>

<div class="INFORMALTABLE"><a id="AEN15201" name="AEN15201"></a>
<table border="0" frame="void" class="CALSTABLE">
<col />
<col />
<thead>
<tr>
<th>Name</th>
<th>Value</th>
</tr>
</thead>

<tbody>
<tr>
<td>ztta/dynpro_area</td>
<td>2500000</td>
</tr>
</tbody>
</table>
</div>

<p><span class="TRADEMARK">SAP</span> Note 0157246:</p>

<div class="INFORMALTABLE"><a id="AEN15213" name="AEN15213"></a>
<table border="0" frame="void" class="CALSTABLE">
<col />
<col />
<thead>
<tr>
<th>Name</th>
<th>Value</th>
</tr>
</thead>

<tbody>
<tr>
<td>rdisp/ROLL_MAXFS</td>
<td>16000</td>
</tr>

<tr>
<td>rdisp/PG_MAXFS</td>
<td>30000</td>
</tr>
</tbody>
</table>
</div>

<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> With the above parameters, on a system with 1&nbsp;gigabyte of memory,
one may find memory consumption similar to:</p>

<pre class="PROGRAMLISTING">
Mem: 547M Active, 305M Inact, 109M Wired, 40M Cache, 112M Buf, 3492K Free
</pre>
</blockquote>
</div>
</div>
</div>

<div class="SECT2">
<h2 class="SECT2"><a id="PROBLEMSDURINGINSTALLATION"
name="PROBLEMSDURINGINSTALLATION">10.7.13 Problems during Installat