Troubleshooting
Problem
The server does not start and the symptoms suggest that the system hostname was changed, but the system administrator did not change the hostname.
Symptom
Restart fails with errors:
ANR0990I Server restart-recovery in progress.
ANR0151W Database manager fails to start. For more information about the failure, issue the db2start command.
ANR0171I dbiconn.c(1844): Error detected on 0:1, database in evaluation mode.
ANR0169E An unexpected error has occurred and the TSM server is stopping.
ANR0162W Supplemental database diagnostic information: -1:58031:-1031 ([IBM][CLI Driver] SQL1031N The database directory cannot be found on the indicated file system. SQLSTATE=58031).
In the db2diag.log, the following events appear:
2016-01-21-09.43.04.784715+060 E38694124E421 LEVEL: Error (OS)
PID : 21857 TID : 140737028351776 PROC : db2start
INSTANCE: tsminst1 NODE : 000
HOSTNAME: hostxxx
FUNCTION: DB2 UDB, oper system services, sqloRemoteShell, probe:50
CALLED : OS, -, execvp OSERR: ENOENT (2)
MESSAGE : Error invoking remote shell program.
DATA #1 : String, 12 bytes
/usr/bin/rsh
2016-01-21-09.43.05.787938+060 E38694546E769 LEVEL: Warning
PID : 21854 TID : 140737028351776 PROC : db2start
INSTANCE: tsminst1 NODE : 000
HOSTNAME: hostxxx
FUNCTION: DB2 UDB, oper system services, sqloPdbInitializeRemoteCommand, probe:110
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error"
DATA #1 : String, 348 bytes
The remote shell program terminated prematurely. The most likely causes are either that the DB2RSHCMD registry variable is set to an invalid setting, or the remote command program failed to authenticate. It can also be the remote daemon is not completely started up yet to handle the request. This attempt will retry a few times before giving up.
DATA #2 : String, 12 bytes
/usr/bin/rsh
2016-01-21-09.43.05.788728+060 E38695316E514 LEVEL: Error
PID : 21854 TID : 140737028351776 PROC : db2start
INSTANCE: tsminst1 NODE : 000
HOSTNAME: hostxxx
FUNCTION: DB2 UDB, oper system services, sqloPdbInitializeRemoteCommand, probe:200
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error"
DATA #1 : String, 6 bytes
hostxxx
DATA #2 : String, 24 bytes
hostxxx.tst.ibm.com
DATA #3 : String, 51 bytes
No diagnostics available from remote shell program.
Cause
For an unknown reason, the hostname returned by the OS command "hostname", changed from the Fully Qualified Domain Name ( FQDN ) to a single name. Example :
The host "hostxxx.tst.ibm.com" becomes "hostxxx"
This causes a problem with DB2, because the hostname returned does not match the name recorded in the db2nodes.cfg file.
Environment
Linux Tivoli Storage Manager V7 server.
Diagnosing The Problem
Look in the db2diag.log . In previous event entries, the "HOSTNAME: hostxxx" lines, changed from the FQDN to a single name or the reverse, so from a single name to the FQDN.
Resolving The Problem
Ask the system administrator to correct the hostname at the system level, or change the hostname within DB2 as documented in the manual. Below are some links to the manual pages and to the technote.
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21975997