db2start fails with SQL6048N in HACMP configuration

Technote (troubleshooting)


Problem(Abstract)

SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing.

Symptom

In a new HACMP setup with DB2 Version 9, db2start fails with SQL6048N when attempting to start the DB2 instance. From the db2diag.log file you will see similar messages as below:

2011-12-07-11.33.33.941087-300 I19969A433         LEVEL: Event
PID     : 1192104              TID  : 1           PROC : db2start
INSTANCE: db2inst1               NODE : 000          
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 68 bytes
/opt/hd/db/db2/instance/db2inst1/sqllib/adm/db2rstar db2profile SN 0 0
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9B2C : 0000 0010                                  ....

2011-12-07-11.34.03.947445-300 E20403A703         LEVEL: Error
PID     : 1192104              TID  : 1           PROC : db2start
INSTANCE: db2inst1               NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloPdbInitializeRemoteCommand,
probe:120
MESSAGE : ZRC=0x810F001A=-2129723366=SQLO_CONN_TIMEOUT "Connection timed
out"
DATA #1 : <preformatted>
DB2 timed out waiting for a response from the remote node. The most
likely causes are either an authentication failure with the remote shell
program (/usr/bin/rsh), or the remote shell program is taking an excessive amount of time to authenticate.  The timeout value is 30 seconds, and can be modified using the DB2RSHTIMEOUT registry variable.

2011-12-07-11.34.03.947829-300 E21107A511         LEVEL: Error
PID     : 1192104              TID  : 1           PROC : db2start
INSTANCE: db2inst1               NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloPdbInitializeRemoteCommand, probe:200
MESSAGE : ZRC=0x810F001A=-2129723366=SQLO_CONN_TIMEOUT "Connection timed out"
DATA #1 : String, 22 bytes
cpaiqpb1.ibm.com
DATA #2 : String, 22 bytes
pqpdi200.ibm.com
DATA #3 : String, 51 bytes                    
No diagnostics available from remote shell program.

2011-12-07-11.34.03.947978-300 I21619A279         LEVEL: Event
PID     : 1192104              TID  : 1           PROC : db2start
INSTANCE: db2inst1               NODE : 000        
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:80
DATA #1 : signed integer, 4 bytes
-6048

Cause

From the db2diag.log, it shows that you are not getting a response from pqpdi200.ibm.com in a timely manner which causing db2stat to fail. The error is a bit miss leading The cause of the problem was due to incorrect permissions on the /etc/.rhosts file. The permissions were set to 644


-rw-rw-rw- 1 db2inst1 db2sadm 139 Dec 07 11:25 .rhosts

According to the rsh man pages, its recommended to set the permissions to 600 for owner.

Although you can set any permissions for the $HOME/.rhosts file, it is
recommended that the permissions of the .rhosts file be set to 600
(read and write by owner only).


Related information

rsh or remsh commands

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows
High Availability - High Availability Data Replication (HDR)

Software version:

9.1, 9.5, 9.7

Operating system(s):

AIX

Software edition:

Advanced Enterprise Server, Enterprise Server

Reference #:

1575690

Modified date:

2013-01-04

Translate my page

Machine Translation

Content navigation