db2 listener

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

    db2 listener

    Hi,

    I have problem to connect to db server from app server. The error is

    SQL30081N A communication error has been detected. Communication
    protocol
    being used: "TCP/IP". Communication API being used: "SOCKETS".
    Location
    where the error was detected: "192.168.59.72" . Communication function
    detecting the error: "connect". Protocol specific error code(s): "79",
    "*",
    "*". SQLSTATE=08001

    The db2 version is 8.2.3. It's on AIX 5.3. The port numbers for the db2
    instance on the db server are 60004 to 60007. I checked the listener by


    netstat -an

    and it doesn't show any of the port number been listening on.

    Any idea about this issue. Thanks.

    Tags: None
    • Challenge
      #2
      Re: db2 listener

      It's solved though I don't know why. The only thing I did is to update
      the 'SVCENAME' to a different port number and then update it back to
      60004 (which doesn't work before). And it works. Any idea why? Thanks.

      Challenge wrote:
      Hi,
      >
      I have problem to connect to db server from app server. The error is
      >
      SQL30081N A communication error has been detected. Communication
      protocol
      being used: "TCP/IP". Communication API being used: "SOCKETS".
      Location
      where the error was detected: "192.168.59.72" . Communication function
      detecting the error: "connect". Protocol specific error code(s): "79",
      "*",
      "*". SQLSTATE=08001
      >
      The db2 version is 8.2.3. It's on AIX 5.3. The port numbers for the db2
      instance on the db server are 60004 to 60007. I checked the listener by
      >
      >
      netstat -an
      >
      and it doesn't show any of the port number been listening on.
      >
      Any idea about this issue. Thanks.

        Comment

        • Ian
          #3
          Re: db2 listener

          Challenge wrote:
          Hi,
          >
          I have problem to connect to db server from app server. The error is
          >
          SQL30081N A communication error has been detected. Communication
          protocol
          being used: "TCP/IP". Communication API being used: "SOCKETS".
          Location
          where the error was detected: "192.168.59.72" . Communication function
          detecting the error: "connect". Protocol specific error code(s): "79",
          "*",
          "*". SQLSTATE=08001
          >
          The db2 version is 8.2.3. It's on AIX 5.3. The port numbers for the db2
          instance on the db server are 60004 to 60007. I checked the listener by
          >
          >
          netstat -an
          >
          and it doesn't show any of the port number been listening on.
          >
          Any idea about this issue. Thanks.
          >
          Chances are you're using the incorrect port number. In /etc/services
          you will typically see 1 single port and then a range reserved for an
          instance.

          The single port (usually close to 50000, default name is db2cINSTANCE
          where INSTANCE is replaced by the name of your instance) is generally
          used for TCPIP listener for client communication (i.e. SVCENAME).

          The range (starting above 60000 by default, with names DB2_INSTANCE,
          DB2_INSTANCE_1, DB2_INSTANCE_2, DB2_INSTANCE_EN D, again where INSTANCE
          is replaced with the real name of your instance) are special ports
          reserved for the fast communications manager, which is used for inter-
          partition communication if you have DPF.

          You should _not_ be using any port between DB2_INSTANCE and
          DB2_INSTANCE_EN D for your TCPIP listener (i.e. SVCENAME), even if you
          aren't using DPF.

            Comment

            • Challenge
              #4
              Re: db2 listener

              Hi Ian,

              I think it's not the reason. 60004 to 60007 were assigned by the server
              automatically when the db2 instance was created. 60004 is the
              DB2_db2instance in /etc/services. I guess some miscommunicatio n
              happened. Anyway it's solved. Thanks.

              Ian wrote:
              Challenge wrote:
              Hi,

              I have problem to connect to db server from app server. The error is

              SQL30081N A communication error has been detected. Communication
              protocol
              being used: "TCP/IP". Communication API being used: "SOCKETS".
              Location
              where the error was detected: "192.168.59.72" . Communication function
              detecting the error: "connect". Protocol specific error code(s): "79",
              "*",
              "*". SQLSTATE=08001

              The db2 version is 8.2.3. It's on AIX 5.3. The port numbers for the db2
              instance on the db server are 60004 to 60007. I checked the listener by


              netstat -an

              and it doesn't show any of the port number been listening on.

              Any idea about this issue. Thanks.
              >
              Chances are you're using the incorrect port number. In /etc/services
              you will typically see 1 single port and then a range reserved for an
              instance.
              >
              The single port (usually close to 50000, default name is db2cINSTANCE
              where INSTANCE is replaced by the name of your instance) is generally
              used for TCPIP listener for client communication (i.e. SVCENAME).
              >
              The range (starting above 60000 by default, with names DB2_INSTANCE,
              DB2_INSTANCE_1, DB2_INSTANCE_2, DB2_INSTANCE_EN D, again where INSTANCE
              is replaced with the real name of your instance) are special ports
              reserved for the fast communications manager, which is used for inter-
              partition communication if you have DPF.
              >
              You should _not_ be using any port between DB2_INSTANCE and
              DB2_INSTANCE_EN D for your TCPIP listener (i.e. SVCENAME), even if you
              aren't using DPF.

                Comment

                • Ian
                  #5
                  Re: db2 listener

                  Challenge wrote:
                  Hi Ian,
                  >
                  I think it's not the reason. 60004 to 60007 were assigned by the server
                  automatically when the db2 instance was created. 60004 is the
                  DB2_db2instance in /etc/services. I guess some miscommunicatio n
                  happened. Anyway it's solved. Thanks.
                  >

                  Please don't top post (above other replies).

                  In any case - as I said you should NOT use DB2_db2instance for SVCENAME.
                  The ports 60004 - 60007 are intended for use by the Fast Communications
                  Manager (FCM), not for client communication.

                  Even if you aren't using DPF, you should avoid using these ports as it
                  is bad practice and can lead to confusion.

                    Comment

                    Previous template Next
                    Working...