Results 1 to 5 of 5

Thread: dba

  1. #1
    Join Date
    Jun 2007
    Posts
    12

    Unanswered: dba

    hi all. anyone seen this lately?

    SQL0952N Processing was cancelled due to an interrupt SQLSTATE=57014

    details -- unix 5.3 OS; udb version 9.5 fp 4 for the database server; udb version 9.5 fp4 on the client machine as well. querytimeoutinterval=0 in the db2cli.ini

    very small database, no major processing on the instance or the server at the time of the interrupt. nothing in the diag log.

    ideas?????

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    The client sent some sort of an interrupt. If you open a command window, connect to a database, then issue a query, then press ctrl-C before the query finishes, you will get this.

    Andy

  3. #3
    Join Date
    Jun 2007
    Posts
    12
    wish it were so............its a batch process, no one actually running it, folks working off shore getting hit some times, local app server getting hit but no one manually hitting the control-c combo............

  4. #4
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Doesn't matter whether someone hits ctl-c. If there was any kind of network interruption or your putty (ssh) session, then it can happen. If you were running the batch job as a cron task, or as a background job (nohup xxxxxxxxxx &) on the database server, then that would be a different story, but if you run the batch job remotely via a ssh session, then a problem with the network can cause the job interrupt.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  5. #5
    Join Date
    Jun 2007
    Posts
    12
    right -- we were looking at that but this is a large shared server -- 20 instances on the box. none of the others experiencing the same thing during the same time period. even if all did not time out you'd think that one or two of the other app servers residing on the same network would have the same experience.
    we're thinking that perhaps the querytimeoutinterval=0 is not really working. someone said they'd seen that in windows before and a registry setting has to be made
    anyone know about that?

Posting Permissions

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