Re: Oracle 9.2 on RH9 Java initialisation error

"andi" <a_at_a.com> wrote in message
news:ba9995$6lv$1_at_reader01.singnet.com.sg...
> Hi Dave.
> how did you managed to solve the ins_oemagent.mk linking error?

The linking error is due to a symbol __ctype_b being replaced by a function call *__ctype_b_loc() in glibc-2.3.2. Somewhere in oemagent, the code directly accesses __ctype_b, hence the error. This issue has been filed as Bug 86465in Redhat's Bugzilla where you can read more about it:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=86465

As mentioned in the bug report, the issue has been fixed in glibc-2.3.2-4.80.6 by re-adding the symbol __ctype_b to libc.a. (The original version of glibc in RH9 is 2.3.2-27.9)

So, to fix the linking errors for oemagent, we need to replace libc with the new version. Get the rpm package for glibc-2.3.2-4.80.6 here:

ftp://updates.redhat.com/8.0/en/os/i686/glibc-2.3.2-4.80.6.i686.rpm

Then do the following:

rpm2cpio glibc-2.3.2-4.80.6.i686.rpm | cpio -idmv cp /lib/libc-2.3.2.so /lib/libc-2.3.2.so.ORIG cp/lib/libc.so.6 /lib/libc.so.6.ORIG
cp ./lib/libc-2.3.2.so /lib/
cp ./lib/libc.so.6 /lib/

Then you can relink oemagent by doing this:

$ORACLE_HOME/bin/relink oemagent

or this:

cd $ORACLE_HOME/network/lib
make -f ins_oemagent.mk install

This time you shouldn't get any linking error.

However, the particular error you encountered "agent shutdown failed" may or may not be related to this issue. If it persists, have a look in the log files under:

$ORACLE_HOME/network/log

and see if there's any clue of what's wrong. If not, turn on tracing for the intelligent agent and debug.

Cheers,
Dave

>
> I tried a workaround from otn linux forum, but the agentctl stop still
gave
> me the message "Agent shutdown failed." (i believe it should be "Agent
> Shutdown") but I checked that the dbsnmp process was not in the memory
> anymore.
>
> Any tips would be very much appreciated.
>
> TIA,
> andi
>
>
> --
> Problems in Windows - reboot
> Problems in Linux - be root
> "Dave Hau" <davehau-no-spam-123_at_no-spam.netscape.net> wrote in message
> news:rHSxa.2660$gy3.330_at_newssvr17.news.prodigy.com...
> > "Fred J" <fred.j_at_dsl.pipex.com> wrote in message
> > news:3ec796a9$0$10762$cc9e4d1f_at_news.dial.pipex.com...
> > >
> > > I am running RH9 and trying to load Oracle server 9.2. I have
followed
> > the
> > > installation documentation provied by Oracle but when I try to start
> > > runInstaller I get the error:
> > >
> > > [oracle_at_neptune Disk1]$ ./runInstaller
> > > [oracle_at_neptune Disk1]$ Initializing Java Virtual Machine from
> > >
> >
>

../stage/Components/oracle.swd.jre/1.1.8/1/DataFiles/Expanded/linux/bin/jre.
> > > Please wait...
> > >
> >
>

/home/oracle/Disk1/stage/Components/oracle.swd.jre/1.1.8/1/DataFiles/Expande
> > > d/linux/lib/linux/native_threads/libzip.so: symbol errno, version
> > GLIBC_2.0
> > > not defined in file libc.so.6 with link time reference (libzip.so)
> > > Unable to initialize threads: cannot find class java/lang/Thread
> > > Could not create Java VM
> > >
> > > Anyone seen this before and got past it?
> >
> > You can get around this by setting LD_ASSUME_KERNEL=2.4.1 in your
> > environment.
> >
> > This happens because even though the installer is a java app, it calls
> > native libraries via JNI to perform tasks like changing file permission,
> > copying files etc. The native libraries are compiled against the glibc
in
> > RHAS and are not compatible with the glibc 2.3.2 in RH9.
> >
> > Cheers,
> > Dave
> >
> >
> >
> > >
> > > TIA
> > >
> > >
> > > Fred Johnson
> > >
> > >
> >
> >
>
>
Received on Mon May 19 2003 - 04:32:07 CDT