Db2 Protocol Specific Error Codes
Contents |
gateway CONNECT; TCP/IP; SOCKET; SQL30081N ; 79 Technote (FAQ) Question I tried to connect to a remote DB2 server, and received http://www.ibm.com/support/docview.wss?uid=swg21179858 the following error message: "SQL30081N A communication error has been detected. Communication protocol https://bytes.com/topic/db2/answers/664733-protocol-specific-error-code-s-10060-sqlstate-08001-a 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 error codes 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 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 db2 error codes command line: db2set Verify that the entries in the TCP/IP services files on the client and gateway machines match the following settings. 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 | p
Ask a Question Need help? Post your question and get tips & solutions from a community of 418,478 IT Pros & Developers. It's quick & easy. Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001 P: 7 Pool I tried to connect DB2 (Sitting in Unix server at my client location) using Db2 connect V8. I am getting the following error message. I tried all the possible options BUt the error is same.. See each type belpw Standard connection failed. SQL30081N A communication 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): "10060", "*", "*". SQLSTATE=08001 CLI connection failed. SQL30081N A communication 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): "10060", "*", "*". SQLSTATE=08001 OLEDB connection failed. SQL30081N A communication 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): "10060", "*", "*". SQLSTATE=08001 JDBC connection failed. [IBM][CLI Driver] SQL30081N A communication 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): "10060", "*", "*". SQLSTATE=08001 ADO connection failed. SQL30081N A communication 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 spec