db2start using an alias in db2nodes.cfg will reports below
error :
$ db2start
SQL6048N A communication error
occurred during START or STOP DATABASE MANAGER processing.
SQL1032N No start database manager command was issued.
SQLSTATE=5701
db2diag.log entries :
2014-05-28-15.48.34.247523-300 E86136E426 LEVEL:
Error (OS)
PID : XXXX TID : XXXX PROC : db2start
INSTANCE: testdb NODE : 000
HOSTNAME: testdb
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
2014-05-28-15.48.35.249777-300 E86563E774 LEVEL:
Warning
PID : XXX TID : XXX PROC : db2start
INSTANCE: testdb NODE : 000
HOSTNAME: testdb
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
2014-05-28-15.48.35.250119-300 E87338E507 LEVEL:
Error
PID : XXX TID : XXX PROC : db2start
INSTANCE: testdb NODE : 000
HOSTNAME: testdb
FUNCTION: DB2 UDB, oper system services,
sqloPdbInitializeRemoteCommand, probe:200
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR
"Communication error"
DATA #1 : String, 11 bytes
testdb
DATA #2 : String, 7 bytes
db2host
DATA #3 : String, 51 bytes
No diagnostics available from remote shell program.
2014-05-28-15.48.35.250330-300 I87846E1157 LEVEL:
Event
PID : XXXXX TID : XXXX PROC : db2start
INSTANCE:testdb NODE : 000
HOSTNAME: testdb
FUNCTION: DB2 UDB, oper system services, sqloPdbOpenConnection,
probe:10
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR
"Communication error"
DATA #1 : String, 27 bytes
Retry the connection again.
DATA #2 : unsigned integer, 8 bytes
30
DATA #3 : unsigned integer, 8 bytes
30
CALLSTCK: (Static functions may not be resolved correctly, as
they are
resolved to the nearest symbol) Page 15 of 44
[0] 0x00007FFFF048B2A1 sqloPdbOpenConnection + 0x2D1
[1] 0x00007FFFF048AE68 sqloPdbStartStopNode + 0x138
[2] 0x00007FFFEF6B6D00
_Z20sqlePdbStartStopNodeiP13sqlo_nodelinePcS1_tS1_mP25sqlo_start
_stop_no
de_infom + 0x280
[3] 0x00007FFFEF6A7A72
_Z18sqleIssueStartStopiPvPcS0_P9sqlf_kcfdP18SQLE_INTERNAL_ARGSjj
P5sqlca
+ 0x2512
[4] 0x00007FFFEF6A3FDC
_Z20sqleProcessStartStopiPvP18SQLE_INTERNAL_ARGSP9sqlf_kcfdPcjjP
5sqlca
+ 0x52C
[5] 0x0000000000405CEC main + 0x268C
[6] 0x000000384D81ED1D __libc_start_main + 0xFD
[7] 0x00000000004035C9 __gxx_personality_v0 + 0x1A1
2014-05-28-15.48.36.252882-300 I89004E1202 LEVEL:
Error
PID : XXXX TID : XXX PROC : db2start
INSTANCE: testdb NODE : 000
HOSTNAME: testdb
FUNCTION: DB2 UDB, oper system services, sqloPdbOpenConnection,
probe:15
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR
"Communication error"
DATA #1 : Codepath, 8 bytes
1:3:5:11
DATA #2 : String, 35 bytes
Give up the remote command attempt.
DATA #3 : unsigned integer, 8 bytes
30
DATA #4 : unsigned integer, 8 bytes
30
CALLSTCK: (Static functions may not be resolved correctly, as
they are
resolved to the nearest symbol)
[0] 0x00007FFFF048B34B sqloPdbOpenConnection + 0x37B
[1] 0x00007FFFF048AE68 sqloPdbStartStopNode + 0x138
[2] 0x00007FFFEF6B6D00
_Z20sqlePdbStartStopNodeiP13sqlo_nodelinePcS1_tS1_mP25sqlo_start
_stop_no
de_infom + 0x280
[3] 0x00007FFFEF6A7A72
_Z18sqleIssueStartStopiPvPcS0_P9sqlf_kcfdP18SQLE_INTERNAL_ARGSjj
P5sqlca
+ 0x2512
[4] 0x00007FFFEF6A3FDC
_Z20sqleProcessStartStopiPvP18SQLE_INTERNAL_ARGSP9sqlf_kcfdPcjjP
5sqlca
+ 0x52C
[5] 0x0000000000405CEC main + 0x268C
[6] 0x000000384D81ED1D __libc_start_main + 0xFD
[7] 0x00000000004035C9 __gxx_personality_v0 + 0x1A1
2014-05-28-15.48.36.255432-300 I90207E309 LEVEL:
Event
PID : XXXXX TID : XXXXX PROC : db2start
INSTANCE: testdb NODE : 000
HOSTNAME: testdb
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop,
probe:8338
DATA #1 : signed integer, 4 bytes
-6048
2014-05-28-15.48.36.275852-300 I90517E1273 LEVEL:
Event
PID : XXXX TID : XXX PROC : db2start
INSTANCE: testdb NODE : 000
HOSTNAME: testdb
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop,
probe:10120
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6048 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLEOCON
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1032 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLEPFIN
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11) |
