Troubleshooting
Problem
Symptom
1. If you are doing a SSH to the server and running the install.sh script then you need to leave that console session running (in the foreground) until the install completes. so you to need to keep "up" the console session where you are running the install.sh and not trying to run it in the background.
2. The APM table installation script in DB2 will modify the TMOUT variable but in some environment it may be set to be "read-only" so the install will hangs, so please uncomment the OS variable TMOUT before installing APM.
The TMOUT environment variable controls how long an inactive terminal window will remain present. If it were set to, say, 600, then inactive windows would close after 600 seconds (10 minutes) -- the window would close itself. A value of zero disables auto-close, which most people prefer. Commenting out the line in /etc/sysconfig/msec has no effect on the system, since the environment variable is already set to zero and made read-only.
more detail about TMOUT variable
https://www.itworld.com/article/2820677/hardware/unix-tip--killing-idle-logins.html
Cause
Environment
Diagnosing The Problem
Resolving The Problem
[root@apmrhel72 ~]# readonly
declare -r BASHOPTS="checkwinsize:cmdhist:expand_aliases:extglob:extquote:force_fignore:histappend:interactive_comments:login_shell:progcomp:promptvars:sourcepath"
declare -ir BASHPID
declare -r BASH_COMPLETION_COMPAT_DIR="/etc/bash_completion.d"
declare -ar BASH_VERSINFO='([0]="4" [1]="2" [2]="46" [3]="2" [4]="release" [5]="x86_64-redhat-linux-gnu")'
declare -ir EUID="0"
declare -ir PPID="26321"
declare -r SHELLOPTS="braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor"
declare -r TMOUT="600"
declare -ir UID="0"
$ unset TMOUT
-bash: unset: TMOUT: cannot unset: readonly variable
$ cat << EOF| sudo gdb
attach $$
call unbind_variable("TMOUT")
detach
EOF
$ echo $TMOUT
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
28 January 2020
UID
ibm11284454