Results 1 to 3 of 3
  1. #1
    Join Date
    Apr 2009

    Unanswered: Connecting to another db2 server

    Good day.

    Our application is currently connected to a Db2 WSE ver. 9.5/ Windows 2008 Enterprise server. Our problem is when we are trying to connect to the other server. It runs in Windows server 64 bit Standard edition / Db2 WSE ver 9.5 which houses our SAP DEV.

    we are encountering this error

    db2 => connect to DEV user devadm
    Enter current password for devadm:
    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: "recv". Protocol specific error code(s): "*", "*", "0".

    I have catalog the node and database already.. but when i am accessing the server in my workstation i was having this error.

    Thank you in advance for your help..

    Romer Roma

  2. #2
    Join Date
    Apr 2006
    Provided Answers: 11
    are you able to connect from any station ?
    have you checked if instance is listening on correct port
    is db2comm enabled
    is catalog been done correctly
    many possibilities
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5-V11 Fundamentals- DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified

  3. #3
    Join Date
    Apr 2009
    I was able to connect it already to the other server (SAp server)..

    thank you very much..

Posting Permissions

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