IZ65855: DEADLOCKLOSERDATAACCESSEXCEPTION WITH WSRR AND DB2
Closed as program error.
When using the WSRR UI, you see "A problem occurred executing the query [query syntax]" followed by GSR0089E and GSR0597E with a reason of org.springframework.dao.DeadlockLoserDataAccessException Once this has happened, subsequent transactions are likely to fail with SQLException error code 4497 and SQLState null.
The way that WSRR interacted with DB2 meant that in some high-throughput environments you might see DeadlockLoserDataAccessException. This fix supplies a runtime fix, and a change to the database configuration parameters. The database configuration parameters will only be applied if you run a new WSRR install. If you are applying this fix to an existing WSRR install, you should set the following parameters directly against DB2: db2set DB2_SKIPINSERTED=YES db2set DB2_SKIPDELETED=YES Note that other databases (for example Oracle) are not affected by this fix.
Apply this fix to reduce the possibility of database deadlock exceptions for DB2. If you are applying an iFix or a fixpack, ensure that you set the DB2SET commands manually to your existing database. It is expected to be available in 126.96.36.199.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels