I vaguely remember running into something like this, and I worked around
it by symlinking /usr/lib/lib<whatever> to /usr/lib64/lib<whatever> and
re-running ldconfig.

Might be worth a shot....

-Lloyd


On 09/09/2011 10:50 AM, Zoltan Forray/AC/VCU wrote:

We are building a new server and decided to go with RedHat 6.  DB2
Requirements page says RHEL 6 is valid for DB2 9.7 with Fix Pack 4.

When we try to run the installation for base 6.2.1 (couldn't find a 6.2.3
in Passport), it chokes saying we are missing  Linux compat-libstdc++
(libstdc++so.6)

But when we check, these libraries are installed at the latest levels.

So I was wondering what DB2 fixpack level does the 6.2.1 base come with?

Comment from my OS guy:

------------------------------------------------------
[root@galaxy ~]# rpm -ql libstdc++
/usr/lib64/libstdc++.so.6
/usr/lib64/libstdc++.so.6.0.13

The library file is there.

[root@galaxy ~]# yum list compat-libstdc++-33
Loaded plugins: product-id, refresh-packagekit, rhnplugin,
subscription-manager
Updating Red Hat repositories.
Installed Packages
compat-libstdc++-33.x86_64                                  3.2.3-69.el6
  @anaconda-RedHatEnterpriseLinux-201105101844.x86_64/6.1
Available Packages
compat-libstdc++-33.i686                                    3.2.3-69.el6
                              rhel-x86_64-server-6

The package is installed at the latest available level.

[root@galaxy ~]# rpm -ql compat-libstdc++-33-3.2.3-69.el6.x86_64
/usr/lib64/libstdc++.so.5
/usr/lib64/libstdc++.so.5.0.7

But the package they asked for provides the wrong version of the library.
-------------------------------------------------------

Our RHEL level: Red Hat Enterprise Linux Server release 6.1 (Santiago)
2.6.32-131.2.1.el6.x86_64 #1 SMP

Are we too far ahead, OS wise, for the installer for this to work? Any
other suggestions for figuring out what it doesn't like?


Zoltan Forray
TSM Software&  Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html