Results 1 to 2 of 2
  1. #1
    Join Date
    Oct 2002
    Posts
    5

    Angry Unanswered: HELP - db2diag.log error

    ok we received the following error in our db2diag.log

    2002-11-12-04.51.47.259128 Instance:wstis001 Node:000
    PID:56010(db2tcpcm) Appid:none
    common_communication sqlcctcpconnmgr_child Probe:112
    DIA3202C The TCP/IP call "setsockopt(TCP_NODELAY)" returned an errno="22".

    I have searched everywhere and cannot find out what has caused this.
    Does anyone have any ideals?

    We are running AIX 4.3.3 with DB2 v7.2 (I think) and
    using WebSphere 3.5

    Our DBA is stumped so she has asked for the AIX department to help.
    I'm relatively new with the company and the expert on this is on
    vacation. Anyone have any ideals on where I can look to
    solve this???




    Thanks for your help

  2. #2
    Join Date
    Apr 2002
    Posts
    188

    Re: HELP - db2diag.log error

    Originally posted by manialg
    ok we received the following error in our db2diag.log

    2002-11-12-04.51.47.259128 Instance:wstis001 Node:000
    PID:56010(db2tcpcm) Appid:none
    common_communication sqlcctcpconnmgr_child Probe:112
    DIA3202C The TCP/IP call "setsockopt(TCP_NODELAY)" returned an errno="22".

    I have searched everywhere and cannot find out what has caused this.
    Does anyone have any ideals?

    We are running AIX 4.3.3 with DB2 v7.2 (I think) and
    using WebSphere 3.5

    Our DBA is stumped so she has asked for the AIX department to help.
    I'm relatively new with the company and the expert on this is on
    vacation. Anyone have any ideals on where I can look to
    solve this???




    Thanks for your help
    Hello,
    This may be an AIX related issue with DB2 processes, in house we have
    AIX 4.5 and AIX5.0 with UDB/DB2 7.2 and from time to time we see similar issues with the TCP sockets, in which we can not even connect
    using the net drivers only the CLI/ODBC catalogs.
    Try checking if your db2jstrt can start, if not then in our case
    we have to bring the instance down issue a db2kill (wich is not recommended) and we go the thing back on

    my 2 cents

    marcos oliva

Posting Permissions

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