Results 1 to 13 of 13
  1. #1
    Join Date
    Mar 2009
    Posts
    11

    Unanswered: Facing problem while cataloging database

    Hi ,

    I'm newbie in DB2 Administration, I'm trying to do database cataloging. I'm working with DB2 V8.2 on Linux V4.
    These are the steps that I have followed to catalog :

    1.db2 catalog tcpip node node1 remote xxx.xxx.xxx.xxx server <sname>

    2. db2 catalog database <database> at node1

    3. db2 connect to <database> user <user> using <password>

    This the error that I'm facing on console

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


    This is error that I get on db2diag.log

    FUNCTION: DB2 UDB, common communication, sqlcctcpconnr, probe:110
    MESSAGE : DIA3202C The TCP/IP call "connect" returned an errno="111".


    Can anyone tell me where I'm going wrong and What I have to do to fix it. Thank you.

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    On step 1, what did you supply for <sname>?

    Andy

  3. #3
    Join Date
    May 2007
    Location
    somewhere in dbforums
    Posts
    221
    Go to the remote computer and check whether the communication protocol is set to TCP/IP

    Execute the following command
    Code:
    db2set -all
    In the list check the value of
    Code:
    DB2COMM
    and see whther it has been set to
    Code:
    TCPIP
    .
    IBM Certified Database Associate, DB2 9 for LUW

  4. #4
    Join Date
    Mar 2009
    Posts
    11
    Hi Andy,
    On step 1, In the <sname> I have supplied service_name of remote system.


    Hi Nick,
    I have gone to remote computer and checked the communication protocol, it is set to TCP/IP

    First of thanks for your replies. But still I'm unable to catalog. Please send your valuable replies. Thankyou.

  5. #5
    Join Date
    Jan 2003
    Posts
    1,605
    Hi,
    111 error means timeout. Did you check firewall settings on server and also on client?
    Regards

  6. #6
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by asish2a
    On step 1, In the <sname> I have supplied service_name of remote system.
    So, how does the client know the contents of /etc/services on the remote system? Unless the same entry exists in /etc/services on the client, use the port number instead.
    ---
    "It does not work" is not a valid problem statement.

  7. #7
    Join Date
    Mar 2009
    Posts
    11
    Hi n_i,

    I have checked by providing port number but still I face the same error.

  8. #8
    Join Date
    Mar 2009
    Posts
    11
    Hi grofaty,

    I have checked firewall settings on server and client. I have gone through the command /usr/sbin/lokkit in my root and checked it. Its all fine. Do I need to have any changes on iptables ?

  9. #9
    Join Date
    Feb 2009
    Posts
    14
    Try to add this to the file db2cli.ini

    [COMMON]
    QUERYTIMEOUTINTERVAL=0

    Maybe it's help.
    Best regrads,
    Danny Utro.

  10. #10
    Join Date
    Mar 2009
    Posts
    11
    Hi Utro,

    I added the content

    [COMMON]
    QUERYTIMEOUTINTERVAL=0

    to db2cli.ini on server and client, but still I'm facing the same error.

  11. #11
    Join Date
    Feb 2009
    Posts
    14
    Does you stop the dbm after setting this parameter? If not - try this (on server).
    db2 force applications all
    db2 terminate
    db2stop
    db2start
    Best regrads,
    Danny Utro.

  12. #12
    Join Date
    Mar 2009
    Posts
    11
    Hi Utro,

    Its working, thankyou thankyou very much.

  13. #13
    Join Date
    Feb 2009
    Posts
    14
    You are welcome!
    Best regrads,
    Danny Utro.

Posting Permissions

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