Oracle 9.2 on RH9 Java initialisation error
Fred J
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@neptune Disk1]$ ./runInstaller
[oracle@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?
TIA
Fred Johnson
Hans Forbrich
Discussed on this group many times. Not a cerified combination. Amongst other
things, Oracle Java vs RH Java conflicts. Also conflicts on GCC (glibc) you may
need to have gcc 2.95 coexist. Not easy to do or resolve. Use google/yahoo to
grep the archive for more discussion.
Howard J. Rogers
"Fred J" <fre...@dsl.pipex.com> wrote in message
news:3ec796a9$0$10762$cc9e...@news.dial.pipex.com...
Interesting. This specific question about Red Hat 9 has popped up at least
three times a week for the past three weeks: I guess all Linux users are as
desperate to upgrade to new releases as us Windows babies are to get our
hands on Windows 2003!!
Now, how do you want your coffee? If you talk to the Linux hard-nuts, Oracle
can be persuaded to work on RH9, provided (variously, and from memory) you
put up with the Database Creation Assistant not working, working, working
erratically, or somewhere in between. Provided also you don't intend using
Enterprise Manager. Or that you do. And provided you know Linux backwards,
and set ASSUME_KERNEL= something, nothing or something and nothing.
If like me you can competently get Oracle working on RH8, despite the
occasional linking glitches it throws up, then the replies to the RH9
questions will have indicated that, quite frankly, Oracle 9.2 doesn't work
on RH9, depending on what you mean by the word "work".
It certainly seems like far too much hassle to be good for the digestive
system.
The best I can suggest is that you flit over to www.google.com, and search
the Group archives for posts here containing the words RH9 over the past, I
would say, four weeks. A lot of them contained workarounds. A lot of them
also gave links to other forums where the issues were discussed (though the
one I looked at didn't ever seem to get around to working out a definitive
answer!).
But if you really want Oracle working properly, and quickly, with minimum
hassle, then fall back to RH8.
Regards
HJR
Dave Hau
news:3ec796a9$0$10762$cc9e...@news.dial.pipex.com...
>
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
>
>
andi
how did you managed to solve the ins_oemagent.mk linking error?
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-n...@no-spam.netscape.net> wrote in message
news:rHSxa.2660$gy3...@newssvr17.news.prodigy.com...
Dave Hau
news:ba9995$6lv$1...@reader01.singnet.com.sg...
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
Mladen Gogala
>
> 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, does that make oracle work OK on RH 9? Installation goes well and
everything works as advertised? You obviously have some internal knowledge
which I lack. Approximately a month ago I posted an article on this group
about RH9 and Oracle. I solved my problems by reloading RH 8.0. Is it
safe to load RH 9? I know it isn't supported but that has't ever stopped
me before. RH 8.0 isn't supported either.
--
Mladen Gogala
Software is like sex, it is better when it is free.
Linus Torvalds
Dave Hau
news:pan.2003.05.19....@adelphia.net...
> On Mon, 19 May 2003 09:32:07 +0000, Dave Hau wrote:
>
> >
> > 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, does that make oracle work OK on RH 9? Installation goes well and
I can't say it's risk free. But IMHO it should be no more riskier than
running it on RH 8.
Cheers,
Dave
andi
this is the message from dbsnmp.log
NMS-00001: Warning: dbsnmp unable to connect to SNMP master agent
20-MAY-2003 09:11:44: NMS-00908: Shutting down normally
what's the SNMP master agent?
TIA,
andi
--
Problems in Windows - reboot
Problems in Linux - be root
"Dave Hau" <davehau-n...@no-spam.netscape.net> wrote in message
news:rw1ya.194$0n6.30...@newssvr15.news.prodigy.com...
Dave Hau
> Hi
> this is the message from dbsnmp.log
>
> NMS-00001: Warning: dbsnmp unable to connect to SNMP master agent
> 20-MAY-2003 09:11:44: NMS-00908: Shutting down normally
>
> what's the SNMP master agent?
It's described here:
http://download-west.oracle.com/docs/cd/B10501_01/em.920/a96676/chap2.htm#1004737
Cheers,
Dave