Error referencing DB2SET in nanny.trace during start
 Technote (FAQ)
 
Problem
WebSphere® Application Server V4.0 fails to start on Unix® after installation configured to run with DB2®. The only log generated is the nanny.trace. The following errors appears in nanny.trace:

... Nanny E About to try to get the umask for the AIX platform.
... Nanny E Found umask string of "DB2SET processing complete, rc = -4400, SQLCODE = 0"
... Nanny W exception caught in Initial adminserver startup: java.lang.NumberFormatException: DB2SET processing complete, rc = -4400, SQLCODE = 0
 
Cause
DB2SET is a DB2 command that updates the database server configuration. It is not appropriate to include this command in any startup scripts.
db2set DB2ENVLIST=EXTSHM
 
Solution
When configuring DB2 to use Extended Shared Memory,
  1. Run "db2set DB2ENVLIST=EXTSHM" once from a command shell, after sourcing db2profile:
    1. . ./db2profile
    2. db2set DB2ENVLIST=EXTSHM
  2. Update db2profile to include the following settings:
    EXTSHM=ON
    export EXTSHM
  3. Configure the user account that starts WebSphere to source db2profile before starting WebSphere.

For example, in the root user account .profile:
. /usr/db2inst1/sqllib/db2profile

For more details on configuring DB2 to use Extended Shared Memory, follow the instructions in the WebSphere Application Server V4.0 Information Center:

http://www.ibm.com/developerworks/websphere/WASInfoCenter/infocenter/

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Data & Information Management DB2 Universal Database
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Install
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 1156869
IBM Group: Software Group
Modified date: Jan 5, 2004