After restarting DB2 service, the application serv

Question

We have an application on IBM WebSphere Application Server 7.x and it connects to a remote database on z/os DB2 10.x. For annual operation, DB2 shut down and restarted. After starting the database, we first get

com.ibm.websphere.ce.cm.StaleConnectionException

and then we get

The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated this particular request due to unexpected error conditions detected at the target system. ERRORCODE=-4499, SQLSTATE=58009

The connection between WebSphere and DB2 tested by 'test Connection' in WAS datasource. Both systems are up and running but there is no correct connection between them! There was no change in DB2, WAS, and JDBC driver.

Update: The JDBC driver version is 4.15.134, connection properties is IBM WebSphere default setting and the connection is direct to DB2. Another problem later showed that while the connection still has the problem, executing the query directly on z/OS's DB2 gets the same the error. The query consist of a select with a join on two different tables, selecting on each table is ok, but the final query does not work and gets ERRORCODE=-4499, SQLSTATE=58009.

Update 2 The detail of environment is: IBM WebSphere Application Server 7.0.0.45, DB2 10.1, Java version 1.6 SR16 and z/OS 1.13.

This specific query gets the error in all environments, on all application server, z/os SPUFI, database viewer, such as DBeaver.

Any help is greatly appreciated.

Answer 1

If I got you correctly, you complain on inability of the driver to reestablish the database connections after the DB2 for Z/OS restart. If yes, then have you tried to set the corresponding connection properties described at the following link?

Configuration of Sysplex workload balancing and automatic client reroute for Java clients

Answer 2

Finally, we found the solution, ran REORG and RUNSTATS on both tables and on all their partitions, and the error vanished both on the application and SPUFI. I guess something went wrong during restart and tables corrupted. Now everything is ok.