Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Pool
    New Member
    • Jun 2007
    • 7

    Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001

    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 specific error code(s): "10060", "*", "*". SQLSTATE=08001
  • mimifat
    New Member
    • Apr 2009
    • 2

    #2
    Hi

    Is this problem fixed?
    I also encounter this on my platform SUSE10 .Hope someone will help

    Comment

    • Shashank1984
      New Member
      • Jul 2007
      • 26

      #3
      Folks,
      Here is the list of some SQL30081N TCP/IP communication protocol errors and recommended action plans associated with them.


      Cheers !
      Thanks,
      Shashank Kharche, IBM.
      DB2 for Linux, Unix & Windows -Information Management Software

      Comment

      • mimifat
        New Member
        • Apr 2009
        • 2

        #4
        Thanks, I will check in to it.

        Comment

        • hitendrap
          New Member
          • Sep 2009
          • 9

          #5
          FOR : error code 10065

          If u are getting: SQL30081N Protocol specific error code(s): "10065", "*", "*". SQLSTATE=08001

          If you are using Linux server , turn off your firewall service & check if you can connect to database remotely through

          client
          to stop firewall type this command on bash : $ etc/init.d/iptables stop

          If now you can connect remotely thru client then
          turn OFF firewall service from all run levels
          before that check

          $ chkconfig --list iptables

          if they are ON @ runlevels 2,3,4,5 then

          $ chkconfig --levels 2345 iptables off


          Regards.
          Hitendra

          Comment

          Working...