os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

In SAP section:

Browse source 
- Add and remove wrong application, command, filename, literal,
  username tags
- Some s/I/we
- Some punctuation fixes
- Some little rewordings
This commit is contained in:
Marc Fonvieille 2003-10-22 07:46:27 +00:00
parent 571c1520f0
commit 434f42efd0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=18532
1 changed files with 120 additions and 116 deletions

236
en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml
View file

@ -1658,7 +1658,7 @@ export PATH</programlisting>
<title>Installing the Necessary RPMs</title>
<indexterm><primary>RPMs</primary></indexterm>
<para>To start the <application>R3SETUP</application> program, PAM support is needed.
<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
@ -1683,7 +1683,7 @@ pam-0.68-7.i386.rpm</userinput></screen>
<sect3 id="linuxprocandfallbackelfbrand">
<title>Some Additional Hints</title>
<para>It might also be a good idea to add <filename>linprocfs</filename>
<para>It might also be a good idea to add <literal>linprocfs</literal>
to <filename>/etc/fstab</filename>, for more informations, 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>
@ -1929,7 +1929,7 @@ Shell: bash (/compat/linux/bin/bash)</programlisting>
</sect3>
<sect3 id="entriesinslashetcslashservices">
<title>Entries in /etc/services</title>
<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
@ -1982,7 +1982,7 @@ en_US.ISO-8859-1</programlisting>
<para>If they are not present, there will be some problems
during the installation. If these are then subsequently
ignored (by setting the status of the offending steps to
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>
@ -2108,7 +2108,7 @@ options SEMUME=100 #number of UNDO keys</programlisting>
</sect3>
<sect3 id="startr3setup-46B">
<title>Start R3SETUP 4.6B</title>
<title>Start <command>R3SETUP</command> 4.6B</title>
<para>Make sure <envar>LD_LIBRARY_PATH</envar> is set correctly:</para>
@ -2305,7 +2305,7 @@ options SEMUME=100 #number of UNDO keys</programlisting>
</sect3>
<sect3 id="startr3setup-46C">
<title>Start R3SETUP 4.6C SR2</title>
<title>Start <command>R3SETUP</command> 4.6C SR2</title>
<para>Make sure <envar>LD_LIBRARY_PATH</envar> is set correctly. This is a
different value from the 4.6B installation with
@ -2450,7 +2450,7 @@ options SEMUME=100 #number of UNDO keys</programlisting>
<sect2 id="installingoracle805">
<title>Installing &oracle; 8.0.5</title>
<para>Please see the corresponding &sap; Notes and &oracle; Readmes
<para>Please see the corresponding &sap; Notes and &oracle; <filename>Readme</filename>s
regarding Linux and <application>&oracle; DB</application> for possible problems. Most if
not all problems stem from incompatible libraries.</para>
@ -2460,7 +2460,7 @@ options SEMUME=100 #number of UNDO keys</programlisting>
<sect3 id="installingtheoracle805withorainst">
<title>Installing the &oracle; 8.0.5 with orainst</title>
<title>Installing the &oracle; 8.0.5 with <command>orainst</command></title>
<para>If <application>&oracle; 8.0.5</application> is to be
used, some additional libraries are needed for successfully
@ -2475,7 +2475,7 @@ options SEMUME=100 #number of UNDO keys</programlisting>
<para><filename>compat-egcs-c++-5.2-1.0.3a.1.i386.rpm</filename></para>
<para><filename>compat-binutils-5.2-2.9.1.0.23.1.i386.rpm</filename></para>
<para>See the corresponding &sap; Notes or &oracle; Readmes for
<para>See the corresponding &sap; Notes or &oracle; <filename>Readme</filename>s for
further information. If this is no option (at the time of
installation we did not have enough time to check this), one
could use the original binaries, or use the relinked
@ -2610,13 +2610,13 @@ options SEMUME=100 #number of UNDO keys</programlisting>
<sect3 id="listener">
<title>Listener</title>
<para>Start the &oracle; Listener as user
<para>Start the <application>&oracle;</application> Listener as user
<username>ora<replaceable>sid</replaceable></username> as follows:</para>
<screen>&prompt.user; <userinput>umask 0; lsnrctl start</userinput></screen>
<para>Otherwise you might get <errorcode>ORA-12546</errorcode> as the sockets will not
have the correct permissions. See &sap; note 072984.</para>
<para>Otherwise you might get the error <errorcode>ORA-12546</errorcode> as the sockets will not
have the correct permissions. See &sap; Note 072984.</para>
</sect3>
<sect3 id="mnlstables">
@ -2645,7 +2645,7 @@ options SEMUME=100 #number of UNDO keys</programlisting>
<screen>&prompt.root; <userinput>/sapmnt/IDS/exe/saplicense -get</userinput></screen>
<para>Calling <command>saplicense</command> without options gives
<para>Calling <command>saplicense</command> without parameters gives
a list of options. Upon receiving the license key, it can be
installed using:</para>
@ -2666,11 +2666,11 @@ LICENSE KEY = <replaceable>license key, 24 chars</replaceable></programlisti
<para>Create a user within client 000 (for some tasks required
to be done within client 000, but with a user different from
users <username>sap*</username> and
<username>ddic</username>). As a user name, I usually choose
<replaceable>wartung</replaceable> (or
<replaceable>service</replaceable> in English). Profiles
required are <emphasis>sap_new</emphasis> and
<emphasis>sap_all</emphasis>. For additional safety the
<username>ddic</username>). As a user name, We usually choose
<username>wartung</username> (or
<username>service</username> in English). Profiles
required are <literal>sap_new</literal> and
<literal>sap_all</literal>. For additional safety the
passwords of default users within all clients should be
changed (this includes users <username>sap*</username> and
<username>ddic</username>).</para>
@ -2680,7 +2680,7 @@ LICENSE KEY = <replaceable>license key, 24 chars</replaceable></programlisti
<title>Configure Transport System, Profile, Operation Modes, Etc.</title>
<para>Within client 000, user different from <username>ddic</username>
and sap*, do at least the following:</para>
and <username>sap*</username>, do at least the following:</para>
<informaltable>
<tgroup cols="2">
@ -2692,7 +2692,7 @@ LICENSE KEY = <replaceable>license key, 24 chars</replaceable></programlisti
</thead>
<tbody>
<row>
<entry>Configure Transport System, eg as <emphasis>Stand-Alone
<entry>Configure Transport System, e.g. as <emphasis>Stand-Alone
Transport Domain Entity</emphasis></entry>
<entry>STMS</entry>
</row>
@ -2709,17 +2709,17 @@ LICENSE KEY = <replaceable>license key, 24 chars</replaceable></programlisti
</informaltable>
<para>These and all the other post-installation steps are
thoroughly described in &sap; installation guides.</para>
thoroughly described in <application>&sap;</application> installation guides.</para>
</sect3>
<sect3 id="editintsidsap">
<title>Edit init<replaceable>sid</replaceable>.sap (initIDS.sap)</title>
<title>Edit <filename>init<replaceable>sid</replaceable>.sap</filename> (<filename>initIDS.sap</filename>)</title>
<para>The file <filename>/oracle/IDS/dbs/initIDS.sap</filename>
contains the &sap; backup profile. Here the size of the tape to
contains the <application>&sap;</application> 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 <command>sapdba</command> /
<command>brbackup</command>, I changed the following values:</para>
<command>brbackup</command>, we changed the following values:</para>
<programlisting>compress = hardware
archive_function = copy_delete_save
@ -2731,45 +2731,45 @@ tape_address_rew = /dev/sa0</programlisting>
<para>Explanations:</para>
<para><varname>compress</varname> The tape I use is a HP DLT1
<para><varname>compress</varname>: The tape we use is a HP DLT1
which does hardware compression.</para>
<para><varname>archive_function</varname> This defines the
default behavior for saving &oracle; archive logs: New logfiles
<para><varname>archive_function</varname>: This defines the
default behavior for saving &oracle; archive logs: new logfiles
are saved to tape, already saved logfiles are saved again and
are then deleted. This prevents lots of trouble if you need to
recover the database, and one of the archive-tapes has gone
bad.</para>
<para><varname>cpio_flags</varname> Default is to use -B which
sets block size to 5120&nbsp;Bytes. For DLT-Tapes, HP recommends at
least 32&nbsp;K block size, so I used --block-size=128 for
64&nbsp;K. --format=newc is needed I have inode numbers greater than
65535. The last option --quiet is needed as otherwise
<para><varname>cpio_flags</varname>: Default is to use <option>-B</option> which
sets block size to 5120&nbsp;Bytes. For DLT Tapes, HP recommends at
least 32&nbsp;K block size, so we used <option>--block-size=128</option> for
64&nbsp;K. <option>--format=newc</option> is needed because we have inode numbers greater than
65535. The last option <option>--quiet</option> is needed as otherwise
<command>brbackup</command>
complains as soon as <command>cpio</command> outputs the
numbers of blocks saved.</para>
<para><varname>cpio_in_flags</varname> Flags needed for
<para><varname>cpio_in_flags</varname>: Flags needed for
loading data back from tape. Format is recognized
automatically.</para>
<para><varname>tape_size</varname> This usually gives the raw
<para><varname>tape_size</varname>: 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.</para>
<para><varname>tape_address</varname> The non-rewindable
<para><varname>tape_address</varname>: The non-rewindable
device to be used with <command>cpio</command>.</para>
<para><varname>tape_address_rew</varname> The rewindable device to be
used with cpio.</para>
<para><varname>tape_address_rew</varname>: The rewindable device to be
used with <command>cpio</command>.</para>
</sect3>
<sect3>
<title>Configuration Issues after Installation</title>
<para>The following &sap; parameters should be tuned after
<para>The following <application>&sap;</application> parameters should be tuned after
installation (examples for IDES 46B, 1&nbsp;GB memory):</para>
<informaltable frame="none">
@ -2864,29 +2864,33 @@ tape_address_rew = /dev/sa0</programlisting>
<title>Problems during Installation</title>
<sect3 id="restartr3setup">
<title>Restart R3SETUP after Fixing a Problem</title>
<title>Restart <command>R3SETUP</command> after Fixing a Problem</title>
<para>R3SETUP stops if it encounters an error. If you have
<para><command>R3SETUP</command> stops if it encounters an error. If you have
looked at the corresponding logfiles and fixed the error,
you have to start R3SETUP again, usually selecting REPEAT
as option for the last step R3SETUP complained about.</para>
you have to start <command>R3SETUP</command> again, usually selecting REPEAT
as option for the last step <command>R3SETUP</command> complained about.</para>
<para>To restart <command>R3SETUP</command>, just start it with the corresponding
<filename>R3S</filename> file:</para>
<para>To restart R3SETUP, just start it with the corresponding
<filename>R3S</filename>-file:
<screen>&prompt.root; <userinput>./R3SETUP -f CENTRDB.R3S</userinput></screen>
for 4.6B, or with
<para>for 4.6B, or with</para>
<screen>&prompt.root; <userinput>./R3SETUP -f CENTRAL.R3S</userinput></screen>
for 4.6C, no matter whether the error occurred
<para>for 4.6C, no matter whether the error occurred
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
<note><para>At some stages, <command>R3SETUP</command> assumes that both database
and <application>&sap;</application> 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
and <application>&sap;</application> by hand after you fixed the errors and before starting
<command>R3SETUP</command> again.</para>
<para>Do not forget to also start the <application>&oracle;</application> listener again (as
<username>ora<replaceable>sid</replaceable></username> with
<command>umask 0; lsnrctl start</command>) if it was also
stopped (for example due to a necessary reboot of the
@ -2895,41 +2899,41 @@ tape_address_rew = /dev/sa0</programlisting>
</sect3>
<sect3 id="indoraduringduringr3setup">
<title>OSUSERSIDADM_IND_ORA during R3SETUP</title>
<title>OSUSERSIDADM_IND_ORA during <command>R3SETUP</command></title>
<para>If R3SETUP complains at this stage, edit the
template file R3SETUP used at that time
<para>If <command>R3SETUP</command> complains at this stage, edit the
template file <command>R3SETUP</command> 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
Locate <literal>[OSUSERSIDADM_IND_ORA]</literal> or search for the
only <literal>STATUS=ERROR</literal> entry
and edit the following values:</para>
<programlisting>HOME=/home/<replaceable>sid</replaceable>adm (was empty)
STATUS=OK (had status ERROR)
</programlisting>
<para>Then you can restart R3SETUP again.</para>
<para>Then you can restart <command>R3SETUP</command> again.</para>
</sect3>
<sect3 id="indoraduringr3setup">
<title>OSUSERDBSID_IND_ORA during R3SETUP</title>
<title>OSUSERDBSID_IND_ORA during <command>R3SETUP</command></title>
<para>Possibly R3SETUP also complains at this stage. The error
<para>Possibly <command>R3SETUP</command> 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
the template file <command>R3SETUP</command> 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
Locate <literal>[OSUSERDBSID_IND_ORA]</literal> or search for the
only <literal>STATUS=ERROR</literal> entry
and edit the following value in that section:</para>
<programlisting>STATUS=OK</programlisting>
<para>Then restart R3SETUP.</para>
<para>Then restart <command>R3SETUP</command>.</para>
</sect3>
<sect3 id="oraviewvrffilenotfound">
@ -2938,24 +2942,24 @@ STATUS=OK (had status ERROR)
<para>You have not deselected <emphasis>&oracle; On-Line Text Viewer</emphasis>
before starting the installation. This is marked for installation even
though this option is currently not available for Linux. Deselect this
product inside the &oracle; installation menu and restart installation.</para>
product inside the <application>&oracle;</application> installation menu and restart installation.</para>
</sect3>
<sect3 id="textenvincalid">
<title><errorname>TEXTENV_INVALID</errorname> during R3SETUP, RFC or SAPGUI Start</title>
<title><errorname>TEXTENV_INVALID</errorname> during <command>R3SETUP</command>, RFC or SAPgui Start</title>
<para>If this error is encountered, the correct locale is
missing. &sap; note 0171356 lists the necessary RPMs that need
be installed (eg <emphasis>saplocales-1.0-3</emphasis>,
<emphasis>saposcheck-1.0-1</emphasis> for RedHat 6.1). In case
missing. &sap; Note 0171356 lists the necessary RPMs that need
be installed (e.g. <filename>saplocales-1.0-3</filename>,
<filename>saposcheck-1.0-1</filename> for RedHat 6.1). In case
you ignored all the related errors and set the corresponding
status from ERROR to OK (in CENTRDB.R3S) every time R3SETUP
complained and just restarted R3SETUP, the &sap; System will not
<literal>STATUS</literal> from <literal>ERROR</literal> to <literal>OK</literal> (in <filename>CENTRDB.R3S</filename>) every time <command>R3SETUP</command>
complained and just restarted <command>R3SETUP</command>, the <application>&sap;</application> system will not
be properly configured and you will then not be able to
connect to the system with a
<literal>sapgui</literal>, even though the system
<application>SAPgui</application>, even though the system
can be started. Trying to connect with the old Linux
<literal>sapgui</literal> gave the following
<application>SAPgui</application> gave the following
messages:</para>
<programlisting>Sat May 5 14:23:14 2001
@ -2967,21 +2971,21 @@ Sat May 5 14:23:22 2001
*** ERROR => no socket operation allowed [trxio.c 3363]
Speicherzugriffsfehler</programlisting>
<para>This behavior is due to &sap.r3; being unable to correctly
<para>This behavior is due to <application>&sap.r3;</application> being unable to correctly
assign a locale and also not being properly configured itself
(missing entries in some database tables). To be able to connect
to &sap;, add the following entries to file
<filename>DEFAULT.PFL</filename> (see note 0043288):</para>
to <application>&sap;</application>, add the following entries to file
<filename>DEFAULT.PFL</filename> (see Note 0043288):</para>
<programlisting>abap/set_etct_env_at_new_mode = 0
install/collate/active = 0
rscp/TCP0B = TCP0B</programlisting>
<para>Restart the &sap; system. Now you can connect to the
<para>Restart the <application>&sap;</application> system. Now you can connect to the
system, even though country-specific language settings might
not work as expected. After correcting country-settings
not work as expected. After correcting country settings
(and providing the correct locales), these entries can be
removed from <filename>DEFAULT.PFL</filename> and the &sap;
removed from <filename>DEFAULT.PFL</filename> and the <application>&sap;</application>
system can be restarted.</para>
</sect3>
@ -2990,7 +2994,7 @@ rscp/TCP0B = TCP0B</programlisting>
<title><errorcode>ORA-00001</errorcode></title>
<para>This error only happened with
<application>&oracle; 8.1.7</application> on FreeBSD&nbsp;4.5.
The reason was that the &oracle; database could not initialize itself
The reason was that the <application>&oracle;</application> 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
<errorcode>ORA-00001</errorcode>.</para>
@ -3002,9 +3006,9 @@ rscp/TCP0B = TCP0B</programlisting>
<sect3 id="ora-00445pmon">
<title><errorcode>ORA-00445</errorcode> (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
This error is reported if the database is started with
the usual <command>startsap</command> script (for example
<command>startsap_majestix_00</command>) as user
<username>prdadm</username>.</para>
<para>A possible workaround is to start the database as user
@ -3021,32 +3025,32 @@ SVRMGR&gt; <userinput>exit</userinput></screen>
<sect3 id="ora-12546">
<title><errorcode>ORA-12546</errorcode> (Start Listener with Correct Permissions)</title>
<para>Start the &oracle; Listener as user
<para>Start the <application>&oracle;</application> listener as user
<username>oraids</username> with the following commands:</para>
<screen>&prompt.root; <userinput>umask 0; lsnrctl start</userinput></screen>
<para>Otherwise you might get <errorcode>ORA-12546</errorcode> as the sockets will not
have the correct permissions. See &sap; note 0072984.</para>
have the correct permissions. See &sap; Note 0072984.</para>
</sect3>
<sect3 id="ora-27102">
<title><errorcode>ORA-27102</errorcode> (Out of Memory)</title>
<para>This error happened whilst trying to use values for
<emphasis>MAXDSIZ</emphasis> and <emphasis>DFLDSIZ</emphasis>
greater than 1&nbsp;GB (1024x1024x1024). Additionally, I got
<literal>MAXDSIZ</literal> and <literal>DFLDSIZ</literal>
greater than 1&nbsp;GB (1024x1024x1024). Additionally, we got
<errorname>Linux Error 12: Cannot allocate memory</errorname>.</para>
</sect3>
<sect3 id="dipgntabindind">
<title>[DIPGNTAB_IND_IND] during R3SETUP</title>
<title>[DIPGNTAB_IND_IND] during <command>R3SETUP</command></title>
<para>In general, see &sap; note 0130581 (R3SETUP step
<para>In general, see &sap; Note 0130581 (<command>R3SETUP</command> step
<literal>DIPGNTAB</literal> terminates). During the
IDES-specific installation, for some reasons the installation
process was not using the proper &sap; system name <quote>IDS</quote>, but
the empty string "" instead. This lead to some minor problems
process was not using the proper <application>&sap;</application> system name <quote>IDS</quote>, but
the empty string <literal>""</literal> instead. This lead to some minor problems
with accessing directories, as the paths are generated
dynamically using <replaceable>SID</replaceable> (in this case IDS). So instead
of accessing:</para>
@ -3059,7 +3063,7 @@ SVRMGR&gt; <userinput>exit</userinput></screen>
<programlisting>/usr/sap//SYS/...
/usr/sap/D00</programlisting>
<para>To continue with the installation, I created a link and an
<para>To continue with the installation, we created a link and an
additional directory:</para>
<screen>&prompt.root; <userinput>pwd</userinput>
@ -3072,13 +3076,13 @@ lrwxr-xr-x 1 root sapsys 7 May 5 11:35 SYS -> IDS/SYS
drwxrwxr-x 2 idsadm sapsys 512 May 5 13:00 tmp
drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans</screen>
<para>I also found &sap; notes (0029227 and 0008401) describing
this behavior. I did not encounter any of these problems with
<para>We also found &sap; Notes (0029227 and 0008401) describing
this behavior. We did not encounter any of these problems with
the <application>&sap; 4.6C</application> installation.</para>
</sect3>
<sect3 id="rfcrswboiniindind">
<title>[RFCRSWBOINI_IND_IND] during R3SETUP</title>
<title>[RFCRSWBOINI_IND_IND] during <command>R3SETUP</command></title>
<para>During installation of <application>&sap; 4.6C</application>,
this error was just the result of another error happening
@ -3087,25 +3091,25 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans</screen>
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
<filename>CENTRDB.R3S</filename>) and restart R3SETUP. After
indeed the correct one (check the &sap; Notes), you can set
<literal>STATUS</literal> of the offending step from <literal>ERROR</literal> to <literal>OK</literal> (file
<filename>CENTRDB.R3S</filename>) and restart <command>R3SETUP</command>. After
installation, you have to execute the report
<literal>RSWBOINS</literal> from transaction SE38. See &sap;
note 0162266 for additional information about phase
Note 0162266 for additional information about phase
<literal>RFCRSWBOINI</literal> and
<literal>RFCRADDBDIF</literal>.</para>
</sect3>
<sect3 id="rfcraddbdifindind">
<title>[RFCRADDBDIF_IND_IND] during R3SETUP</title>
<para>Here the same restrictions apply: Make sure by looking
<title>[RFCRADDBDIF_IND_IND] during <command>R3SETUP</command></title>
<para>Here the same restrictions apply: make sure by looking
through the logfiles, that this error is not caused by some
previous problems.</para>
<para>If you can confirm that &sap; Note 0162266 applies, just
set STATUS of the offending step from ERROR to OK (file
<filename>CENTRDB.R3S</filename>) and restart R3SETUP. After
set <literal>STATUS</literal> of the offending step from <literal>ERROR</literal> to <literal>OK</literal> (file
<filename>CENTRDB.R3S</filename>) and restart <command>R3SETUP</command>. After
installation, you have to execute the report
<literal>RADDBDIF</literal> from transaction SE38.</para>
</sect3>
@ -3113,25 +3117,25 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans</screen>
<sect3 id="sigactionsig31">
<title><errorcode>sigaction sig31: File size limit exceeded</errorcode></title>
<para>This error occurred 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
<para>This error occurred during start of <application>&sap;</application> processes
<emphasis>disp+work</emphasis>. If starting <application>&sap;</application> with the
<command>startsap</command> script, subprocesses are then started which
detach and do the dirty work of starting all other <application>&sap;</application>
processes. As a result, the script itself will not notice
if something goes wrong.</para>
<para>To check whether the &sap; processes did start properly,
<para>To check whether the <application>&sap;</application> processes did start properly,
have a look at the process status with
<command>ps ax | grep <replaceable>SID</replaceable></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,
you a list of all <application>&oracle;</application> and <application>&sap;</application> processes. If it looks like
some processes are missing or if you cannot connect to the <application>&sap;</application> system,
look at the corresponding logfiles which can be found
at <filename>/usr/sap/<replaceable>SID</replaceable>/DVEBMGS<replaceable>nr</replaceable>/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
<application>&oracle;</application> and <application>&sap;</application> 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:
@ -3142,12 +3146,12 @@ options SHMMAXPGS=393216
</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,
<title>Start of <command>saposcol</command> Failed</title>
<para>There are some problems with the program <command>saposcol</command> (version 4.6D).
The <application>&sap;</application> system is using <command>saposcol</command> to collect data about the
system performance. This program is not needed to use the <application>&sap;</application> 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
(4.6B) does work, but does not collect all the data (many calls will
just return 0, for example for CPU usage).</para>
</sect3>
</sect2>