Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2012

    Unanswered: SQLSTATE 805 after certain numbers of statements


    we are running a Spring/JPA application which does multithreaded data processing on tomcat using DB2. If we are running large jobs containing a lot of statements the database raises a SQLSTATE 805 after ~1150 statements.

    if we perform a entityEanager.flush() manually the problem does not appear.

    how can this happen? is there a certain limitation in DB2 for statements in parallel sessions?

    Notice : we run DB2 on z/os

    Thanks in advance,

  2. #2
    Join Date
    Apr 2012
    Provided Answers: 17
    Find out (from the DBA, or from the detailed messages in the log files) *which* package is not found or not bound... You have to have that as a starting point...

    Is the package the same for every occurrence of the problem, or does the package-name vary?

  3. #3
    Join Date
    Jun 2003
    Toronto, Canada
    Provided Answers: 1

  4. #4
    Join Date
    Jan 2007
    Jena, Germany
    If the error is cursor-related, check that you close your cursors properly. For example, Java/JDBC has a very unfortunate default setting to use WITH HOLD cursors, which are not closed upon COMMIT. (And that default is used because auto-commit is another such unfortunate default.)
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

Posting Permissions

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