A Communication Error Occurred During Start
Contents |
SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing. Symptom When trying to start an instance using the db2start command, the following error is received. SQL6048N A a communication error occurred during start or stop database manager processing communication error occurred during START or STOP DATABASE MANAGER processing. Cause The examples are
An Error Occurred During Communication With The Server
shown below : 1. Your system might have a different hostname than the hostname listed in
$ db2_all "echo OK"
rshd: 0826-813 Permission is denied.
rshd: 0826-813 Permission is denied.
Run the the following command to display related information: db2 ? SQL6048N Resolving the problem Resolve the problem using one of these solutions: If the hostname displayed by the hostname command is different than the hostname
An Error Occurred During Communication With The Server This Is A Dns Error
from
OK
coralpib135: echo OK completed ok
OK
coralpib137: echo OK completed ok Step 3: Run the db2stop or db2start command. $ db2stop
11/29/2011 01:45:13 0 0 SQL1064N DB2STOP processing was successful.
11/29/2011 01:45:13 1 0 SQL1064N DB2STOP processing was successful.
SQL1064N DB2STOP processing was successful. This is one of the method to solve the MPP start problem. If user runs the db2 ? command, SQL6048N will display related information. Document information More support for: DB2 for Linux, UNIX and Windows DBA/System Administration - db2start/db2stop Software version: 9.1, 9.5, 9.7, 10.1, 10.5, 11.1 Operating system(s): AIX, HP-UX, Linux, Solaris Software edition: Enterprise Server Reference #: 1443907 Modified date: 2016-07-20 Site availability Site assistance Contact and feedback Need support? Subm
How to resolve db2start failing with SQL6048N error in MPP environment? Symptom Following error will be thrown when db2start is an error occurred during ssl communication issued trying to establish connection with all the nodes defined in the a communication error occurred during operations on the connection's underlying socket sqllib/db2nodes.cfg file including the new node you attempted to add.: Eg: $home/../sqllib> db2start 10/18/2011 03:54:21 1 0 SQL6048N
A Communication Error Occurred During The Fax Transmission
A communication error occurred during START or STOP DATABASE MANAGER processing. 10/18/2011 03:54:22 2 0 SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing. 10/18/2011 03:54:23 http://www-01.ibm.com/support/docview.wss?uid=swg21443907 3 0 SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing. 10/18/2011 03:54:25 4 0 SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing. 10/18/2011 03:54:25 0 0 SQL1026N The database manager is already active. SQL6032W Start command processing was attempted on "5" node(s). "0" node(s) were successfully started. "1" node(s) were http://www-01.ibm.com/support/docview.wss?uid=swg21578906 already started. "4" node(s) could not be started. db2diag.log file entries would be similar to the following when host name is not a fully qualified name: 2011-10-18-01.57.59.083502-240 E3289784E602 LEVEL: Error PID : 7397 TID : 47343526210544PROC : db2start INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, oper system services, sqloPdbInitializeRemoteCommand, probe:110 MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error" DATA #1 : String, 204 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. DATA #2 : String, 12 bytes /usr/bin/ssh 2011-10-18-01.57.59.083676-240 E3290387E504 LEVEL: Error PID : 7397 TID : 47343526210544PROC : db2start INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, oper system services, sqloPdbInitializeRemoteCommand, probe:200 MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error" DATA #1 : String, 37 bytes myserver.spifnet.ibm.com DATA #2 : String, 17 bytes myserver DATA #3 : String, 38 bytes db2rcmd: Failed to getaddrinfo, rc -2 So issue is with getaddrinfo. Cause The issue may be caused by one of the following reason: Logical
with Chef and Docker. Follow @leonsp Recent Posts Enable better git diffs on the http://lpetr.org/blog/archives/sql6048n-a-communication-error-occurred-during-start-or-stop-database-manager-processing Mac 656x Faster JSON Parsing in Python with ijson Preserve bash history across multiple terminals and sessions No meta description has been specified Datathon For Diabetes in https://bytes.com/topic/db2/answers/672350-need-help-db2-db2start-throwing-sql6048n-error Boston Categories Announcement (18) Big Data (12) Blogging (1) Database (51) Mac (6) Opinion (2) Python (1) Software development (6) Unix (19) Web applications (11) Web error occurred browsers (4) Web development (16) Web sites (8) Windows (13) SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing I've written about issues related to "SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing" before, but I thought I'd add a few short notes. Your machine needs error occurred during to be able to ping itself. If it can't ping itself, it can't DB2 itself either. The output of hostname, db2set -all, and cat /home/db2inst1/sqllib/db2nodes.cfg needs to match. If your machine can't ping itself, cat /etc/hosts. Chances are, you need to add a line like the following: 127.0.0.1 myhostname.mydomain myhostname 1 127.0.0.1 myhostname.mydomain myhostname 1 If DB2SYSTEM is set to the wrong value, db2set -g DB2SYSTEM=hostname will fix it on Linux. If db2nodes.cfg has the wrong value, overwrite it with the right one. Published by Leons Petrazickis I'm a full-stack developer at IBM Analytics Emerging Technologies. I do Ruby, JS, Python, Hadoop, Spark, as well as web scale devops with Chef and Docker. My opinions are my own. View all posts by Leons Petrazickis Posted on Fri 2011-10-21Thu 2011-10-20Author Leons PetrazickisCategories Database Post navigation Previous Previous post: Chairing a Hadoop workshop at CASCON 2011Next Next post: Materials for the Hadoop workshop at CASCON Proudly powered by WordPress
help? Post your question and get tips & solutions from a community of 418,417 IT Pros & Developers. It's quick & easy. Need Help with db2 db2start throwing SQL6048N error P: n/a LittleMaster Dear Gurus Please help. I have installed DB2 8.2 on AIX 5.3. No apparent errors while installing. I opted the defaults to create the instance db2inst1 But when I do a db2start, I get the following error 07/03/2007 21:51:03 0 0 SQL6048N A Communication error occurred during START or STOP DATABASE MANAGER processing. SQL1032N No start database manager command was issued. SQLSTATE=57019 Please help. I am trying to connect to DB from the same server (both client and server on same system) Thanks Jul 4 '07 #1 Post Reply Share this Question 2 Replies P: n/a db2start On Jul 4, 5:56 am, LittleMaster