Installations of SAP Systems using FreeBSD will not be supported by the SAP support team -- they only offer support for certified platforms.
This document describes a possible way of installing a SAP R/3 4.6B IDES-System with Oracle 8.0.5 for Linux onto a FreeBSD 4.3 machine, including the installation of FreeBSD 4.3-STABLE and Oracle 8.0.5.
Even though this document tries to describe all important steps in a greater detail, it is not intended as a replacement for the Oracle and SAP R/3 installation guides.
Please see the documentation that comes with the SAP R/3 Linux edition for SAP- and Oracle-specific questions, as well as resources from Oracle and SAP OSS.
The following CDROMs have been used for SAP-installation:
|KERNEL||51009113||SAP Kernel Oracle / Installation / AIX, Linux, Solaris|
|RDBMS||51007558||Oracle / RDBMS 8.0.5.X / Linux|
|EXPORT1||51010208||IDES / DB-Export / Disc 1 of 6|
|EXPORT2||51010209||IDES / DB-Export / Disc 2 of 6|
|EXPORT3||51010210||IDES / DB-Export / Disc3 of 6|
|EXPORT4||51010211||IDES / DB-Export / Disc4 of 6|
|EXPORT5||51010212||IDES / DB-Export / Disc5 of 6|
|EXPORT6||51010213||IDES / DB-Export / Disc6 of 6|
Additionally, I used the Oracle 8 Server (Pre-production version 8.0.5 for Linux, Kernel Version 2.0.33) CD which is not really necessary, and of course FreeBSD 4.3 stable (it was only a few days past 4.3 RELEASE).
The following notes should be read before installing SAP R/3 or proved to be useful during installation:
|0171356||SAP Software auf Linux: grundlegenden Anmerkungen|
|0201147||INST: 4.6C R/3 Inst. on UNIX - Oracle|
|0373203||Update / Migration Oracle 8.0.5 --> 8.0.6/8.1.6 LINUX|
|0072984||Release of Digital UNIX 4.0B for Oracle|
|0130581||R3SETUP step DIPGNTAB terminates|
|0144978||Your system has not been installed correctly|
|0162266||Questions and tips for R3SETUP on Windows NT / W2K|
The following equipment is sufficient for a SAP R/3 System (4.6B):
|Processor||2 x 800MHz Pentium III||2 x 800MHz Pentium III|
|Memory||1GB ECC||2GB ECC|
|Hard Disc Space||50-60GB (IDES)||50-60GB (IDES)|
For use in production, Xeon-Processors with large cache, high-speed disc access (SCSI, RAID hardware controller), USV and ECC-RAM is recommended. The large amount of Hard disc space is due to the preconfigured IDES System, which creates 27 GB of database files during installation. Usually after installation it is then necessary to extend some tablespaces.
I used a dual processor board with 2 800MHz Pentium III processors, Adaptec 29160 Ultra160 SCSI adapter (for accessing a 40/80 GB DLT tape drive and CDROM), Mylex AcelleRAID (2 channels, firmware 6.00-1-00 with 32MB RAM). To the Mylex Raid-controller are attached two 17GB hard discs (mirrored) and four 36GB hard discs (RAID level 5).
First I installed FreeBSD 4.3 stable. I did the default-installation via FTP.
Get the diskimages kern.flp and mfsroot.flp and put them on floppy disks (I got mine from ftp7.de.freebsd.org. Please choose the appropriate mirror).
# dd if=kern.flp of=/dev/fd0 # dd if=mfsroot.flp of=/dev/fd0
Do not forget to use different disks for the two images, then boot from the floppy with the kern.flp-image on it and follow instructions. I used the following disk layout:
|Filesystem||Size (1k-blocks)||Size (GB)||Mounted on|
I had to configure and initialize the two logical drives with the Mylex software beforehand. It is located on the board itself and can be started during the boot phase of the PC.
Please note that this disk layout differs slightly from the SAP recommendations, as SAP suggests mounting the oracle-subdirectories (and some others) separately - I decided to just create them as real subdirectories for simplicity.
For FreeBSD 4.3 stable onwards, it is quite easy to get the latest stable sources. With the older versions of FreeBSD, I had my own script located in /etc/cvsup. Setting up CVSup for FreeBSD 4.3 is quite easy. As user root do the following:
# cp /etc/defaults/make.conf /etc/make.conf # vi /etc/make.conf
The file /etc/make.conf requires the following entries to be active:
SUP_UPDATE= yes SUP= /usr/local/bin/cvsup SUPFLAGS= -g -L 2 SUPHOST= cvsup8.FreeBSD.org SUPFILE= /usr/share/examples/cvsup/stable-supfile PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile
Change the SUPHOST-value appropriately. The supfiles in /usr/share/examples/cvsup should be fine. If you do not want to load all the docfiles, leave the corresponding DOCSUPFILE-entry inactive. Starting cvsup to get the latest stable-sources is then very easy:
# cd /usr/src # make update
The first thing to do is to install the sources. As user root, do the following:
# cd /usr/src # make world
If this goes through, one can then continue creating and configuring the new kernel. Usually this is where to customize the kernel configuration file. As the computer is named troubadix, the natural name for the config file also is troubadix:
# cd /usr/src/sys/i386/conf # cp GENERIC TROUBADIX # vi TROUBADIX
At this stage one can define the drivers to use and not to use, etc. See the appropriate documentation or have a look at file LINT for some additional explanations.
One can then also include the parameters as described below Creating the new kernel then requires:
# cd /usr/src/sys/i386/conf # config TROUBADIX # cd /usr/src/sys/compile/TROUBADIX # make depend # make # make install
After make install finished successfully, one should reboot the computer to have the new kernel available.
I had some trouble downloading the required RPM-files (for 4.3 stable, 2nd May 2001), so you might try one of the following locations (if all the others fail and the following are not out of date):
First the Linux base-system needs to be installed (as root):
# cd /usr/ports/emulators/linux_base # make package
Next, the Linux development is needed:
# cd /usr/ports/devel/linux_devtools # make package
To start the R3SETUP-Program, pam support is needed. As this also requires some other packages, I ended up installing several packages. After that, pam still complained about a missing package, so I forced the installation and it worked. I wonder if the other packages are really needed or if it would have been sufficient to install the pam-package.
Anyway, here is the list of packages I installed:
I installed these packages with the following command:
# rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm <package_name>
except for the pam package, which I forced with
# rpm -i --ignoreos --nodeps --root /compat/linux --dbpath /var/lib/rpm \ pam-0.68-7.i386.rpm
For Oracle to run the intelligent agent, I also had to install the following RedHat Tcl package (as is stated in the FreeBSD Handbook): tcl-8.0.5-30.i386.rpm (otherwise the relinking during Oracle install will not work). There are some other issues regarding relinking of Oracle, but that is a Oracle-Linux issue, not FreeBSD specific as far as I understand it.
For a simple installation, it is sufficient to create the following filesystems:
|mountpoint||size in GB|
I also created some links, so FreeBSD will also find the correct path:
# ln -s /compat/linux/oracle /oracle # ln -s /compat/linux/sapmnt /sapmnt # ln -s /compat/linux/usr/sap /usr/sap
SAP R/3 needs two users and three groups. The usernames depend on the SAP system id (SID) which consists of three letters. Some of these SIDs are reserved by SAP (for example SAP and NIX. For a complete list please see the SAP documentation). For the IDES installation I used IDS. We have therefore the following groups (group ids might differ, these are just the values I used with my installation):
|group id||group name||description|
|100||dba||Data Base Administrator|
|102||oper||Data Base Operator|
For a default Oracle-Installation, only group dba is used. As oper-group, one also uses group dba (see Oracle- and SAP-documentation for further information).
We also need the following users:
|user id||username||generic name||group||additional groups||description|
Adding the users with adduser requires the following (please note shell and home directory) entries for SAP-Administrator:
Name: idsadm <sid>adm Password: ****** Fullname: SAP IDES Administrator Uid: 1000 Gid: 101 (sapsys) Class: Groups: sapsys dba HOME: /home/idsadm /home/<sid>adm Shell: /bin/sh
and for Database-Administrator:
Name: oraids ora<sid> Password: ****** Fullname: Oracle IDES Administrator Uid: 1002 Gid: 100 (dba) Class: Groups: dba HOME: /oracle/IDS /oracle/<sid> Shell: /bin/sh
This should also include group oper in case you are using both groups dba and oper.
These directories are usually created as separate filesystems. This depends entirely on your requirements. I choose to create them as simple directories, as they are all located on the same RAID 5 anyway:
First we will set owners and right of some directories (as user root):
# chmod 775 /oracle # chmod 777 /sapmnt # chown root:dba /oracle # chown idsadm:sapsys /compat/linux/usr/sap # chmow 775 /compat/linux/usr/sap
Second we will create directories as user ora<sid>. These will all be subdirectories of /oracle/IDS:
# su - oraids # mkdir mirrlogA mirrlogB origlogA origlogB # mkdir sapdata1 sapdata2 sapdata3 sapdata4 sapdata5 sapdata6 # mkdir saparch sapreorg # exit
In the third step we create directories as user idsadm (<sid>adm):
# su - idsadm # cd /usr/sap # mkdir IDS # mkdir trans # exit
SAP R/3 requires some entries in file /etc/services , 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, 00. It'll do no harm adding all entries from 00 to 99 for dp, gw, sp and ms);
sapdp00 3200/tcp # SAP Dispatcher. 3200 + Instance-Number sapgw00 3300/tcp # SAP Gateway. 3300 + Instance-Number sapsp00 3400/tcp # 3400 + Instance-Number sapms00 3500/tcp # 3500 + Instance-Number sapmsIDS 3600/tcp # SAP Message Server. 3600 + Instance-Number
SAP 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.
It is also possible to just create appropriate links (for example from de_DE and en_US ), but I 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:
If they are not present, there will be some problems during the installation. If these are then subsequently ignored (eg by setting the status of the offending steps to OK in file CENTRDB.R3S), it will be impossible to log onto the SAP-system without some additional effort.
SAP R/3 Systems need a lot of resources. I therefore added the following parameters to my kernel config-file:
# 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 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 indentifiers options SEMUME=100 #number of UNDO keys
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.
There are lots of CDROMs to mount and unmount during installation. Assuming you have enough CDROM-drives, you can just mount them all. I decided to copy the CDROM contents to corresponding directories:
where <cd-name> was one of KERNEL, RDBMS, EXPORT1, EXPORT2, EXPORT3, EXPORT4, EXPORT5 and EXPORT6. All the filenames should be in capital letters, otherwise use the -g option for mounting. So use the following commands:
# mount_cd9660 -g /dev/cd0a /mnt # cp -R /mnt/* /oracle/IDS/sapreorg/<cd-name> # umount /mnt
First we need to prepare an install-directory:
# cd /oracle/IDS/sapreorg # mkdir install # cd install
Then the install-script is started, which will copy nearly all the relevant files into the install-directory:
As this is an IDES-Installation with a fully customized SAP R/3 Demo-System, we have six instead of just three EXPORT-CDs. At this point the installation template CENTRDB.R3S is for installing a standard central instance (R/3 and Database), not an IDES central instance, so copy the corresponding CENTRDB.R3S from the EXPORT1 directory, otherwise R3SETUP will only ask for three EXPORT-CDs.
Make sure LD_LIBRARY_PATH is set correctly:
# export LD_LIBRARY_PATH=/oracle/IDS/lib:/sapmnt/IDS/exe:/oracle/805_32/lib
Start R3SETUP as user root from installation directory:
# cd /oracle/IDS/sapreorg/install # ./R3SETUP -f CENTRDB.R3S
The script then asks some questions (defaults in brackets, followed by actual input):
|Enter SAP System ID||[C11]||IDS<ret>|
|Enter SAP Instance Number||||<ret>|
|Enter SAPMOUNT Directory||[/sapmnt]||<ret>|
|Enter name of SAP central host||[troubadix.domain.de]||<ret>|
|Enter name of SAP db host||[troubadix]||<ret>|
|Select character set|| (WE8DEC)||<ret>|
|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>|
|Extract Oracle Client archive|| (Yes, extract)||<ret>|
|Enter path to KERNEL CD||[/sapcd]||/oracle/IDS/sapreorg/KERNEL|
|Enter path to RDBMS CD||[/sapcd]||/oracle/IDS/sapreorg/RDBMS|
|Enter path to EXPORT1 CD||[/sapcd]||/oracle/IDS/sapreorg/EXPORT1|
|Directory to copy EXPORT1 CD||[/oracle/IDS/sapreorg/CD4_DIR]||<ret>|
|Enter path to EXPORT2 CD||[/sapcd]||/oracle/IDS/sapreorg/EXPORT2|
|Directory to copy EXPORT2 CD||[/oracle/IDS/sapreorg/CD5_DIR]||<ret>|
|Enter path to EXPORT3 CD||[/sapcd]||/oracle/IDS/sapreorg/EXPORT3|
|Directory to copy EXPORT3 CD||[/oracle/IDS/sapreorg/CD6_DIR]||<ret>|
|Enter path to EXPORT4 CD||[/sapcd]||/oracle/IDS/sapreorg/EXPORT4|
|Directory to copy EXPORT4 CD||[/oracle/IDS/sapreorg/CD7_DIR]||<ret>|
|Enter path to EXPORT5 CD||[/sapcd]||/oracle/IDS/sapreorg/EXPORT5|
|Directory to copy EXPORT5 CD||[/oracle/IDS/sapreorg/CD8_DIR]||<ret>|
|Enter path to EXPORT6 CD||[/sapcd]||/oracle/IDS/sapreorg/EXPORT6|
|Directory to copy EXPORT6 CD||[/oracle/IDS/sapreorg/CD9_DIR]||<ret>|
|Enter amount of RAM for SAP + DB||850<ret> (in Megabytes)|
|Service Entry Message Server||||<ret>|
|Enter Group-ID of sapsys||||<ret>|
|Enter Group-ID of oper||||<ret>|
|Enter Group-ID of dba||||<ret>|
|Enter User-ID of <sid>adm||||<ret>|
|Enter User-ID of ora<sid>||||<ret>|
|Number of parallel procs||||<ret>|
If I had not copied the CDs to the different locations, then the SAP-Installer cannot find the CD needed (identified by the LABEL.ASC-File on CD) and would then ask you to insert / mount the CD and confirm or enter the mount path.
The CENTRDB.R3S might not be error-free. In my case, it requested EXPORT4 again (but indicated the correct key (6_LOCATI ON, then 7_LOCATION etc.), so one can just continue with entering the correct values. Do not get irritated.
Apart from some problems mentioned below, everything should go straight through up to the point where the Oracle database software needs to be installed.
Please see the corresponding SAP-Notes and Oracle Readmes regarding Linux and Oracle DB for possible problems. Most if not all problems stem from incompatible libraries
For more information on installing Oracle, refer to the Installing Oracle chapter.
If Oracle 8.0.5 is to be used, some additional libraries are needed for successfully relinking, as Oracle 8.0.5 was linked with an old glibc (RedHat 6.0), but RedHat 6.1 already uses a new glibc. So you have to install the following additional packages to ensure that linking will work:
See the corresponding SAP-Notes or Oracle Readmes for further information. If this is no option (at the time of installation I did not have enough time to check this), one could use the original binaries, or use the relinked binaries from an original RedHat System.
For compiling the intelligent agent, the RedHat Tcl package must be installed. If you cannot get tcl-8.0.3-20.i386.rpm, a newer one like tcl-8.0.5-30.i386.rpm for RedHat 6.1 should also do.
Apart from relinking, the installation is straightforward:
# su - oraids # export TERM=xterm # export ORACLE_TERM=xterm # export ORACLE_HOME=/oracle/IDS # cd /ORACLE_HOME/orainst_sap # ./orainst
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 relink with i386-glibc20-linux-gcc instead of the available gcc, egcs or i386-redhat-linux-gcc .
Due to time constrains I decided to use the binaries from an Oracle 8.0.5 PreProduction release, after the first attempt at getting the version from the RDBMS-CD working, failed, and finding / accessing the correct RPMs was a nightmare at that time.
This installation is quite easy. Mount the CD, start the installer. It will then ask for the location of the Oracle home directory, and copy all binaries there. I did not delete the remains of my previous RDBMS-installation tries, though.
Afterwards, Oracle Database could be started with no problems.
First check the environment settings of users idsamd (<sid>adm) and oraids (ora<sid>). They should now both have the files .profile , .login and .cshrc which are all using hostname. In case the system's hostname is the fully qualified name, you need to change hostname to hostname -s within all three files.
Afterwards, R3SETUP can either be restarted or continued (depending on whether exit was chosen or not). R3SETUP then creates the tablespaces and loads the data from EXPORT1 to EXPORT6 (remember, it is an IDES system, otherwise it would only be EXPORT1 to EXPORT3) with R3load into the database.
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!):
|Enter Password for sapr3||sap<ret>|
|Confirum Password for sapr3||sap<ret>|
|Enter Password for sys||change_on_install<ret>|
|Confirm Password for sys||change_on_install<ret>|
|Enter Password for system||manager<ret>|
|Confirm Password for system||manager<ret>|
At this point I had a few problems with dipgntab.
Start the Oracle-Listener as user oraids (ora<sid>) as follows:
umask 0; lsnrctl start
Otherwise you might get ORA-12546 as the sockets will not have the correct permissions. See SAP note 072984.
This is needed, as the temporary license is only valid for four weeks. Do not forget to enter the correct Operating System: (X) Other: FreeBSD 4.3 Stable. First get the hardware key. Log on as user idsadm and call saplicense:
# /sapmnt/IDS/exe/saplicense -get
Calling saplicense without options gives a list of options. Upon receiving the license key, it can be installed using
# /sapmnt/IDS/exe/saplicense -install
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>
Create a user within client 000 (for some tasks required to be done within client 000, but with a user different from users sap* and ddic). As a username, I usually choose wartung (or service in English). Profiles required are sap_new and sap_all. For additional safety the passwords of default users within all clients should be changed (this includes users sap* and ddic).
Within client 000, user different from ddic and sap*, do at least the following:
|Configure Transport System, eg as Stand-Alone Transport Domain Entity||STMS|
|Create / Edit Profile for System||RZ10|
|Maintain Operation Modes and Instances||RZ04|
These and all the other post-installation steps are thoroughly described in SAP installation guides.
The file /oracle/IDS/dbs/initIDS.sap contains the SAP 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 sapdba / brbackup, I changed the following values:
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
compress The tape I use is a HP DLT1 which does hardware compression.
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 one needs to recover the database, and one of the archive-tapes has gone bad.
cpio_flags Default is to use -B which sets blocksize to 5120 Bytes. For DLT-Tapes, HP recommends at least 32K blocksize, so I used --block-size=128 for 64K. --format=newc is needed I have inode numbers greater than 65535. The last option --quiet is needed as otherwise brbackup complains as soon as cpio outputs the numbers of blocks saved.
cpio_in_flags Flags needed for loading data back from tape. Format is recognized automagically.
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 device to be used with cpio.
tape_address_rew The rewindable device to be used with cpio.
The following SAP-parameters should be tuned after installation:
Note: With the above parameters, on a system with 1 gigabyte of memory, one may find memory consumption similar to:Mem: 547M Active, 305M Inact, 109M Wired, 40M Cache, 112M Buf, 3492K Free
If R3SETUP complains at this stage, edit file CENTRDB.R3S. Locate [OSUSERSIDADM_IND_ORA] and edit the following values:
HOME=/home/idsadm (was empty) STATUS=OK (had status ERROR)
Then you can restart R3SETUP with:
# ./R3SETUP -f CENTRDB.R3S
Possibly R3SETUP also complains at this stage. Just edit CENTRDB.R3S. Locate [OSUSERDBSID_IND_ORA] and edit the following value in that section:
Then just restart R3SETUP again:
# ./R3SETUP -f CENTRDB.R3S
You have not deselected Oracle On-Line Text Viewer 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.
If this error is encountered, the correct locale is missing. SAP note 0171356 lists the necessary RPMs that need be installed (eg saplocales-1.0-3, saposcheck-1.0-1 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 be properly configured and you will then not be able to connect to the system with a sapgui, even though the system can be started. Trying to connect with the old Linux sapgui gave the following messages:
Sat May 5 14:23:14 2001 *** ERROR => no valid userarea given [trgmsgo. 0401] Sat May 5 14:23:22 2001 *** ERROR => ERROR NR 24 occured [trgmsgi. 0410] *** ERROR => Error when generating text environment. [trgmsgi. 0435] *** ERROR => function failed [trgmsgi. 0447] *** ERROR => no socket operation allowed [trxio.c 3363] Speicherzugriffsfehler
This behavior is due to SAP R/3 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 DEFAULT.PFL (see note 0043288):
abap/set_etct_env_at_new_mode =0 install/collate/active =0 rscp/TCP0B =TCP0B
Restart the SAP system. Now one can connect to the system, even though country-specific language settings might not work as expected. After correcting country-settings (and providing the correct locales), these entries can be removed from DEFAULT.PFL and the SAP system can be restarted.
Start the Oracle Listener as user oraids with the following commands:
# umask 0; lsnrctl start
Otherwise one might get ORA-12546 as the sockets will not have the correct permissions. See SAP note 0072984.
In general, see SAP note 0130581 (R3SETUP step DIPGNTAB terminates). During this specific installation, for some reasons the installation 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 of accessing:
the following path were used:
To continue with the installation, I created a link and an additional directory:
# pwd /compat/linux/usr/sap # ls -l total 4 drwxr-xr-x 3 idsadm sapsys 512 May 5 11:20 D00 drwxr-x--x 5 idsadm sapsys 512 May 5 11:35 IDS 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
I also found SAP notes (0029227 and 0008401) describing this behavior.
Set STATUS of the offending step from ERROR to OK (file CENTRDB.R3S) and restart R3SETUP. After installation, you have to execute the report RSWBOINS from transaction SE38. See SAP note 0162266 for additional information about phase RFCRSWBOINI and RFCRADDBDIF.
Set STATUS of the offending step from ERROR to OK (file CENTRDB.R3S) and restart R3SETUP. After installation, you have to execute the report RADDBDIF from transaction SE38. See SAP note 0162266 for further information.
This, and other documents, can be downloaded from ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/.
For questions about FreeBSD, read the
before contacting <questions@FreeBSD.org>.
For questions about this documentation, e-mail <doc@FreeBSD.org>.