ERROR [40003] [IBM][CLI Driver] SQL30081N A communication error has been detected. Communic

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Tim Reynolds
    #1

    ERROR [40003] [IBM][CLI Driver] SQL30081N A communication error has been detected. Communic

    I support a .Net application running on a SERVER accessing MF Db2
    data. Occasionally, we have some type of connection problem that we
    have been unable to debug up to this point. We typically receive one
    of these IBM.Data.DB2.DB 2Exception messages:

    ERROR [40003] [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: ‘138.83.176.1'. Communication function detecting the error:
    ‘recv'. Protocol specific error code(s): ‘10053', ‘*', ‘*'.
    SQLSTATE=08001

    This corresponds to some messages in the DB2 started task running on
    the MF:

    10.30.57 STC11095 DSNL511I -DB2C DSNLIENO TCP/IP CONVERSATION FAILED
    866
    866 TO LOCATION 112.64.103.172
    866 IPADDR=112.64.1 03.172 PORT=2655
    866 SOCKET=RECV RETURN CODE=1121 REASON
    CODE=76650446
    10.31.08 STC11095 DSNL511I -DB2C DSNLIENO TCP/IP CONVERSATION FAILED
    032
    032 TO LOCATION 112.64.103.172
    032 IPADDR=112.64.1 03.172 PORT=3180
    32 SOCKET=RECV RETURN CODE=1121 REASON CODE=76650446


    Along with the Communication error exception, we typically also
    receive some other exceptions during this time, mainly....

    Inner Exception Type: IBM.Data.DB2.DB 2Exception ;Inner Exception
    Message: ERROR [08003] [IBM][CLI Driver] CLI0106E Connection is
    closed. SQLSTATE=08003

    So the communication problem (whatever it is) seems to manifest in the
    first exception - Communication problem - and this must hose up some
    of our connections so at that point, we begin to receive the
    Connection is Closed message.

    Our C# instansiates a DB2Connectin object and issues an open against
    it. Then an executeNonQuery statement to run the SP. It is pretty
    standard code and works nearly all the time. We think our problem is
    load related - b/c we only encounter under productin load and more so
    on our busiest servers.

    Any help greatly appreciated.

    Tim Reynolds
    Verizon Data Services
    Tags: None
    • dps027
      #2
      Re: ERROR [40003] [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: '138.83.176.1'. Communication fun

      Hi -

      some time ago I got similar communication errors in an earlier FP version
      (FP9??) of UDB for Windows v7. After I installed the FP11, the problem was
      resolved.

      For my particular problem, it was actually the case that some UDB problems
      caused out-of-memory situation, and hence caused the communication failed.
      In other words, the communication errors did not show the root cause, and
      actually it also spent me quite some time to identify the root cause
      problem. So you may want to check if there are other errors besides the
      communication errors.

      aw


      "Tim Reynolds" <tim.reynolds@v erizon.com> wrote in message
      news:a5ec0f10.0 409160952.27383 2f4@posting.goo gle.com...[color=blue]
      > I support a .Net application running on a SERVER accessing MF Db2
      > data. Occasionally, we have some type of connection problem that we
      > have been unable to debug up to this point. We typically receive one
      > of these IBM.Data.DB2.DB 2Exception messages:
      >
      > ERROR [40003] [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: '138.83.176.1'. Communication function detecting the error:
      > 'recv'. Protocol specific error code(s): '10053', '*', '*'.
      > SQLSTATE=08001
      >
      > This corresponds to some messages in the DB2 started task running on
      > the MF:
      >
      > 10.30.57 STC11095 DSNL511I -DB2C DSNLIENO TCP/IP CONVERSATION FAILED
      > 866
      > 866 TO LOCATION 112.64.103.172
      > 866 IPADDR=112.64.1 03.172 PORT=2655
      > 866 SOCKET=RECV RETURN CODE=1121 REASON
      > CODE=76650446
      > 10.31.08 STC11095 DSNL511I -DB2C DSNLIENO TCP/IP CONVERSATION FAILED
      > 032
      > 032 TO LOCATION 112.64.103.172
      > 032 IPADDR=112.64.1 03.172 PORT=3180
      > 32 SOCKET=RECV RETURN CODE=1121 REASON CODE=76650446
      >
      >
      > Along with the Communication error exception, we typically also
      > receive some other exceptions during this time, mainly....
      >
      > Inner Exception Type: IBM.Data.DB2.DB 2Exception ;Inner Exception
      > Message: ERROR [08003] [IBM][CLI Driver] CLI0106E Connection is
      > closed. SQLSTATE=08003
      >
      > So the communication problem (whatever it is) seems to manifest in the
      > first exception - Communication problem - and this must hose up some
      > of our connections so at that point, we begin to receive the
      > Connection is Closed message.
      >
      > Our C# instansiates a DB2Connectin object and issues an open against
      > it. Then an executeNonQuery statement to run the SP. It is pretty
      > standard code and works nearly all the time. We think our problem is
      > load related - b/c we only encounter under productin load and more so
      > on our busiest servers.
      >
      > Any help greatly appreciated.
      >
      > Tim Reynolds
      > Verizon Data Services[/color]


        Comment

        • michelles
          #3
          Re: ERROR [40003] [IBM][CLI Driver]

          I don't know if you ever resolved this, but we just had similar problem.
          What version of DB2 are you on? We just upgraded to Db2 V7, with DB2
          connect 8.1 and DB2 client 8.1.2. We also were in the middle of upgrading
          DB2 Clint to Service pack 12. Well anyway, all went back to upgrade to
          DB2 V7 on mainframe. We needed to increate IDACK from 30 to 50, MAXDBAT
          from 64 to 200 and CONDAT from 64 to 200 and CTHREADS from 130 to 200.
          This seemed to fix the issue.



            Comment

            • cwahlmeier@data-tronics.com
              #4
              Re: ERROR [40003] [IBM][CLI Driver]

              michelles wrote:
              I don't know if you ever resolved this, but we just had similar problem.
              What version of DB2 are you on? We just upgraded to Db2 V7, with DB2
              connect 8.1 and DB2 client 8.1.2. We also were in the middle of upgrading
              DB2 Clint to Service pack 12. Well anyway, all went back to upgrade to
              DB2 V7 on mainframe. We needed to increate IDACK from 30 to 50, MAXDBAT
              from 64 to 200 and CONDAT from 64 to 200 and CTHREADS from 130 to 200.
              This seemed to fix the issue.
              We have been getting about 50 -30081's per day every since we switched
              from SNA to TCP/IP four years ago. I have worked two different ETR's
              with IBM with no success. If you figure yours out, I would like to
              hear about it. (We have reviewed every mainframe/gateway/client
              setting known to humanity. No changes have fixed this problem for more
              than a month!) I am going to have -30081 etched on my grave...

              (We run DB2 Client on Windows V8 fp 11, DB2 Connect Enterprise Edition
              on Windows V8 fp 11, and DB2 for z/OS V7.)

              Craig Wahlmeier

                Comment

                Previous template Next
                Working...