|
Problem IC73564
|
Status: Closed |
DB2 ENVIRONMENT VARIABLES MAY NOT SET UP CORRECTLY IF AN INSTANCE IS STARTED AUTOMATICALLY. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
After performing a reboot of the machine on which DB2 resides,
if there are any instances configured to start automatically
using the db2iauto command, then they may not have the correct
environment variables set up.
There was a V97FP3 APAR to address this (IC68689). Issue
still exists after applying this APAR.
Steps to reproduce:
1) set user profile like below:
DSMI_CONFIG=/usr/local/etc/db2/dsm.opt.dsmicfg
DSMI_DIR=/opt/tivoli/tsm/client/api/bin64
DSMI_LOG=/proj/db2/home/dsmicfg/tsm HOSTNAME=serverA
2) reboot system
3) db2sysc environment after rebooting machine. However, an
instance started automatically may only have the following:
db2inst1@serverA:~> ps eww 8283
PID TTY STAT TIME COMMAND
8283 ? Sl 0:01 db2sysc 0
HOME=/ PWD=/ DB2INSTANCE=db2inst1 DB2INSTDEF=db2inst1 DB2LPORT=0
DB2NODE=0 DB2SYSC_EXEC_OWNER=DB2
PATH=/home/db2inst1/sqllib/bin:/home/db2inst1/sqllib/adm:/bin:/u
sr/bin:
LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib32:/home/db2inst1/sqlli
b/function:/home/db2inst1/sqllib/java/jdk32/jre/bin:/home/db2ins
t1/sqllib/java/jdk32/jre/bin/classic:/home/db2inst1/sqllib/java/
jdk32/jre/bin/j9vm
From above, db2 didn't load 3 TSM variables such as DSMI_CONFIG,
DSMI_DIR, and DSMI_LOG.
4) stop/start instance
db2inst1@serverA:~> ps eww 9061
PID TTY STAT TIME COMMAND
9061 pts/1 Sl 0:01 db2sysc 0
HOME=/home/db2inst1 PWD=/home/db2inst1 DB2INSTANCE=db2inst1
DB2INSTDEF=db2inst1 DB2LPORT=0 DB2NODE=0
DSMI_CONFIG=/usr/local/etc/db2/dsm.opt.dsmicfg
DSMI_DIR=/opt/tivoli/tsm/client/api/bin64
DSMI_LOG=/proj/db2/home/dsmicfg/tsm HOSTNAME=serverA
LANG=en_US.UTF-8 USER=db2inst1
CLASSPATH=/home/db2inst1/sqllib/java/db2java.zip:/home/db2inst1/
sqllib/java/db2jcc.jar:/home/db2inst1/sqllib/java/sqlj.zip:/home
/db2inst1/sqllib/function:/home/db2inst1/sqllib/java/db2jcc_lice
nse_cu.jar:.
DB2SYSC_EXEC_OWNER=DB2
PATH=/home/db2inst1/sqllib/bin:/home/db2inst1/sqllib/adm:/bin:/u
sr/bin:
LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib32:/home/db2inst1/sqlli
b/function:/home/db2inst1/sqllib/java/jdk32/jre/bin:/home/db2ins
t1/sqllib/java/jdk32/jre/bin/classic:/home/db2inst1/sqllib/java/
jdk32/jre/bin/j9vm
Now the 3 TSM variables such as DSMI_CONFIG, DSMI_DIR, and
DSMI_LOG are loaded on the environment. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* UNIX *
****************************************************************
* PROBLEM DESCRIPTION: *
* After performing a reboot of the machine on which DB2 *
* resides, *
* if there are any instances configured to start automatically *
* *
* using the db2iauto command, then they may not have the *
* correct *
* environment variables set up. *
* *
* *
* *
* There was a V97FP3 APAR to address this (IC68689). Issue *
* *
* still exists after applying this APAR. *
* *
* *
* *
* Steps to reproduce: *
* *
* *
* *
* 1) set user profile like below: *
* *
* DSMI_CONFIG=/usr/local/etc/db2/dsm.opt.dsmicfg *
* *
* *
* *
* DSMI_DIR=/opt/tivoli/tsm/client/api/bin64 *
* *
* DSMI_LOG=/proj/db2/home/dsmicfg/tsm HOSTNAME=serverA *
* *
* *
* *
* *
* *
* 2) reboot system *
* *
* *
* *
* 3) db2sysc environment after rebooting machine. However, an *
* *
* instance started automatically may only have the following: *
* *
* db2inst1@serverA:~> ps eww 8283 *
* *
* PID TTY STAT TIME COMMAND *
* *
* 8283 ? Sl 0:01 db2sysc 0 *
* *
* *
* *
* *
* *
* HOME=/ PWD=/ DB2INSTANCE=db2inst1 DB2INSTDEF=db2inst1 *
* DB2LPORT=0 *
* DB2NODE=0 DB2SYSC_EXEC_OWNER=DB2 *
* *
* PATH=/home/db2inst1/sqllib/bin:/home/db2inst1/sqllib/adm:/bi *
* n:/u *
* sr/bin: *
* *
* LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib32:/home/db2inst1/s *
* qlli *
* b/function:/home/db2inst1/sqllib/java/jdk32/jre/bin:/home/db *
* 2ins *
* t1/sqllib/java/jdk32/jre/bin/classic:/home/db2inst1/sqllib/j *
* ava/ *
* jdk32/jre/bin/j9vm *
* *
* *
* *
* From above, db2 didn't load 3 TSM variables such as *
* DSMI_CONFIG, *
* DSMI_DIR, and DSMI_LOG. *
* *
* *
* *
* 4) stop/start instance *
* *
* db2inst1@serverA:~> ps eww 9061 *
* *
* PID TTY STAT TIME COMMAND *
* *
* 9061 pts/1 Sl 0:01 db2sysc 0 *
* *
* *
* *
* *
* *
* HOME=/home/db2inst1 PWD=/home/db2inst1 DB2INSTANCE=db2inst1 *
* *
* DB2INSTDEF=db2inst1 DB2LPORT=0 DB2NODE=0 *
* *
* DSMI_CONFIG=/usr/local/etc/db2/dsm.opt.dsmicfg *
* *
* *
* *
* DSMI_DIR=/opt/tivoli/tsm/client/api/bin64 *
* *
* DSMI_LOG=/proj/db2/home/dsmicfg/tsm HOSTNAME=serverA *
* *
* *
* *
* LANG=en_US.UTF-8 USER=db2inst1 *
* *
* CLASSPATH=/home/db2inst1/sqllib/java/db2java.zip:/home/db2in *
* st1/ *
* sqllib/java/db2jcc.jar:/home/db2inst1/sqllib/java/sqlj.zip:/ *
* home *
* /db2inst1/sqllib/function:/home/db2inst1/sqllib/java/db2jcc_ *
* lice *
* nse_cu.jar:. *
* *
* DB2SYSC_EXEC_OWNER=DB2 *
* *
* PATH=/home/db2inst1/sqllib/bin:/home/db2inst1/sqllib/adm:/bi *
* n:/u *
* sr/bin: *
* *
* LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib32:/home/db2inst1/s *
* qlli *
* b/function:/home/db2inst1/sqllib/java/jdk32/jre/bin:/home/db *
* 2ins *
* t1/sqllib/java/jdk32/jre/bin/classic:/home/db2inst1/sqllib/j *
* ava/ *
* jdk32/jre/bin/j9vm *
* *
* *
* *
* Now the 3 TSM variables such as DSMI_CONFIG, DSMI_DIR, and *
* *
* DSMI_LOG are loaded on the environment. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 5 *
**************************************************************** |
| Local Fix: |
Stop/start instance manually |
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Version 9.7 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.12.2010
21.12.2011
21.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
