Red Hat Bugzilla – Bug 102328
LTC3920-[BETA] DB2 v8.1 FP2 doesn't install on Beta 1 RHEL 3
Last modified: 2007-11-30 17:06:57 EST
The following has be reported by IBM LTC:
[BETA] DB2 v8.1 FP2 doesn't install on Beta 1 RHEL 3
Please fill in each of the sections below.
Hardware Environment: IA64 system. 4 cpu
Software Environment: Red Hat Enterprise Linux 3 Beta 1
Steps to Reproduce:
1. Install RHEL 3, Beta 1, install all errata listed from RHN
2. Take DB2 install image and attempt to install on RHEL 3, Beta 1
Actual Results: Message generated by the install program:
[root@panda99 download]# ./ese/db2setup
error: /download/ese/db2/linux64/install/../bin/disp_msg: symbol _dl_loaded,
version GLIBC_2.2 not defined in file ld-linux-ia64.so.2 with link time
Expected Results: JAVA gui starts up to begin install.
This symbol existed on RH AS 2.1:
[root@it2 lib]# nm -o ld-2.2.4.so | grep dl_loaded
ld-2.2.4.so:0000000000042680 S _dl_loaded
But not on RH EL 3:
[root@panda99 lib]# nm -o ld-linux-ia64.so.2 | grep dl_loaded
Please advise. Should this symbol be here? We have not explicitly added it in
our build env. as far as we can tell.
If you need a copy of DB2, please let me know.. Otherwise the DB2 for Linux
IA64 can be downloaded from the www.ibm.com/db2 website.
Glen/Greg - probably the quickest way is to ask Red Hat about this dl_loaded
symbol which does not seem to exist in RHEL3 beta1. Thanks.
_dl_loaded used to be ld.so's private symbol, no application should ever use it
(and is no longer present in glibc 2.3+ and even if it would, it would be
marked as GLIBC_PRIVATE).
If applications need to look at what libraries are loaded, glibc provides
------ Additional Comments From email@example.com 2003-14-08 10:10 -------
I can't seem to add anything to the Red Hat bugzilla bug system. (I have an
id, just don't have permission).
I was able to track down where the symbol came from. It looks like DB2 didn't
add it in, but rather the Intel compiler did. I will pursue this with them.
------ Additional Comments From firstname.lastname@example.org 2003-18-08 13:21 -------
Chatted with Yvonne. They were able to track down where the symbol came from.
It looks like DB2 didn't add it in, but rather the Intel compiler did.
This is be followed-upon with Intel