on 03-13-2008 2:18 PM
I'm having problems installing the NW$ testdrive on Opensuse 10.3. When I issue the command :
./install.sh
I get the following output:
rm: cannot remove '/usr/lib/java': Is a directory
ln: creating a symbolic link '/usr/lib/java/java-1.5.0-sun_update12' : File exists
The package sapj2ee-srv-sapdb-6.40-2 is already installed.
The package sapdb-7.5-2 is already installed.
The package sapdb-db-log-7.5-2 is already installed.
The package sapdb-db-files-7.5-2 is already installed.
Found interface: eth0 . Alias is eth0:0
ifconfig eth0:0 195.155.155.1 up
uname: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
uname: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
uname: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
sed: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory
sed: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory
uname: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
tty: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory
uname: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
awk: error while loading shared libraries: libdl.so.2: cannot open shared object
file: No such file or directory
rm: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory
/sapdb/programs/bin/xuser: error while loading shared libraries: libdl.so.2:
cannot open shared object file: No such file or directory
[: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory
could not write db password file for nw4adm
Creation of .XUSER.62 failed.
Here are the outputs from system queries that were recommended on other threads with the same issues:
uname -a
Linux NW4linux 2.6.22.5-31-default #1 SMP 2007/09/21 22:29:00 UTC i686 i6
86 i386 GNU/Linux
file /sapdb/programs/bin/xuser
/sapdb/programs/bin/xuser: ELF 32-bit LSB executable, Intel 80386, version 1 (SY
SV), for GNU/Linux 2.0.0, dynamically linked (uses shared libs), not stripped
ldd /sapdb/programs/bin/xuser
linux-gate.so.1 => (0xffffe000)
libdl.so.2 => /lib/libdl.so.2 (0xb7fc1000)
librt.so.1 => /lib/librt.so.1 (0xb7fb8000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7f86000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb7f6f000)
libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0xb7f22000
0)
libm.so.6 => /lib/libm.so.6 (0xb7efd000)
libc.so.6 => /lib/libc.so.6 (0xb7dc9000)
/lib/ld-linux.so.2 (0xb7fd0000)
echo $LD_ASSUME_KERNEL
rpm -q --queryformat %{NAME}.%{ARCH}\\n compat-libstdc++-33
package compat-libstdc++-33 is not installed
rpm -V compat-libstdc++-33
package compat-libstdc++-33 is not installed
I would appreciate anyone's help.
Thanks
Hey Conrad,
I have another idea. As i remember correctly, the SAP 640 kernel binaries are build with gcc 296. Therefore, please check that you have the compat-libstdc++ for gcc 2.96 installed. If I remember correctly, the rpm is named compat-libstdc++-5.0.7-86.i586.rpm. Maybe you can give it a shot.
If this does not work, OpenSUSE 10.3 is too new. Maybe check with OpenSUSE10.1 or later...
Thanks
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
On OpenSUSE 10.2 it installs also.
But I advise to install on SLES 10. It already includes SUSE-sapinit RPM package and is officially supported.
Though sapinit.rpm can be downloaded from here also: http://support.novell.com/techcenter/psdb/8420a0fde1d2c54070669938e083e2c9.html
Note 171356 - SAP software on Linux Essential information
Note 958253 - SUSE LINUX Enterprise Server 10: Installation notes
Hey Conrad,
what does
grep -i LD_ASSUME_KERNEL install.sh
give? I assume that the install.sh scripts is setting this variable in the script, which causes the installation to crash.
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Conrad,
argh, I thought that there is an LD_ASSUME_KERNEL setting in the install.sh for the installation. The entries you found are only for the later part, when everything is already installed.
I'm not very familiar with the NW4 testdrive, maybe someone else has a deeper knowledge of it. I'd also suggest to have a look into the install.sh file and execute the steps manually. Maybe this gives you a hint.
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.