IBM Support

Instance fails to start with error SQL6030N reason code "19"

Troubleshooting


Problem

db2start command failed with error SQL6030N START or STOP DATABASE MANAGER failed. Reason code "19".

Symptom

The following is an example of command output
$ db2start dbpartitionnum 1

05/04/2013 21:43:33    97   0   SQL6030N  START or STOP DATABASE MANAGER failed.  Reason code "19".

SQL1032N  No start database manager command was issued.  SQLSTATE=57019

You may also find the following entries in db2diag.log:


2013-05-04-21.31.10.459302-180 E6039A453          LEVEL: Error (OS)
PID     : 12345678             TID  : 1234        PROC : db2sysc 1
INSTANCE: db2inst1             NODE : 001
EDUID   : 1234                 EDUNAME: db2fcmr 1
FUNCTION: DB2 UDB, oper system services, sqloPdbBindSocket, probe:20
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error"
CALLED  : OS, -, bind
OSERR   : EADDRNOTAVAIL (68) "Can't assign requested address"


2013-05-04-21.31.10.460345-180 I6493A434          LEVEL: Severe
PID     : 12345678             TID  : 1234        PROC : db2sysc 1
INSTANCE: db2inst1             NODE : 001
EDUID   : 1234                 EDUNAME: db2fcmr 1
FUNCTION: DB2 UDB, fast comm manager, sqkfTcpServices::allocRemoteLinkResource, probe:100
RETCODE : ZRC=0x8159006D=-2124873619=SQLKF_SOCKDIR_NOT_CREATED
          "FCM socket directory not created successfully"

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Database Objects\/Config - Instance","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"9.8;9.7;9.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
01 May 2025

UID

swg21636395