{"id":309,"date":"2016-02-06T15:06:33","date_gmt":"2016-02-06T09:36:33","guid":{"rendered":"http:\/\/www.middlewareprimer.com\/blog\/?p=309"},"modified":"2016-02-06T15:06:33","modified_gmt":"2016-02-06T09:36:33","slug":"sql6048n-a-communication-error-occurred-during-start-or-stop-database-manager-processing","status":"publish","type":"post","link":"http:\/\/www.middlewareprimer.com\/blog\/2016\/02\/06\/sql6048n-a-communication-error-occurred-during-start-or-stop-database-manager-processing\/","title":{"rendered":"SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing"},"content":{"rendered":"<p>SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing, message pops up when we try to start DB2 (v9.7). While contacting the customer, I came to know that there was a VM restart and after that DB2 was not starting at all.<\/p>\n<p>Following was coming up during start command of the database,<\/p>\n<p>[root@&lt;hostname&gt; adm]# .\/db2start<br \/>\n02\/01\/2016 20:09:57\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0 0\u00a0\u00a0 SQL6048N\u00a0 A communication error occurred during START or STOP DATABASE MANAGER processing.<br \/>\nSQL1032N\u00a0 No start database manager command was issued.\u00a0 SQLSTATE=57019<\/p>\n<p><span style=\"text-decoration: underline;\"><strong>Resolution<\/strong><\/span><\/p>\n<p>1. Make sure that you have proper user rights to start the database.<\/p>\n<p>2. Make sure that hostname is defined properly in db2nodes.cfg file.<\/p>\n<p>Navigate to &lt;db2instancename&gt;\/sqllib directory and then edit the db2nodes.cfg file with proper hostname.<\/p>\n<p>[root@&lt;hostname&gt; adm]# cd \/home\/&lt;db2instancename&gt;\/sqllib\/<br \/>\n[root@&lt;hostname&gt; sqllib]# vi db2nodes.cfg<\/p>\n<p>Make sure that the hostname is defined within 0 &amp; 0. Dont delete the zeroes over there and edit the file with proper hostname. If FQDN is used as hostname, make sure that the same is used in the config file.<\/p>\n<p>example: if my hostname is pi.middlewareprimer.com then your db2nodes.cfg file should have as below,<\/p>\n<p>0 pi.middlewareprimer.com 0<\/p>\n<p>After editing the file, it resolved the issue and I was able to start the database.<\/p>\n<p>IBM Technotes for reference,<\/p>\n<p><a href=\"http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21221940\" target=\"_blank\">http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21221940<\/a><\/p>\n<p><a href=\"http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21443907\" target=\"_blank\">http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21443907<\/a><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing, message pops up when we try to start DB2 (v9.7). While contacting the customer, I came to know that there was a VM restart and after that DB2 was not starting at all. Following was coming up during start command of the database, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[80],"tags":[82,88,87],"class_list":["post-309","post","type-post","status-publish","format-standard","hentry","category-ibm-db2","tag-db2-v9-7","tag-ibm-db2","tag-sql6048n"],"_links":{"self":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/309","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/comments?post=309"}],"version-history":[{"count":2,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/309\/revisions"}],"predecessor-version":[{"id":315,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/309\/revisions\/315"}],"wp:attachment":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/media?parent=309"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/categories?post=309"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/tags?post=309"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}