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

Symptom

System has undergone maintenance and cannot be started.
Db2start fails with error
SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing.
SQL1032N No start database manager command was issued. SQLSTATE=57019

The db2diag.log reports errors like:
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.

FUNCTION: DB2 UDB, oper system services, sqloPdbInitializeRemoteCommand, probe:200 MESSAGE : ZRC=0x810F001A=-2129723366=SQLO_CONN_TIMEOUT "Connection timed out"

Environment

Db2 LUW IBM

Product

SAP enhancement package 1 for SAP NetWeaver 7.0

Keywords

connection, maintenance, down, cannot connect, crash, recovery, remote, authenticate, host, ID, shell, ssh, , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.