|
Problem IC68689
|
Status: Closed |
AFTER MACHINE REBOOT, AN INSTANCE STARTED AUTOMATICALLY MAY NOT HAVE THE CORRECT ENVIRONMENT VARIABLES SET UP |
| 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.
For example a typical DB2 instance may have the following:
ps -ef | grep db2 | grep db2sysc | grep -v grep
v91ee 7780 7754 1 11:27 ? 00:00:00 db2sysc 0
ps eww 7780
PID TTY STAT TIME COMMAND
7780 ? S 0:00 db2sysc
0 HOME=/ PWD=/
DB2INSTANCE=v91ee DB2INSTDEF=v91ee DB2LPORT=0 DB2NODE=0
DSMI_LOG=/home/v91ee/tsm/dsmerror.log
CLASSPATH=/home/v91ee/sqllib/java/db2java.zip:/home/v91ee/sqllib
/java/db2jcc.jar:/home/v91ee/sqllib/java/sqlj.zip:/home/v91ee/sq
llib/function:/home/v91ee/sqllib/java/db2jcc_license_cu.jar:.
DB2SYSC_EXEC_OWNER=DB2
PATH=/home/v91ee/sqllib/bin:/home/v91ee/sqllib/adm:/bin:/usr/bin
:
LD_LIBRARY_PATH=/home/v91ee/sqllib/lib32:/home/v91ee/sqllib/func
tion:/home/v91ee/sqllib/java/jdk32/jre/bin:/home/v91ee/sqllib/ja
va/
However, an instance started automatically may only have the
following:
ps -ef | grep db2 | grep db2sysc | grep -v grep
v91ee 2774 2768 0 11:23 ? 00:00:00 db2sysc 0
ps eww 2774
PID TTY STAT TIME COMMAND
2774 ? S 0:00 db2sysc
0 HOME=/ PWD=/
DB2INSTANCE=v91ee DB2INSTDEF=v91ee DB2LPORT=0 DB2NODE=0
DB2SYSC_EXEC_OWNER=DB2
PATH=/home/v91ee/sqllib/bin:/home/v91ee/sqllib/adm:/bin:/usr/bin
:
LD_LIBRARY_PATH=/home/v91ee/sqllib/lib32:/home/v91ee/sqllib/func
tion:/home/v91ee/sqllib/java/jdk32/jre/bin:/home/v91ee/sqllib/ja
va/jdk32/jre/bin/classic:/home/v91ee/sqllib/java/jdk32/jre/bin/j
9vm
This apar fixes this problem to ensure that the correct
environment variables are set up even after a machine reboot. |
| Problem Summary: |
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.
For example a typical DB2 instance may have the following:
ps -ef | grep db2 | grep db2sysc | grep -v grep
v91ee 7780 7754 1 11:27 ? 00:00:00 db2sysc 0
ps eww 7780
PID TTY STAT TIME COMMAND
7780 ? S 0:00 db2sysc
0 HOME=/ PWD=/
DB2INSTANCE=v91ee DB2INSTDEF=v91ee DB2LPORT=0 DB2NODE=0
DSMI_LOG=/home/v91ee/tsm/dsmerror.log
CLASSPATH=/home/v91ee/sqllib/java/db2java.zip:/home/v91ee/sqllib
/java/db2jcc.jar:/home/v91ee/sqllib/java/sqlj.zip:/home/v91ee/sq
llib/function:/home/v91ee/sqllib/java/db2jcc_license_cu.jar:.
DB2SYSC_EXEC_OWNER=DB2
PATH=/home/v91ee/sqllib/bin:/home/v91ee/sqllib/adm:/bin:/usr/bin
:
LD_LIBRARY_PATH=/home/v91ee/sqllib/lib32:/home/v91ee/sqllib/func
tion:/home/v91ee/sqllib/java/jdk32/jre/bin:/home/v91ee/sqllib/ja
va/
However, an instance started automatically may only have the
following:
ps -ef | grep db2 | grep db2sysc | grep -v grep
v91ee 2774 2768 0 11:23 ? 00:00:00 db2sysc 0
ps eww 2774
PID TTY STAT TIME COMMAND
2774 ? S 0:00 db2sysc
0 HOME=/ PWD=/
DB2INSTANCE=v91ee DB2INSTDEF=v91ee DB2LPORT=0 DB2NODE=0
DB2SYSC_EXEC_OWNER=DB2
PATH=/home/v91ee/sqllib/bin:/home/v91ee/sqllib/adm:/bin:/usr/bin
:
LD_LIBRARY_PATH=/home/v91ee/sqllib/lib32:/home/v91ee/sqllib/func
tion:/home/v91ee/sqllib/java/jdk32/jre/bin:/home/v91ee/sqllib/ja
va/jdk32/jre/bin/classic:/home/v91ee/sqllib/java/jdk32/jre/bin/j
9vm
This apar fixes this problem to ensure that the correct
environment variables are set up even after a machine reboot. |
| Local Fix: |
Do not start the instance automatically after rebooting. Or stop
the instance after initial start and restart it as the instance
owner. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
|
| Solution |
First fixed in db2 v9.7 fp3. |
| Workaround |
Do not start the instance automatically after rebooting. Or stop
the instance after initial start and restart it as the instance
owner. |
| BUG-Tracking |
forerunner : IC68496
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.05.2010
24.09.2010
24.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
