Results 1 to 2 of 2
  1. #1
    Join Date
    Aug 2013
    Posts
    6

    Unanswered: Db2 db2tcp_client_rcvtimeout

    Hello. I have a problem and I'm hoping somebody can help.

    I'm using a scheduled bash script to execute a particularly time consuming piece of SQL. It takes approximately 10 mins to execute. However I always get the following error.

    s
    DB21034E The command was processed as an SQL statement because it was not a
    valid Command Line Processor command. During SQL processing it returned:
    SQL30081N A communication error has been detected. Communication protocol
    being used: "TCP/IP". Communication API being used: "SOCKETS". Location
    where the error was detected: "127.0.0.1". Communication function detecting
    the error: "selectForRecvTimeout". Protocol specific error code(s): "2", "*",
    "*". SQLSTATE=08001


    I did some research and as a result I have tried changing the value of DB2TCP_CLIENT_RCVTIMEOUT to 600 seconds.

    I do this as part of the script and then change it back to 6 which is the current value.


    However according to the logfile my bash script produces I get the timeout after 5 minutes. This appears to happen regardless of the value I set.

    >>>>Log File>>>>>>
    Calculating Stats for 201307
    Fri Aug 2 13:45:40 CEST 2013
    insert into.......(removed)
    During SQL processing it returned:
    SQL30081N A communication error has been detected. Communication protocol
    being used: "TCP/IP". Communication API being used: "SOCKETS". Location
    where the error was detected: "127.0.0.1". Communication function detecting
    the error: "selectForRecvTimeout". Protocol specific error code(s): "2", "*",
    "*". SQLSTATE=08001

    Fri Aug 2 13:50:40 CEST 2013



    I tried executing the piece of sql from CLI without the bash script too and it works whatever the value of the timeout, here it is 6 seconds.

    $db2set;date;insert....;date
    DB2TCP_CLIENT_RCVTIMEOUT=6
    Fri Aug 2 16:40:39 CEST 2013
    insert into .......
    Fri Aug 2 16:48:44 CEST 2013



    I'm not sure where to go with this. Any suggestions welcome.

  2. #2
    Join Date
    Aug 2013
    Posts
    6
    It was to do with bash scripts. It's solved now.

Posting Permissions

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