Error Code=-30081 Sqlstate=08001
Contents |
connecting Controller application server to DB2 database server Technote (troubleshooting) Problem(Abstract) Administrator is trying to test communication between the Controller application server and the
Protocol Specific Error Code(s) 10060 * * . Sqlstate=08001
DB2 database server. For example, administrator opens a command prompt (D:\Program Files\IBM\SQLLIB\BIN) protocol specific error code(s): "*", "*", "0". sqlstate=08001 and runs a command similar to: db2 connect to
Sql30081n A Communication Error Has Been Detected.
SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "
gateway CONNECT; TCP/IP; SOCKET; SQL30081N ; 79 Technote (FAQ) Question I tried to connect to a remote DB2 server, and received the following error message: "SQL30081N A communication http://www.ibm.com/support/docview.wss?uid=swg21179858 error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "79", "*", "*". SQLSTATE=08001" Cause The following error occurs when a remote client fails to connect to DB2 Connect gateway: SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error protocol specific was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "79", "*", "*". SQLSTATE=08001 Answer Complete the following steps to resolve solve the problem: Verify that the DB2COMM profile variable is set to tcpip on the DB2 Connect gateway by entering the following on a DB2 command line: db2set Verify that the entries in the TCP/IP services files on the client and gateway machines match the following settings. protocol specific error There might be a mismatch between the TCP/IP service name and/or the port number specifications on the DB2 client and the DB2 Connect gateway. Open a DB2 command window on the DB2 server, and enter: db2 get dbm cfg | grep SVCENAME For example, if TCP/IP Service name (SVCENMAE) = db2c_db2inst1, then you would enter: db2 get dbm cfg | grep db2c_db2inst1 Open the services file from /etc, and get the port number for this service. For example: db2c_db2inst1 50000/tcp Open a DB2 command window on the client machine, and enter: db2 list node directory Make sure that the service name is set to the correct port number listed in the services directory for the DB2 instance. If the port number in the client side does not match with the server, you must uncatalog the node from client machine: db2 uncatalog node node_name Recatalog node to the proper port value: db2 catalog tcpip node node_name remote [hostname | ip_address] server [svcename | port_number]. Verify that DB2 is started on the DB2 connect gateway: On the gateway machine, set the Database Manager Configuration diaglevel to 4. Open a DB2 command window and enter: db2 update dbm cfg using diaglevel 4 After stopping and restarting DB2, look in the db2diag