DB2 - Problem description
Problem IT31612 | Status: Closed |
PIGGYBACK COMMANDS ARE NOT REPLAYED IF FAILURE HAPPENS DURING FIRST SQL EXECUTION IN CASE OF NON-SEAMLESS FAILOVER | |
product: | |
DB2 CONNECT / DB2CONNCT / B10 - DB2 | |
Problem description: | |
T4 Java application throwing Error : com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-440, SQLSTATE=42884 ( resource not found) when piggyback commands fails to replay due to first sql non seamless execution failure. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * 1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Piggyback commands are not replayed if failure happens * * during first sql execution in case of non-seamless failover * * The issue been fixed in v11.1m4fp4 (4.25) and 11.5m4fp0 ( * * 4.27 ) * **************************************************************** | |
Local Fix: | |
NA | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * 1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Piggyback commands are not replayed if failure happens * * during first sql execution in case of non-seamless failover * * The issue been fixed in v11.1m4fp4 (4.25) and 11.5m4fp0 ( * * 4.27 ) * **************************************************************** | |
Comment | |
T4 Java application throwing Error : com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-440, SQLSTATE=42884 ( resource not found) when piggyback commands fails to replay due to first sql non seamless execution failure. The issue been fixed in v11.1m4fp4 (4.25) and 11.5m4fp0 ( 4.27 ) | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.01.2020 22.05.2020 22.05.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |