IZ44579: SQL0805 RECEIVED EVEN AFTER FREEING STATEMENT HANDLES BEFORE.

DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• When a program tries to open a lot of statement handles (up to
  the limit which is indicated by an SQL0805), and
  then closes some handles and again opens a new statement handle,
  then a SQL0805 error is received, even
  though this should not happen (because some handles were closed
  in between, at least same number of handles should be allowed to
  be opened as they were closed earlier)
  
  
  This behaviour is observed in universal (JCC T2 and T4) drivers
  while legacy drivers work as expected i.e. the application can
  create again as many statements as the cli-packages allow.
  
  This problem is observed on all versions i.e. DB2 V8.1, V8.2,
  V9.1, V9.5 using Universal Driver (JCC).
  

Local fix

• If the application really needs to use these many statements
  concurrently, then this -805 suggests that
  there are no more packages to use and user should bind more
  packages. Binding more packages will allow  using more than
  the earlier number of statements.
  
  Furthermore, if the application doesn't really need to use these
  many statements concurrently, it's a good practice to close the
  statement right after using it then the number of statement
  won't reach the limitation.
  

Problem summary

• When a program tries to open a lot of statement handles (up to
  the limit which is indicated by an SQL0805), and
  then closes some handles and again opens a new statement handle,
  then a SQL0805 error is received, even
  though this should not happen (because some handles were closed
  in between, at least same number of handles should be allowed to
  be opened as they were closed earlier)
  
  
  This behaviour is observed in universal (JCC T2 and T4) drivers
  while legacy drivers work as expected i.e. the application can
  create again as many statements as the cli-packages allow.
  
  This problem is observed on all versions i.e. DB2 V8.1, V8.2,
  V9.1, V9.5 using Universal Driver (JCC).
  

Problem conclusion

• Problem was first fixed in Version v9.1 Fix Pack 7
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IZ19517

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 CEE AIX

• Fixed component ID

  5765F3000

Applicable component levels

• R910 PSN

     UP