Problem when Iam installing ias on Red Hat As 3.0

Question

Hi,
I am trying to install it, I run the OUI and then that mentions that there is no problem with the prerequisites.
However, after only display wait and never show a window of the OUI.
What can I do?

Answer 1

Not sure what versions you are installing and installing on, but here is a Metalink note with a similar issue. It's kind of old and for Oracle 8i, but matches your stated issue with the OUI, so it might be worth checking out the patches it mentions:
Subject:      8.1.7.0.1 Linux - RedHat 7.1 Certification Note
     Doc ID:      Note:163135.1      Type:      BULLETIN
     Last Revision Date:      19-DEC-2002      Status:      PUBLISHED
8.1.7.0.1 Linux - RedHat 7.1 Certification Note
I. New Installations
PLEASE NOTE:
The following recommendations should be used in conjunction with this Note:
Note 114141.1 LINUX Quick Start Guide - 8.1.6 and 8.1.7 RDBMS Installation
Oracle Installation of 8.1.6 and 8.1.7 does not work correctly on Redhat 7.1
(glibc 2.2 and above) There are two known issues:
1. The initial problem is that the Oracle Universal Installer does not start
(although runInstaller has started and the jre is running the OUI never actually
starts and displays the OUI window)
2. The next problem will be that the relink phase of the installation fails due
to Bug 1467074. If the fix for this bug is not applied, none of the Oracle
executables will run and you will not be able to create a database during the
installation.
Solution to Issue 1:
To solve the initial problem of the OUI not starting you need to install the
following patches available via the Redhat 7.1 CDs or from www.redhat.com
compat-glibc-6.2-2.1.3.2.i386.rpm (CD1)
compat-egcs-6.2-1.1.2.14.i386.rpm (CD2)
compat-libs-6.2-3.i386.rpm (CD2)
The following commands can be run to check if the patches have been applied
(the expected output is listed below the command) :
# rpm -q compat-egcs
compat-egcs-6.2-1.1.2.14
# rpm -q compat-glibc
compat-glibc-6.2-2.1.3.2
# rpm -q compat-libs
In a shell window, set the environment variable LD_ASSUME_KERNEL as follows :
$ export LD_ASSUME_KERNEL=2.2.5
In the same shell window as used in the previous step, run the system glibc
environment script as follows :
$ . /usr/i386-glibc21-linux/bin/i386-glibc21-linux-env.sh
The OUI should now start correctly.
(If the OUI still does not start, you will need to apply the patch for Bug 2062423.
Please refer to the README.txt associated with the patch for more information.)
Solution to Issue 2:
At the first relinking error,
Apply the glibc patch for Bug 1467074. Follow the instructions in the bug readme.txt to apply the patch.
Apply the interMedia Text patch - patch for Bug 2062512. Follow the instructions in the bug readme.txt
to apply the patch.
Click on "Retry" on the installer (to re-try the relinking).
II. O/S Upgrade customers/installations :
This is for customers who already have 8.1.7.0.1 installed on say RedHat 7.0 and
upgrade their O/S to RedHat 7.1. When the O/S upgrade completes, if the
OUI/Assistants no longer work:
o Apply the JRE/OUI patch - patch for Bug 2062423 (follow the instructions in
the bug readme to apply the patch) on top of the 8.1.7.0.1 installation. The
patch would upgrade the JRE of the installation.
o Apply the Context patch - patch for Bug 2062512 (follow the instructions in
the bug readme to apply the patch).
o The OUI/Assistants should work fine now.
III. Patchset application
If the OUI cannot be launched from the Installation CD or the $ORACLE_HOME/bin directory:
o Apply the JRE/OUI patch - patch for Bug 2062423 (follow the instructions in
the bug readme to apply the patch) on top of the 8.1.7.0.1 installation. The
patch would upgrade the JRE of the installation. The installer from the
install-home can then be used to apply any patchsets.
o The glibc patch has to be applied during every patchset application as the
patchset may overwrite the relinking makefiles.
IV. Instructions to download the patches
1. Log in to MetaLink and in the menu, click on the button "Patches".
2. On the "Patch Download" screen, enter the "Patch Number" (2062423, 1467074 or 2062512)
and leave all other fields with the default values, and click on the
"Submit" button.
3. Click on the "Download" button.
4. Install the patch by following the instructions in the readme.txt file.
5. Repeat steps 2 through 4 for the second patch.