Member Avatar for vasanth19

Has someone managed to install Oracle 11.1 on Fedora 12 ?

The following packages failed to install :

Checking for libaio-0.3.106-i386; Not found. Failed <<<<
Checking for libstdc++-4.1.1-i386; Not found. Failed <<<<
Checking for libgcc-4.1.1-i386; Not found. Failed <<<<
Checking for glibc-devel-2.5-i386; Not found. Failed <<<<
Checking for compat-libstdc++-33-3.2.3-i386; Not found. Failed <<<<

I couldn't find any of these packages in the x64_86 or i386 DVD.
i686 version of the above packages are already installed, but I still get the error while installation.

  • 2 Contributors
  • 2 Replies
  • 606 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by vasanth19

Dani AI

Generated

Short note for future readers: Oracle Database 11g Release 1 (11.1) on a 64‑bit Linux host will often require the 32‑bit compatibility RPMs as well as the 64‑bit ones — the installer checks for those 32‑bit packages on x86_64 platforms for releases prior to 11.2.0.2. This is why the OUI reports “missing” packages even on a 64‑bit system. (docs.oracle.com)

Practical troubleshooting steps that avoid guesswork:

  • Refresh yum and search which package provides the missing library name (for example, a missing lib*.so).
  • Install the 32‑bit build of the package from your enabled repositories (append the architecture: .i686 on Fedora/RHEL systems).
    Example commands:
    sudo yum clean all
yum whatprovides "*/libaio.so"       # find the package that supplies a library
yum list <packagename> --showduplicates
sudo yum install <packagename>.i686  # install the 32-bit compatibility RPM

    Yum will accept the .i686 suffix on multilib systems; if you hit “protected multilib versions” errors, that means the i686 and x86_64 variants are different versions and need to be resolved (update repos or install matching versions). (docs.redhat.com)

Notes on shortcuts and safety: was right that symlinks can sometimes trick the installer, but that is fragile and can produce runtime failures if the ABI/SONAMEs differ. Prefer installing proper compatibility RPMs and then re-running the installer. If you must bypass the prerequisite check you can run the installer with the flag to ignore system prereqs (-ignoreSysPrereqs), but only do that after verifying the actual libraries the Oracle binaries need with:

file $ORACLE_HOME/bin/oracle
ldd  $ORACLE_HOME/bin/oracle | grep "not found"

and only if every “not found” line is addressed. The installer flag is documented in OUI docs. (docs.oracle.com)

If the installer already completed (as reported), still run the ldd checks above and exercise the database under load: missing runtime libs often only show up later. Best practice is to install matching multilib RPMs from the distro or use a supported OS image (RHEL/OEL) for Oracle to avoid surprises.

Recommended Answers

All 2 Replies

Member Avatar for blud

Are the same 'version' of the packages installed? Sometimes newer packages are installed by the OS, but the oracle installer is looking for specific files in specific directories. Some people get around this with symlinks, although I don't think there is going to be a 'fix' for this until oracle supports RHEL6, I don't think it keeps up with fedora.

Member Avatar for vasanth19

Installer couldn't check the difference between i386 and i686, I ignored the error and completed the installation. Oracle works fine.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.