From 7ed11f84f3ce5a2ba4872962199440234ba36871 Mon Sep 17 00:00:00 2001 From: Martin Heinen Date: Wed, 27 Nov 2002 12:52:16 +0000 Subject: - s!<ret>!Enter! - use instead of <> - fix and tags - move hyphen out of elements - put error messages in or - add missing tags There are still many misued tags. Approved by: alex (mentor) --- .../books/handbook/linuxemu/chapter.sgml | 312 ++++++++++----------- 1 file changed, 156 insertions(+), 156 deletions(-) (limited to 'en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml') diff --git a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml index 8bf94b4038..cf61387397 100644 --- a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml @@ -227,7 +227,7 @@ Id Refs Address Size Name Let us assume you used FTP to get the Linux binary of - Doom, and put it on a Linux system you have access to. You + Doom, and put it on a Linux system you have access to. You then can check which shared libraries it needs by running ldd linuxdoom, like so: @@ -551,14 +551,14 @@ disco.example.com 7115-70839-20412 If you have not done so, order a license for Maple from Maple Waterloo Software (http://register.maplesoft.com) and copy it to - /usr/local/maple/license/license.dat + /usr/local/maple/license/license.dat Install the FLEXlm license manager by running the INSTALL_LIC install shell script that comes with Maple. Specify the primary hostname for your machine for the license - server. + server. Patch the usr/local/maple/bin/maple.system.type @@ -578,7 +578,7 @@ disco.example.com 7115-70839-20412 # We have two Linux implementations, one for Red Hat and ----- snip end of patch ----- - Please note that after the "FreeBSD"|\ no other + Please note that after the "FreeBSD"|\ no other whitespace should be present. This patch instructs Maple to @@ -593,7 +593,7 @@ disco.example.com 7115-70839-20412 The following script, installed as /usr/local/etc/rc.d/lmgrd.sh is a - convenient way to start up lmgrd: + convenient way to start up lmgrd: ----- snip ------------ @@ -657,11 +657,11 @@ FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \ ISSUED=11-may-2000 NOTICE=" Technische Universitat Wien" \ SN=XXXXXXXXX - Serial number and key 'X''ed out. "chillig" is a + Serial number and key 'X''ed out. chillig is a hostname. Editing the license file works as long as you do not - touch the "FEATURE" line (which is protected by the + touch the FEATURE line (which is protected by the license key). @@ -984,7 +984,7 @@ export PATH Please see the documentation that comes with the SAP R/3 - Linux edition for SAP- and + Linux edition for SAP- and Oracle-specific questions, as well as resources from Oracle and SAP OSS. @@ -1147,7 +1147,7 @@ export PATH - 0373203 Update / Migration Oracle 8.0.5 --> + 0373203 Update / Migration Oracle 8.0.5 --> 8.0.6/8.1.6 LINUX @@ -1318,11 +1318,11 @@ export PATH Disk Layout To keep it simple, the same disk layout both for the - SAP R/3 46B- and SAP R/3 46C - SR2-installation was used. Only the device names - changed, as the installations were on different hardware (/dev/da - and /dev/amr respectively, so if using an AMI MegaRAID, one will see - /dev/amr0s1a instead of /dev/da0s1a): + SAP R/3 46B- and SAP R/3 46C + SR2-installation was used. Only the device names + changed, as the installations were on different hardware (/dev/da + and /dev/amr respectively, so if using an AMI MegaRAID, one will see + /dev/amr0s1a instead of /dev/da0s1a): @@ -1336,52 +1336,52 @@ export PATH - /dev/da0s1a + /dev/da0s1a 1.016.303 1 - / + / - /dev/da0s1b + /dev/da0s1b 6 - <swap> + swap - /dev/da0s1e + /dev/da0s1e 2.032.623 2 - /var + /var - /dev/da0s1f + /dev/da0s1f 8.205.339 8 - /usr + /usr - /dev/da1s1e + /dev/da1s1e 45.734.361 45 - /compat/linux/oracle + /compat/linux/oracle - /dev/da1s1f + /dev/da1s1f 2.032.623 2 - /compat/linux/sapmnt + /compat/linux/sapmnt - /dev/da1s1g + /dev/da1s1g 2.032.623 2 - /compat/linux/usr/sap + /compat/linux/usr/sap @@ -1445,7 +1445,7 @@ export PATH &prompt.root; make package Linux Development has only been installed for the SAP - R/3 46B IDES- installation. It is not needed, if + R/3 46B IDES-installation. It is not needed, if the Oracle DB is not relinked on the FreeBSD system. This is the case if you are using the Oracle tarball from a linux system. @@ -1508,17 +1508,17 @@ pam-0.68-7.i386.rpm - /compat/linux/oracle + /compat/linux/oracle 45 GB - /compat/linux/sapmnt + /compat/linux/sapmnt 2 GB - /compat/linux/usr/sap + /compat/linux/usr/sap 2 GB @@ -1622,7 +1622,7 @@ ERROR 2002-03-19 16:45:36 R3LINKS_IND_IND Ins_SetupLinks:0 1000 idsadm/prdadm - <sid>adm + sidadm sapsys oper SAP Administrator @@ -1630,7 +1630,7 @@ ERROR 2002-03-19 16:45:36 R3LINKS_IND_IND Ins_SetupLinks:0 1002 oraids/oraprd - ora<sid> + orasid dba oper DB Administrator @@ -1643,26 +1643,26 @@ ERROR 2002-03-19 16:45:36 R3LINKS_IND_IND Ins_SetupLinks:0 requires the following (please note shell and home directory) entries for SAP-Administrator: - Name: <sid>adm + Name: sidadm Password: ****** -Fullname: SAP Administrator <SID> +Fullname: SAP Administrator SID Uid: 1000 Gid: 101 (sapsys) Class: Groups: sapsys dba -HOME: /home/<sid>adm +HOME: /home/sidadm Shell: bash (/compat/linux/bin/bash) and for Database-Administrator: - Name: ora<sid> + Name: orasid Password: ****** -Fullname: Oracle Administrator <SID> +Fullname: Oracle Administrator SID Uid: 1002 Gid: 100 (dba) Class: Groups: dba -HOME: /oracle/<sid> +HOME: /oracle/sid Shell: bash (/compat/linux/bin/bash) This should also include group @@ -1686,31 +1686,31 @@ Shell: bash (/compat/linux/bin/bash) &prompt.root; chmod 775 /oracle &prompt.root; chmod 777 /sapmnt &prompt.root; chown root:dba /oracle -&prompt.root; chown <sid>adm:sapsys /compat/linux/usr/sap +&prompt.root; chown sidadm:sapsys /compat/linux/usr/sap &prompt.root; chmod 775 /compat/linux/usr/sap Second we will create directories as user - ora<sid>. These + orasid. These will all be subdirectories of - /oracle/<SID>: + /oracle/SID: - &prompt.root; su - ora<sid> -&prompt.root; cd /oracle/<SID> + &prompt.root; su - orasid +&prompt.root; cd /oracle/SID &prompt.root; mkdir mirrlogA mirrlogB origlogA origlogB &prompt.root; mkdir sapdata1 sapdata2 sapdata3 sapdata4 sapdata5 sapdata6 &prompt.root; mkdir saparch sapreorg &prompt.root; exit - For the Oracle 8.1.7-installation + For the Oracle 8.1.7-installation some additional directories are needed: - &prompt.root; su - ora<sid> + &prompt.root; su - orasid &prompt.root; cd /oracle &prompt.root; mkdir 805_32 &prompt.root; mkdir client stage &prompt.root; mkdir client/80x_32 &prompt.root; mkdir stage/817_32 -&prompt.root; cd /oracle/<SID> +&prompt.root; cd /oracle/SID &prompt.root; mkdir 817_32 The directory client/80x_32 is used @@ -1718,11 +1718,11 @@ Shell: bash (/compat/linux/bin/bash) with some number or anything. In the third step we create directories as user - <sid>adm: + sidadm: - &prompt.root; su - <sid>adm + &prompt.root; su - sidadm &prompt.root; cd /usr/sap -&prompt.root; mkdir <SID> +&prompt.root; mkdir SID &prompt.root; mkdir trans &prompt.root; exit @@ -1749,7 +1749,7 @@ 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 +sapmsSID 3600/tcp # SAP Message Server. 3600 + Instance-Number sapgw00s 4800/tcp # SAP Secure Gateway 4800 + Instance-Number @@ -1823,8 +1823,8 @@ options SEMUME=100 #number of UNDO keys With the default installation of FreeBSD 4.5 on x386, leave MAXDSIZ and DFLDSIZ at 1 GB maximum. Otherwise, strange - errors like ORA-27102: out of memory and - Linux Error: 12: Cannot allocate memory + errors like ORA-27102: out of memory and + Linux Error: 12: Cannot allocate memory might happen. @@ -1840,9 +1840,9 @@ options SEMUME=100 #number of UNDO keys can just mount them all. I decided to copy the CDROM contents to corresponding directories: - /oracle/<SID>/sapreorg/<cd-name> + /oracle/SID/sapreorg/cd-name - where <cd-name> was one of KERNEL, + where cd-name was one of KERNEL, RDBMS, EXPORT1, EXPORT2, EXPORT3, EXPORT4, EXPORT5 and @@ -1852,11 +1852,11 @@ options SEMUME=100 #number of UNDO keys DISK3, DISK4 and LANG for the 4.6C SR2-installation. All the filenames on the mounted CDs should be in capital letters, - otherwise use the -g option for mounting. So use the following + otherwise use the option for mounting. So use the following commands: &prompt.root; mount_cd9660 -g /dev/cd0a /mnt -&prompt.root; cp -R /mnt/* /oracle/<SID>/sapreorg/<cd-name> +&prompt.root; cp -R /mnt/* /oracle/SID/sapreorg/cd-name &prompt.root; umount /mnt @@ -1865,14 +1865,14 @@ options SEMUME=100 #number of UNDO keys First you have to prepare an install-directory: - &prompt.root; cd /oracle/<SID>/sapreorg + &prompt.root; cd /oracle/SID/sapreorg &prompt.root; mkdir install &prompt.root; cd install Then the install-script is started, which will copy nearly all the relevant files into the install-directory: - &prompt.root; /oracle/<SID>/sapreorg/KERNEL/UNIX/INSTTOOL.SH + &prompt.root; /oracle/SID/sapreorg/KERNEL/UNIX/INSTTOOL.SH The IDES-Installation (4.6B) comes with a fully customized SAP R/3 Demo-System, so there are six instead of just three @@ -1883,7 +1883,7 @@ options SEMUME=100 #number of UNDO keys from the EXPORT1 directory, otherwise R3SETUP will only ask for three EXPORT-CDs. - The newer SAP 4.6C SR2-release + The newer SAP 4.6C SR2-release comes with four EXPORT-CDs. The parameter-file that controls the installation-steps is CENTRAL.R3S. Contrary to earlier releases there are no separate installation @@ -1897,19 +1897,19 @@ options SEMUME=100 #number of UNDO keys only, not the fully qualified domain name. So either set the hostname accordingly, or set an alias with alias hostname='hostname -s' for - both ora<sid> and - <sid>adm (and for + both orasid and + sidadm (and for root at least during installation steps performed as root). It is also possible to adjust the installed profile- and login-scripts of both users that are installed during - SAP-installation. + SAP-installation. Start R3SETUP 4.6B - Make sure LD_LIBRARY_PATH is set correctly: + Make sure LD_LIBRARY_PATH is set correctly: &prompt.root; export LD_LIBRARY_PATH=/oracle/IDS/lib:/sapmnt/IDS/exe:/oracle/805_32/lib @@ -1935,42 +1935,42 @@ options SEMUME=100 #number of UNDO keys Enter SAP System ID [C11] - IDS<ret> + IDSEnter Enter SAP Instance Number [00] - <ret> + Enter Enter SAPMOUNT Directory [/sapmnt] - <ret> + Enter Enter name of SAP central host [troubadix.domain.de] - <ret> + Enter Enter name of SAP db host [troubadix] - <ret> + Enter Select character set [1] (WE8DEC) - <ret> + Enter Enter Oracle server version (1) Oracle 8.0.5, (2) Oracle 8.0.6, (3) Oracle 8.1.5, (4) Oracle 8.1.6 - 1<ret> + 1Enter Extract Oracle Client archive [1] (Yes, extract) - <ret> + Enter Enter path to KERNEL CD @@ -1990,7 +1990,7 @@ options SEMUME=100 #number of UNDO keys Directory to copy EXPORT1 CD [/oracle/IDS/sapreorg/CD4_DIR] - <ret> + Enter Enter path to EXPORT2 CD @@ -2000,7 +2000,7 @@ options SEMUME=100 #number of UNDO keys Directory to copy EXPORT2 CD [/oracle/IDS/sapreorg/CD5_DIR] - <ret> + Enter Enter path to EXPORT3 CD @@ -2010,7 +2010,7 @@ options SEMUME=100 #number of UNDO keys Directory to copy EXPORT3 CD [/oracle/IDS/sapreorg/CD6_DIR] - <ret> + Enter Enter path to EXPORT4 CD @@ -2020,7 +2020,7 @@ options SEMUME=100 #number of UNDO keys Directory to copy EXPORT4 CD [/oracle/IDS/sapreorg/CD7_DIR] - <ret> + Enter Enter path to EXPORT5 CD @@ -2030,7 +2030,7 @@ options SEMUME=100 #number of UNDO keys Directory to copy EXPORT5 CD [/oracle/IDS/sapreorg/CD8_DIR] - <ret> + Enter Enter path to EXPORT6 CD @@ -2040,47 +2040,47 @@ options SEMUME=100 #number of UNDO keys Directory to copy EXPORT6 CD [/oracle/IDS/sapreorg/CD9_DIR] - <ret> + Enter Enter amount of RAM for SAP + DB - 850<ret> (in Megabytes) + 850Enter (in Megabytes) Service Entry Message Server [3600] - <ret> + Enter Enter Group-ID of sapsys [101] - <ret> + Enter Enter Group-ID of oper [102] - <ret> + Enter Enter Group-ID of dba [100] - <ret> + Enter - Enter User-ID of <sid>adm + Enter User-ID of sidadm [1000] - <ret> + Enter - Enter User-ID of ora<sid> + Enter User-ID of orasid [1002] - <ret> + Enter Number of parallel procs [2] - <ret> + Enter @@ -2106,7 +2106,7 @@ options SEMUME=100 #number of UNDO keys Start R3SETUP 4.6C SR2 - Make sure LD_LIBRARY_PATH is set correctly. This is a + Make sure LD_LIBRARY_PATH is set correctly. This is a different value from the 4.6B installation with Oracle 8.0.5: @@ -2133,47 +2133,47 @@ options SEMUME=100 #number of UNDO keys Enter SAP System ID [C11] - PRD<ret> + PRDEnter Enter SAP Instance Number [00] - <ret> + Enter Enter SAPMOUNT Directory [/sapmnt] - <ret> + Enter Enter name of SAP central host [majestix] - <ret> + Enter Enter Database System ID [PRD] - PRD<ret> + PRDEnter Enter name of SAP db host [majestix] - <ret> + Enter Select character set [1] (WE8DEC) - <ret> + Enter Enter Oracle server version (2) Oracle 8.1.7 - 2<ret> + 2Enter Extract Oracle Client archive [1] (Yes, extract) - <ret> + Enter Enter path to KERNEL CD @@ -2183,52 +2183,52 @@ options SEMUME=100 #number of UNDO keys Enter amount of RAM for SAP + DB 2044 - 1800<ret> (in Megabytes) + 1800Enter (in Megabytes) Service Entry Message Server [3600] - <ret> + Enter Enter Group-ID of sapsys [100] - <ret> + Enter Enter Group-ID of oper [101] - <ret> + Enter Enter Group-ID of dba [102] - <ret> + Enter Enter User-ID of oraprd [1002] - <ret> + Enter Enter User-ID of prdadm [1000] - <ret> + Enter LDAP support - 3<ret> (no support) + 3Enter (no support) Installation step completed [1] (continue) - <ret> + Enter Choose installation service [1] (DB inst,file) - <ret> + Enter @@ -2236,9 +2236,9 @@ options SEMUME=100 #number of UNDO keys So far, creation of users gives an error during installation in phases OSUSERDBSID_IND_ORA (for creating - user ora<sid>) and + user orasid) and OSUSERSIDADM_IND_ORA (creating user - <sid>adm). + sidadm). Apart from some problems mentioned below, everything should go straight through up to the point where the Oracle @@ -2296,7 +2296,7 @@ options SEMUME=100 #number of UNDO keys &prompt.root; cd /ORACLE_HOME/orainst_sap &prompt.root; ./orainst - Confirm all Screens with Enter until the software is + Confirm all Screens with Enter until the software is installed, except that one has to deselect the Oracle On-Line Text Viewer, as this is not currently available for Linux. Oracle then wants to @@ -2333,7 +2333,7 @@ options SEMUME=100 #number of UNDO keys Installing the Oracle 8.1.7 linux tarball Take the tarball oracle81732.tgz you produced from the installation directory on a linux system - and untar it to /oracle/<SID>/817_32/ + and untar it to /oracle/SID/817_32/ @@ -2341,8 +2341,8 @@ options SEMUME=100 #number of UNDO keys First check the environment settings of users idsamd - (<sid>adm) and - oraids (ora<sid>). They should now + (sidadm) and + oraids (orasid). They should now both have the files .profile, .login and .cshrc which are all using hostname. In case the @@ -2375,27 +2375,27 @@ options SEMUME=100 #number of UNDO keys Enter Password for sapr3 - sap<ret> + sapEnter Confirum Password for sapr3 - sap<ret> + sapEnter Enter Password for sys - change_on_install<ret> + change_on_installEnter Confirm Password for sys - change_on_install<ret> + change_on_installEnter Enter Password for system - manager<ret> + managerEnter Confirm Password for system - manager<ret> + managerEnter @@ -2410,11 +2410,11 @@ options SEMUME=100 #number of UNDO keys Listener Start the Oracle-Listener as user - ora<sid> as follows: + orasid as follows: &prompt.user; umask 0; lsnrctl start - Otherwise you might get ORA-12546 as the sockets will not + Otherwise you might get ORA-12546 as the sockets will not have the correct permissions. See SAP note 072984. @@ -2452,11 +2452,11 @@ options SEMUME=100 #number of UNDO keys You are then required to enter the following values: - SAP SYSTEM ID = <SID, 3 chars> -CUSTOMER KEY = <hardware key, 11 chars> -INSTALLATION NO = <installation, 10 digits> -EXPIRATION DATE = <yyyymmdd, usually "99991231"> -LICENSE KEY = <license key, 24 chars> + SAP SYSTEM ID = SID, 3 chars +CUSTOMER KEY = hardware key, 11 chars +INSTALLATION NO = installation, 10 digits +EXPIRATION DATE = yyyymmdd, usually "99991231" +LICENSE KEY = license key, 24 chars @@ -2512,7 +2512,7 @@ LICENSE KEY = <license key, 24 chars> - Edit init<sid>.sap (initIDS.sap) + Edit init<replaceable>sid</replaceable>.sap (initIDS.sap) The file /oracle/IDS/dbs/initIDS.sap contains the SAP backup profile. Here the size of the tape to @@ -2530,17 +2530,17 @@ tape_address_rew = /dev/sa0 Explanations: - compress The tape I use is a HP DLT1 + compress The tape I use is a HP DLT1 which does hardware compression. - archive_function This defines the + archive_function 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. - cpio_flags Default is to use -B which + cpio_flags Default is to use -B which sets blocksize to 5120 Bytes. For DLT-Tapes, HP recommends at least 32 K blocksize, so I used --block-size=128 for 64 K. --format=newc is needed I have inode numbers greater than @@ -2549,20 +2549,20 @@ tape_address_rew = /dev/sa0 complains as soon as cpio outputs the numbers of blocks saved. - cpio_in_flags Flags needed for + cpio_in_flags Flags needed for loading data back from tape. Format is recognized automagically. - tape_size This usually gives the raw + tape_size 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. - tape_address The non-rewindable + tape_address The non-rewindable device to be used with cpio. - tape_address_rew The rewindable device to be - used with cpio. + tape_address_rew The rewindable device to be + used with cpio. @@ -2650,9 +2650,9 @@ tape_address_rew = /dev/sa0 With the above parameters, on a system with 1 gigabyte - of memory, one may find memory consumption similar to: + of memory, one may find memory consumption similar to: - Mem: 547M Active, 305M Inact, 109M Wired, 40M Cache, 112M Buf, 3492K Free + Mem: 547M Active, 305M Inact, 109M Wired, 40M Cache, 112M Buf, 3492K Free @@ -2669,7 +2669,7 @@ tape_address_rew = /dev/sa0 as option for the last step R3SETUP complained about. To restart R3SETUP, just start it with the corresponding - R3S-file: + R3S-file: &prompt.root; ./R3SETUP -f CENTRDB.R3S for 4.6B, or with &prompt.root; ./R3SETUP -f CENTRAL.R3S @@ -2684,7 +2684,7 @@ tape_address_rew = /dev/sa0 and SAP by hand after you fixed the errors and before starting R3SETUP again. Don't forget to also start the oracle listener again (as - ora<sid> with + orasid with umask 0; lsnrctl start) if it was also stopped (for example due to a necessary reboot of the system). @@ -2703,7 +2703,7 @@ tape_address_rew = /dev/sa0 only STATUS=ERROR-entry and edit the following values: - HOME=/home/<sid>adm (was empty) + HOME=/home/sidadm (was empty) STATUS=OK (had status ERROR) @@ -2730,7 +2730,7 @@ STATUS=OK (had status ERROR) - oraview.vrf FILE NOT FOUND During Oracle Installation + <errorname>oraview.vrf FILE NOT FOUND</errorname> During Oracle Installation You have not deselected Oracle On-Line Text Viewer before starting the installation. This is marked for installation even @@ -2739,7 +2739,7 @@ STATUS=OK (had status ERROR) - TEXTENV_INVALID During R3SETUP, RFC or SAPGUI Start + <errorname>TEXTENV_INVALID</errorname> During R3SETUP, RFC or SAPGUI Start If this error is encountered, the correct locale is missing. SAP note 0171356 lists the necessary RPMs that need @@ -2784,20 +2784,20 @@ rscp/TCP0B = TCP0B - ORA-00001 + <errorcode>ORA-00001</errorcode> This error only happened with Oracle 8.1.7 on FreeBSD 4.5. The reason was that the Oracle database could not initialize itself properly and crashed, leaving semaphores and shared memory on the system. The next try to start the database then returned - ORA-00001. + ORA-00001. Find them with ipcs -a and remove them with ipcrm. - ORA-00445 (background process PMON did not start) + <errorcode>ORA-00445</errorcode> (background process PMON did not start) This error happened with Oracle 8.1.7. This error is reported if the Database is started with the usual startsap-script (for example @@ -2816,24 +2816,24 @@ SVRMGR> exit - ORA-12546 (start Listener with Correct Permissions) + <errorcode>ORA-12546</errorcode> (start Listener with Correct Permissions) Start the Oracle Listener as user oraids with the following commands: &prompt.root; umask 0; lsnrctl start - Otherwise you might get ORA-12546 as the sockets will not + Otherwise you might get ORA-12546 as the sockets will not have the correct permissions. See SAP note 0072984. - ORA-27102 (out of memory) + <errorcode>ORA-27102</errorcode> (out of memory) This error happend whilst trying to use values for MAXDSIZ and DFLDSIZ greater than 1 GB (1024x1024x1024). Additionally, I got - Linux Error 12: Cannot allocate memory. + Linux Error 12: Cannot allocate memory. @@ -2842,10 +2842,10 @@ SVRMGR> exit In general, see SAP note 0130581 (R3SETUP step DIPGNTAB terminates). During the IDES-specific installation, for some reasons the installation - process was not using the proper SAP system name "IDS", but + process was not using the proper SAP system name IDS, but the empty string "" instead. This lead to some minor problems with accessing directories, as the paths are generated - dynamically using <SID> (in this case IDS). So instead + dynamically using SID (in this case IDS). So instead of accessing: /usr/sap/IDS/SYS/... @@ -2871,7 +2871,7 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans I also found SAP notes (0029227 and 0008401) describing this behavior. I did not encounter any of these problems with - the SAP 4.6C-Installation. + the SAP 4.6C-installation. @@ -2919,11 +2919,11 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans To check whether the SAP processes did start properly, have a look at the process status with - ps ax | grep <SID>, which will give + ps ax | grep SID, which will give you a list of all Oracle- and SAP-processes. If it looks like some processes are missing or if you can't connect to the SAP-System, look at the corresponding logfiles which can be found - at /usr/sap/<SID>/DVEBMGS<nr>/work/. + at /usr/sap/SID/DVEBMGSnr/work/. The files to look at are dev_ms and dev_disp. -- cgit v1.2.3