Thursday, November 18, 2010

Starting IBM InfoSphere Information Server node agents as a non-root user

Question
Can we start the node agents (ASB and logging agents) for IBM InfoSphere Information Server as a non-root user on Linux and UNIX?

Answer
The node agents (mainly the ASB and logging agents) can be started as the DataStage administrator user.

Link to IBM: http://www-01.ibm.com/support/docview.wss?rs=14&uid=swg21415257
Version 8.5: http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/topic/com.ibm.swg.im.iis.found.admin.common.doc/topics/appsvconfig_nonrootadmin_agents.html

Failure during patch installation on IBM InfoSphere Information Server 8.1 running on Aix

Failure during patch installation on IBM InfoSphere Information Server 8.1 running on Aix

Problem

Installation of patch fails on IBM InfoSphere Information Server 8.1 running on Aix, due to the fact that the patch installer fails to restart IBM WebSphere

Symptom

Unable to install patch, as IBM WebSphere fails to start and produces a Core Dump

Cause

Trouble building LIBPATH due to the length of the environment variable

Resolving the problem

1. Create the file MetadataServer_env.sh in the <IS_HOME>/ASBServer/bin directory, with the following entries:
#!/bin/sh
unset LIBPATH
unset LDR_CNTRL
export LIBPATH LDR_CNTRL

NOTE: LDR_CNTRL is also being unset as IBM Information Server 8.1 is a 64-bit application.
LDR_CNTRL should not be set for 64-bit programs, as this will limit the amount of memory a 64-bit program can use. This variable is intended primarily for 32-bit programs.

2. Set permission on the file:

chmod 775 MetadataServer_env.sh

If the file is already there then ensure that the above entries as per Point 1 are added. This file will then be sourced by the patch installer when it restarts IBM WebSphere during the patch installation.
 
Link to IBM:  http://www-01.ibm.com/support/docview.wss?uid=swg21396886
 

Monday, November 1, 2010

DB2 9.5 fails to install with Segmentation fault

Recently i tried to install DB2 9.5 on CentOS. However i hit problems during the installation (which exits by itself) with the following java exception.

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 "".

Further investigation shows that  installation succeed but fails during instance creation.

Resolution: The problem lies with the installation is unable to resolve the hostname. You need to add the hostname in the /etc/hosts file. After that the installation completes successfully.