Results 1 to 11 of 11
  1. #1
    Join Date
    Mar 2006
    Posts
    104

    Unanswered: [IBM][CLI Driver] SQL30081N A communication error has been detected.

    We are using DB2 version 7.2.5 and websphere application server 5.1.5.

    Occasionaly we get a communication error connecting to database through Websphere Datasource.

    Any idea why this error is comming? Can it be due to network problems?


    The Error in websphere log is

    STATE: 08001; MESSAGE: [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
    DSRA0010E: SQL State = 08001, Error Code = -30,081; ERROR_CODE: -30081
    java.sql.SQLException: [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


    Thanks
    DSRA0010E: SQL State = 08001, Error Code = -30,081

  2. #2
    Join Date
    Oct 2004
    Location
    DELHI INDIA
    Posts
    338
    Hi Dear,
    If your WEBSPHERE is on a different machine and on that DB2 client is installed, then take the entry in the db2diag.log at the client machine as well as in the DB2 Server machine.

    I hope looking at the db2diag.log people can give you better suggestion.

  3. #3
    Join Date
    Oct 2004
    Location
    DELHI INDIA
    Posts
    338
    Hi Dear,
    If your WEBSPHERE is on a different machine and on that DB2 client is installed, then take the entry in the db2diag.log at the client machine as well as in the DB2 Server machine.

    I hope looking at the db2diag.log people can give you better suggestion.

  4. #4
    Join Date
    Mar 2006
    Posts
    104
    Thanks for the reply Jayant.
    The websphere and db2 are running in different machines.

    The db2 server has no error entries.

    The entries in db2diag.log in client machine are:

    2006-03-04-16.57.51.734000 InstanceB2 Node:000
    PID:3424(java.exe) TID:5976 Appid:015DC746.B104.060303052002
    common_communication sqlcctcpconnr Probe:101
    DIA3202C The TCP/IP call "connect" returned an errno="10060".

    2006-03-05-00.00.22.093000 InstanceB2 Node:000
    PID:4424(java.exe) TID:2224 Appid:
    common_communication sqlcctcpconnr Probe:101
    DIA3202C The TCP/IP call "connect" returned an errno="10060".

    2006-03-05-04.46.22.781000 InstanceB2 Node:000
    PID:3424(java.exe) TID:4544 Appid:015DC746.B104.060303052002
    common_communication sqlcctcpconnr Probe:101
    DIA3202C The TCP/IP call "connect" returned an errno="10060".


  5. #5
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    For a start, a couple of things to check ...

    a) Can the websphere machine connect to the db2 machine ... can you ping from one another ..

    b) What is the port number on the server DB2 is configure ..

    db2 get dbm cfg , SVCENAME config parm ...

    netstat -an | find "<portnum>"

    Is the DB2 server really listening ?

    c) On the client is the node directory referring to the correct host (ping using this hostname) and the portnumber as identified above ...

    d) on the server, have you set the registry variable, DB2COMM set to TCPIP

    db2set -all

    Cheers
    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  6. #6
    Join Date
    Mar 2006
    Posts
    104
    Hi Sathyam,

    a) Can the websphere machine connect to the db2 machine ... can you ping from one another ..

    yes

    b) What is the port number on the server DB2 is configure ..

    db2 get dbm cfg , SVCENAME config parm ...

    netstat -an | find "<portnum>"

    Is the DB2 server really listening ?

    YES

    c) On the client is the node directory referring to the correct host (ping using this hostname) and the portnumber as identified above ...

    YES
    d) on the server, have you set the registry variable, DB2COMM set to TCPIP

    YES

  7. #7
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Ha ... I missed the term occassionally in your original post. If this is the case, yes, I would say it is very likely to be network issues

    Sathyaram

    Quote Originally Posted by sundaram
    Occasionaly we get a communication error connecting to database through Websphere Datasource.

    Any idea why this error is comming? Can it be due to network problems?
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  8. #8
    Join Date
    Mar 2006
    Location
    UK
    Posts
    8

    communication error

    hi sundaram

    I also got this problem in my setup,I have logged a PMR for this 2 days back and they asked me to visit this site and i hope it will be helpful for you also

    http://www-1.ibm.com/support/docview...UTF-8&lang=all


    Let me know for any further info

  9. #9
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Did this solve your problem ??

    When I had a similar issue, I tried all such settings and they didn't help .. As the client was communicating over a WAN to a remote database server, certain firewall settings caused timeout and DB2 received this error .. So the network guys had to make some configuration changes ... Well, this was back in 2000 ...

    Of course, every environment is unique

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  10. #10
    Join Date
    Mar 2006
    Location
    UK
    Posts
    8
    Hi
    As I mentioned that it happens 2 days back only,I am yet to test this.

    Just pass the info if it can help

    Regards
    Ati

  11. #11
    Join Date
    Mar 2006
    Posts
    104
    Hi

    That link is quite useful. We will try it out and let the forum know of the outcome.


    Thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •