DB2 9.5 Install fails on Linux Centos x86

DB2 9.5 Install fails on Linux Centos x86_64

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

News - 22 Mar 2008 13:44 GMT

with the following java exception. any idea ?

NULL
------------------------------------------------------------------------
0SECTION TITLE subcomponent dump routine
NULL ===============================
1TISIGINFO Dump Event "gpf" (00002000) received
1TIDATETIME Date: 2008/03/22 at 12:34:40
1TIFILENAME Javacore filename: /tmp/javacore.
20080322.123439.5049.txt
NULL
------------------------------------------------------------------------
0SECTION GPINFO subcomponent dump routine
NULL ================================
2XHOSLEVEL OS Level : Linux 2.6.18-53.1.14.el5
2XHCPUS Processors -
3XHCPUARCH Architecture : amd64
3XHNUMCPUS How Many : 2
NULL
1XHEXCPCODE J9Generic_Signal_Number: 0000000000000004
1XHEXCPCODE Signal_Number: 000000000000000B
1XHEXCPCODE Error_Value: 0000000000000000
1XHEXCPCODE Signal_Code: 0000000000000001
1XHEXCPCODE Handler1: 00002AAAAAF2AFF0
1XHEXCPCODE Handler2: 00002AAAAB17DE70
1XHEXCPCODE InaccessibleAddress: 0000000000000018
NULL
1XHEXCPMODULE Module: ./libdb2ure.so
1XHEXCPMODULE Module_base_address: 00002AAAB9C1C000
1XHEXCPMODULE Symbol: _ZN12InstallTCPIP13iIsPortOpenedEi
1XHEXCPMODULE Symbol_address: 00002AAAB9D37FA6

**db2setup.err******************

/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:60: Engine "clearlooks" is
unsupported, ignoring
Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b
Error_Value=00000000 Signal_Code=00000001
Handler1=00002AAAAAF2AFF0 Handler2=00002AAAAB17DE70
InaccessibleAddress=0000000000000018
RDI=0000000003510D90 RSI=0000003EE191A2C6 RAX=0000000000000000
RBX=000000000484E940
RCX=0000000000000000 RDX=0000000000000001 R8=0000000000000000
R9=FF2F626F6F626763
R10=0000000000000000 R11=0000000000000000 R12=000000000000003F
R13=000000000000EA60
R14=00000000404AD648 R15=000000000484E940
RIP=00002AAAB9D38022 GS=0004000000000000 FS=0000000400000000
RSP=00000000404AAD30
EFlags=0000000000010202 CS=0000000000000033 RBP=0000000000000001
ERR=0000000000000004
TRAPNO=000000000000000E OLDMASK=0000000000000000 CR2=0000000000000018
xmm0 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm1 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm2 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm3 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm4 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm5 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm6 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm7 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm8 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm10 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm11 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm12 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm13 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=./libdb2ure.so
Module_base_address=00002AAAB9C1C000
Symbol=_ZN12InstallTCPIP13iIsPortOpenedEi
Symbol_address=00002AAAB9D37FA6
Target=2_30_20070420_12448_LHdSMr (Linux 2.6.18-53.1.14.el5)
CPU=amd64 (2 logical CPUs) (0x7da88000 RAM)
JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.
JVMDUMP007I JVM Requesting System Dump using '/tmp/db2.tmp.3343/db2/
linuxamd64/install/core.20080322.123439.5049.dmp'
JVMDUMP010I System Dump written to /tmp/db2.tmp.3343/db2/linuxamd64/
install/core.20080322.123439.5049.dmp
JVMDUMP007I JVM Requesting Snap Dump using '/tmp/db2.tmp.3343/db2/
linuxamd64/install/Snap0002.20080322.123439.5049.trc'
JVMDUMP010I Snap Dump written to /tmp/db2.tmp.3343/db2/linuxamd64/
install/Snap0002.20080322.123439.5049.trc
JVMDUMP007I JVM Requesting Java Dump using '/tmp/javacore.
20080322.123439.5049.txt'
JVMDUMP010I Java Dump written to /tmp/javacore.
20080322.123439.5049.txt
JVMDUMP013I Processed Dump Event "gpf", detail "".

Reply to this Message

Darin McBride - 24 Mar 2008 04:50 GMT

> with the following java exception. any idea ?

Unfortunately, CentOS is not officially supported by IBM, so you're kind of
stuck.

The best solution is to reproduce your problem using a supported-by-IBM
distribution, and then open a PMR. However, for some reason, I suspect
that'll be difficult, even if you do grab RHEL to test with.

If you can take a trace of the install (add "-t /tmp/db2setup.trc" to the
command line) and send me the trace (/tmp/db2seutp.trc*), I might be able
to give you some help.

Reply to this Message

News - 26 Mar 2008 00:41 GMT

On 24 mar, 04:50, Darin McBride <dmcbr...@naboo.to.org.no.spam.for.me>
wrote:

> > with the following java exception. any idea ?
>
> Unfortunately, CentOS is not officially supported by IBM, so you're kind of
> stuck.

RedHat 5 is supported and CentOS is announced 100% compatible

Reply to this Message

Darin McBride - 26 Mar 2008 06:06 GMT

> On 24 mar, 04:50, Darin McBride <dmcbr...@naboo.to.org.no.spam.for.me>
> wrote:
[quoted text clipped - 4 lines]
>
> RedHat 5 is supported and CentOS is announced 100% compatible

Somehow I doubt that'll get IBM to accept the problem report ;-) Now, if
you want to get the CentOS guys to give you support ...

Seriously, CentOS is making the claim of compatibility. IBM has not
verified that claim (at least not that they've advertised). I suspect it
may be an uphill battle to get IBM to verify the claim and add CentOS to
their list of supported distributions. I further suspect that RH may
encourage IBM not to do so, if they haven't already through contracts.

So, if you want to be able to open a PMR, you'll likely have to reproduce
your problem on a supported distribution (e.g., RHEL5), which I suspect
will be hard to do (not because of the difference between CentOS and RHEL,
but just because it'll be a differnet machine).

Otherwise, you could take a trace, and if that doesn't help, send me the
trace and I might be able to take a look (but no guarantees on speediness).

Reply to this Message