We are running the following:

AIX 5.3
WAS 6.0, WAS ND 6.0.2.17, WCC 6.5
DB2 v8.1.1.160 (fix pack 18)

We get the following error:
############
Error code:
200000100

Error Message:
Reading an extension Person failed

Throwable Message:
java.lang.Exception: Exception while retrieving Alert Objects com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -805, SQLSTATE: 51002, SQLERRMC: NULLID.SYSLN21E 0X5359534C564C3031

com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -805, SQLSTATE: 51002, SQLERRMC: NULLID.SYSLN21E 0X5359534C564C3031

We have:
1. reviewed all application code and confirmed all open statements have a corresponding close statement
2. our configuration for number of pkgs is at the maximum
3. been advised this is fixed in v9.2 (upgrading is not an option at this point in time)

Any ideas?

been advised this is fixed in v9.2 (????
this is not a problem : please read the doc and find the sql code .....
-805 just means : package missing
have a look at doc and execute the bind for needed db2 packages
IBM DB2 9.5 Information Center for Linux, UNIX, and Windows
this is common for all versions

Been advised its fixed in 9.2, should have been 9.1

known defect IZ44579

https://www-304.ibm.com/support/docv...id=swg1IZ44579

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).

NOTE: I am not a DBA, I am primarily middleware support, can you provide more info about this 'bind' reference you have made.

for users to be able to work with db2 some binds are needed - loading packages in db
typical : db2ubind.lst db2cli.lst db2schema.bnd
the lst files are just lists keeping bind files names
so looking at the doc : you will see
cd sqllib/bnd
connect to db
db2 bind db2schema.bnd blocking all grant public sqlerror continue or
db2 bind @db2cli.lst ......... @ needed if list

DBAs have advised they have been through this steps already and verified.

This has made no difference to the issue.

Some more information provided by my DBAs,

We have ran this command 'db2 bind @db2cli.lst blocking all sqlerror continue grant public CLIPKG 30' but we still ran out of packages
The reason appears to be caused by the Universal driver not closing statement handles.

Related technote:
https://www-304.ibm.com/support/docv...id=swg21366855

As previously advised, we have verified the code is closing statements and connections.

We have also found technotes indicating this is a known bug with DB2 version 8. As we are not in a position to upgrade to v9.2 (where the fix is), I would like to find out if anyone knows of any UDB driver fixes available for v8 (AIX).

Either your application is not closing transactions properly or you don't commit often enough. I don't care how many code reviews you say you have done.

Rebinding to allow more packages is like giving more drugs to a drug addict. It only makes things worse.

I agree with Marcus. Your application does not properly close all statements or it runs too much stuff in parallel. Maybe some threads run into a wait/deadlock situation while having statements opened?

p.s: V8 is out of service for years now.