Tuxedo Install Error



I have been attempting to install Tuxedo on Oracle Enterprise Linux 5.  The installation presented several problems, and so, I thought it might be helpful to blog the fixes.

Both errors appear to be part of the InstallAnywhere installation system.  So, the fixes that I found were not specifically for Tuxedo or even PeopleSoft/Bea.

The first error output looked like this:

awk: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/ls: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/tmp/install.dir.5362/Linux/resource/jre/bin/java:
error while loading shared libraries: libpthread.so.0: cannot open
shared object file: No such file or directory
Tuxedo 9.1 base installation complete

I found the fix here.  Basically, you comment out the part of the script that sets the LD_ASSUME_KERNEL variable.  You can’t just use any text editor or even vi because the file actually contains the binary installation files zipped up in it.  Instead, this sed command seems to work:

cd linux/sles9/base/
cp tuxedo91_32_SLES_9_x86.bin ../Install.bak
chmod +w tuxedo91_32_SLES_9_x86.bin
cat ../Install.bak | sed "s/export LD_ASSUME_KERNEL/#xport LD_ASSUME_KERNEL/" > tuxedo91_32_SLES_9_x86.bin

That fixed part of the problem.  But, I still received this error:

awk: cmd. line:6: warning: escape sequence `\.' treated as plain `.'
=======================================================

Installer User Interface Mode Not Supported

Unable to load and to prepare the installer in console or silent mode.

=======================================================

The awk… message looks like it is a problem, but that can be ignored.  A couple of searches showed that other people’s successful installs had this error message.  As best I can tell, the problem lies in the packaged version of Java.

To fix the problem, I first had to install Java.  GCJ comes installed by default.  I installed Sun’s Java 1.5 by downloading and installing jdk-1_5_0_16-linux-i586-rpm.bin.

Then, I found an article that explains how to override the JVM used by the installer.  To make this work, you need to edit (with either the vi command or the gedit command) the install.sh.  Change the line from (line #259):

        sh $INSTALL_BINARY -f $SILENT_INSTALL_FILE > $INSTALLER_OUTPUT;

to:

        sh $INSTALL_BINARY LAX_VM /usr/java/jdk1.5.0_16/bin/java -f $SILENT_INSTALL_FILE > $INSTALLER_OUTPUT;

After that fix, tuxedo finally installed for me!

Resources


Share

4 Comments

  1. Kel Mitchell says:

    Thank you thank you thank you! I have been beating my head against the wall on these issue with OEL. I thought I was going to pull what little hair i had left out. Because of your blog, I shall remain somewhat “unbald” now :)

  2. Jun Chee says:

    Thanks for the help.

    The 1st workaround resolved the 1st problem for me. But I’m still having the 2nd problem after installing Sun’s Java 1.5 and adding “LAX_VM /usr/java/jdk1.5.0_16/bin/java” for line #259 in install.sh.

    Any additional help will be greatly appreciated!

  3. Jun Chee says:

    I found out why. I’m doing Linux 64, which is not supported for Tuxedo 9.1.

  4. Sandeep says:

    Thankyou very much,
    I commentted out the part of the script that sets the LD_ASSUME_KERNEL variable, I my problem resolved.

Leave a comment