Results 1 to 7 of 7
  1. #1
    Join Date
    Feb 2009
    Posts
    5

    Unanswered: Error while cataloging remote database

    I have cataloged remote database into my DB2(V8.2) server. It was cataloged successfully but when I try to connect to that database (db2 "connect to mydb") I see this error,

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

    Can any one please help me on this.

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    Can you post the catalog commands for the db and node?

    Andy

  3. #3
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Make sure the instance is running and the database server on the is accessible at the specified port (e.g. the firewall is not blocking traffic to that port).
    ---
    "It does not work" is not a valid problem statement.

  4. #4
    Join Date
    Feb 2009
    Posts
    5
    Hi ARWinner

    I have used the following catalog commands for node and db,

    DB2 "catalog tcpip node remotenode remote 172.17.5.24 server 60000"

    DB2 "catalog db mydb at node remotenode"

    thanks,
    Pradeep

  5. #5
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Check if:
    - you can telnet to the server using this port (telnet <host> <port>)
    - db2comm and svcename is set

    For more info, please check the following technote:
    IBM - SQL30081N TCPIP communication errors

  6. #6
    Join Date
    Feb 2009
    Posts
    1
    You have to catalog TCPIP node, DCS database and remote database.
    Try these commands in order.

    DB2 CATALOG TCPIP NODE nodename REMOTE xxx.xxx.xxx.xxx
    DB2 CATALOG DCS DATABASE host name
    DB2 CATALOG DATABASE AP3DDBM1
    Terminate

    List DCS directory,node directory and DCS directory to make sure that catalog is successful.

    Thanks
    Prasad Vankina

  7. #7
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    dcs db is only needed if connecting from luw to mainframe z/os or vm/vse
    what is source and what is target as o/s
    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 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified
    http://www.infocura.be

Posting Permissions

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