IC84655: ODBC WRAPPER DOES NOT ROLLBACK CURRENT TRANSACTION WHEN IT GETS A GENERAL CONNECTION ERROR
Fixes are available
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
Closed as program error.
When ODBC wrapper gets a general connection error like 08001, 08003 and 08S01, it just reports -30080 error without rolling back the current transaction. So, when the application tries to close the current connection to Federation server, -4471 error would be returned since the current transaction is still in progress on the connection.
no local fix or workaround
User affected: Users who use ODBC wrapper of in InfoSphere Federation Server Problem description and summay: See error description
Problem was fistly fixed in Version 10, FixPak 1. This fix should be applied on the federation Server.
Reported component name
DB2 FOR LUW
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
DB2 FOR LUW
Fixed component ID
Applicable component levels
Translate this page: