Results 1 to 8 of 8
  1. #1
    Join Date
    Jul 2003
    Location
    Hamburg, Germany
    Posts
    31

    Exclamation Unanswered: ***** SQL30081N ..."recv" *****

    Hello,

    while I'm (Client is on windows XP) connecting to my DB-Server (Solaris), I get the error message after 10 minutes:

    ------------------------------------------------
    SQL30082N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "SERVER-IP". Communication function detecting the error: "recv". Protocol specific error code(s): "*", "*", "0". SQLSTATE=08001
    ------------------------------------------------

    Any Ideas????

    Thanks in advance
    Savas
    Last edited by savas; 09-05-03 at 06:02.

  2. #2
    Join Date
    Jan 2003
    Posts
    1,605
    Hi,

    Check:
    1. username and password of Solaris server,
    2. TCP/IP - network between client and server (check if communication works).
    3. Check if Solaris server and database is up and running

    Hope this helps,
    Grofaty

  3. #3
    Join Date
    Jul 2003
    Location
    Hamburg, Germany
    Posts
    31

    start sever

    Hello,

    do you mean "db2start"? Or something else?

    Check if Solaris server and database is up and running
    Thanks
    Savas

  4. #4
    Join Date
    Sep 2003
    Posts
    4
    1. You got to make sure all instances in your Solaris are running correctly. (Test it using UNIX command shell first)

    2. make sure that the IP and Port no. are correct in your client side.

    3. Then you could try, supposing you create your database node using configuration assistance. Normally the security option is default to "Use Authentication value in server's DBM configuration", let's change it to use "Server Authentication (Server)" again and test again.

    Let's see the result. (I encountered this error in some XP machines for some DB2v8.1 client with some earlier fixpaks)

  5. #5
    Join Date
    Jul 2003
    Location
    Hamburg, Germany
    Posts
    31

    not better

    Hi,

    I tried it, but that's not better
    I don't know what can I do otherwise?!

    I'm reading so many messages in several forum, and they have nearly the same problem!? Is that a common problem?

    Please help!


    3. Then you could try, supposing you create your database node using configuration assistance. Normally the security option is default to "Use Authentication value in server's DBM configuration", let's change it to use "Server Authentication (Server)" again and test again.

  6. #6
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1

    Re: not better

    Originally posted by savas
    Hi,

    I tried it, but that's not better
    I don't know what can I do otherwise?!

    I'm reading so many messages in several forum, and they have nearly the same problem!? Is that a common problem?

    Please help!
    IBM have a problem determination tutorial on their web site

    http://www-3.ibm.com/cgi-bin/db2www/...l_conn.d2w/toc

    You may want to have a look at it.

    Nick
    ---
    "It does not work" is not a valid problem statement.

  7. #7
    Join Date
    Jul 2003
    Location
    Hamburg, Germany
    Posts
    31

    db2diag.log

    Hi n_i,

    the tutorial is very good

    I think if someone won't find there the problem, then I believe he/she won't find the solution perhaps anywhere?!

    I write this, because I found something very interesting! I followede the instructions...

    Create a backup copy of the db2diag.log, then clear the contents of the original db2diag.log file. Raise the diagnostic level to 4, then stop and restart this DB2 instance, via the following commands:

    db2 update dbm cfg using diaglevel 4
    db2stop
    db2start


    Verify that the db2diag.log shows that the listeners for the specific protocol which we are interested have been started successfully.

    2002-11-24-01.09.46.282346 Instance:lcawley Node:000
    PID:72732(db2tcpcm) Appid:none
    common_communication sqlcctcpconnmgr_child Probe:66
    DIA3004I Normal shutdown requested for "TCPIP" protocol support.

    2002-11-24-01.09.46.784304 Instance:lcawley Node:000
    PID:16744(db2stop2) Appid:none
    base_sys_utilities stopdbm Probe:911

    2002-11-24-01.09.50.606535 Instance:lcawley Node:000
    PID:23694(db2sysc) Appid:none
    common_communication sqlcctcpconnmgr Probe:160
    DIA3218I "1" TCP/IP connection manager(s) was/were successfully started.

    2002-11-24-01.09.50.624615 Instance:lcawley Node:000
    PID:23694(db2sysc) Appid:none
    common_communication sqlcctcp_start_listen Probe:80
    DIA3000I "TCPIP" protocol support was successfully started.

    2002-11-24-01.09.51.652177 Instance:lcawley Node:000
    PID:16748(db2star2) Appid:none
    base_sys_utilities startdbm Probe:911
    But my db2diag.log looks like...

    2003-09-10-10.00.22.117125 Instance:db2inst1 Node:000
    PID:29856(db2tcpcm 0) TID:1 Appid:none
    common communication sqlcctcpconnmgr_child Probe:66

    DIA3004I Normal shutdown requested for "TCPIP" protocol support.

    2003-09-10-10.00.22.145082 Instance:db2inst1 Node:000
    PID:29857(db2tcpcm 0) TID:1 Appid:none
    common communication sqlcctcpconnmgr_child Probe:66

    DIA3004I Normal shutdown requested for "TCPIP" protocol support.

    2003-09-10-10.00.23.216423 Instance:db2inst1 Node:000
    PID:598(db2stop2) TID:1 Appid:none
    base sys utilities stopdbm Probe:911

    ADM7514W Database manager has stopped.

    2003-09-10-10.00.23.376334 Instance:db2inst1 Node:000
    PID:596(db2stop) TID:1 Appid:none
    oper system services sqlofica Probe:10

    ALERT :997
    PID:596 TID:1 Node:000 Title: Not available!
    5351 4c43 4120 2020 0000 0088 ffff fbd8 SQLCA ....ÿÿûØ
    0000 2020 2020 2020 2020 2020 2020 2020 ..
    2020 2020 2020 2020 2020 2020 2020 2020
    2020 2020 2020 2020 2020 2020 2020 2020
    2020 2020 2020 2020 2020 2020 2020 2020
    2020 2020 2020 2020 5351 4c45 5046 494e SQLEPFIN
    0000 0000 0000 0000 0000 0000 0000 0000 ................
    0000 0000 0000 0000 2020 2020 2020 2020 ........
    2020 2020 2020 2020

    2003-09-10-10.00.27.160780 Instance:db2inst1 Node:000
    PID:603(db2star2) TID:1 Appid:none
    base sys utilities LicCheckProcessors Probe:20

    SQL8017W Die Anzahl Prozessoren auf dieser Maschine überschreitet die
    definierte zulässige Anzahl von "1" für das Produkt "DB2 Enterprise Server
    Edition". Die Anzahl Prozessoren auf dieser Maschine beträgt "4". Sie sollten
    zusätzliche Prozessorlizenzen von Ihrem IBM Ansprechpartner oder
    Vertragshändler erwerben und Ihre Lizenz mit Hilfe der Lizenzzentrale oder des
    Befehlszeilenprogramms db2licm aktualisieren. Weitere Informationen zur
    Aktualisierung von Prozessorlizenzen finden Sie im Handbuch 'Einstieg' für
    Ihre Plattform. Weitere Informationen zum Dienstprogramm db2licm finden Sie
    im Handbuch 'DB2 Command Reference'.


    2003-09-10-10.00.27.264827 Instance:db2inst1 Node:000
    PID:605(db2wdog 0) TID:1 Appid:none
    base sys utilities sqleReadEvlogCtlInfo Probe:20

    Corrupted or empty event log file, will recreate. Bytes read = 0000 0000 ....

    2003-09-10-10.00.31.551579 Instance:db2inst1 Node:000
    PID:605(db2wdog 0) TID:1 Appid:none
    oper system services sqloRunInstance Probe:98

    DiagData
    0000 0001 ....

    2003-09-10-10.00.31.554759 Instance:db2inst1 Node:000
    PID:606(db2sysc 0) TID:1 Appid:none
    oper system services sqlockpw_daemon_init Probe:20

    effective userid not root:0000 006c ...l

    2003-09-10-10.00.32.125328 Instance:db2inst1 Node:000
    PID:606(db2sysc 0) TID:1 Appid:none
    oper system services sqloRunInstance Probe:165

    DiagData
    870f 0022 ..."

    2003-09-10-10.00.32.585644 Instance:db2inst1 Node:000
    PID:606(db2sysc 0) TID:1 Appid:none
    common communication sqlcctcpconnmgr Probe:160

    DIA3218I "2" TCP/IP connection manager(s) was/were successfully started.

    2003-09-10-10.00.32.622206 Instance:db2inst1 Node:000
    PID:606(db2sysc 0) TID:1 Appid:none
    common communication sqlcctcp_start_listen Probe:80

    DIA3000I "TCPIP" protocol support was successfully started.

    2003-09-10-10.00.33.820902 Instance:db2inst1 Node:000
    PID:603(db2star2) TID:1 Appid:none
    base sys utilities startdbm Probe:911

    ADM7513W Database manager has started.

    2003-09-10-10.00.33.922804 Instance:db2inst1 Node:000
    PID:601(db2start) TID:1 Appid:none
    oper system services sqlofica Probe:10

    ALERT :997
    PID:601 TID:1 Node:000 Title: Not available!
    5351 4c43 4120 2020 0000 0088 ffff fbd9 SQLCA ....ÿÿûÙ
    0000 2020 2020 2020 2020 2020 2020 2020 ..
    2020 2020 2020 2020 2020 2020 2020 2020
    2020 2020 2020 2020 2020 2020 2020 2020
    2020 2020 2020 2020 2020 2020 2020 2020
    2020 2020 2020 2020 5351 4c45 5046 494e SQLEPFIN
    0000 0000 0000 0000 0000 0000 0000 0000 ................
    0000 0000 0000 0000 2020 2020 2020 2020 ........
    2020 2020 2020 2020
    In the log there is something about license? (SQL8017W)
    Is that a problem?!

    Thanks
    Savas

  8. #8
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: db2diag.log

    Savas ... It is unfortunate that you get the TCP/IP problem ...

    I do not think it has anything to do with licensing issue ..

    My suggestion will be to get you Network Admin or Solaris admin to get involved ... they may probably be able to help you out ...

    Good Luck

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

Posting Permissions

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