DB2 启动/远程连接失败错误: SQL5043N 解决一例

Categories: Database; Tagged with: DB2 • SQL5043N; @ October 2nd, 2010 16:24

改动了下端口, 结果重新start时出现错误.

在本机使用DB2正常, 但无法从远程使用. telnet 50000端口失败.
本机telnet 50000端口, 失败.

db2cmd中报错:

SQL5043N Support for one or more communications protocols failed to start sussfully. However, core database manager functionality started successfully.

用CC时UI报错:

Support for one or more communications protocols failed to start
successfully. However, core database manager functionality
started successfully.

Explanation:

Communication protocol support did not start successfully for one or
more protocols. Possible reasons can include the following:
* Communication subsystem configuration error.
* Communication subsystem call failure.
* Database manager configuration error.
* System call failure.
* Database manager licensing error.
* Cluster manager call failure.

You can still connect to the server with communication protocols that
did start successfully. Local clients can also connect to the server.

User response:

The database manager attempts to start all communication protocols
specified by the DB2COMM environment variable.

Check the administration notification log for details on this error. The
log will contain more information on the cause of the error and also
which communication protocol(s) did not start successfully.

This error only affects communication protocols specified by the DB2COMM
environment variable.

解决方法:

运行db2diag, 或查看db2diag.log, 最新的Error:

2010-10-02-16.15.37.298000+480 I467399H464        LEVEL: Error
PID     : 2424                 TID : 1580        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
EDUID   : 1580                 EDUNAME: db2sysc
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr, probe:5
MESSAGE : DIA3201E The service name "db2c_DB2" specified in the database
          manager configuration file cannot be found in the TCP/IP services file.

豁然了, 说services中没有对应的配置…

但我的问题是配置无误, 只是配置在etc/services最后一行, 而且没有注释. 如:

"db2c_DB2 50000/tcp" —– 此种情况下死活不工作.

最终解决方法:

加一个注释或在后面增加其他Instance对应端口后, 可正常工作. 如:

"db2c_DB2 50000/tcp #DB2 Port"

小记DB2远程连接不上解决

为什么客户端连服务器总是报错SQL30081N错？？？ http://www.itpub.net/thread-477760-1-7.html

Windows下DB2端口查看/修改/分配 <-> 通过JDBC连接DB2错误Connection timed out错误排除