DB2 - Problem description
Problem IC91730 | Status: Closed |
DTC:XA:NOT SUPPORTED ISOLATIONLEVEL IN ADO.NET SCENARIO | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
The issue can occur when the server is being abnormally terminated. For example if an iterative db2stop force and db2start is done or the DB2 process is manually killed. Otherwise the transaction should go through fine. The error message looks like below: 2012-11-30-8.19.19.214 <PID:5236> <TID:3> <Commands.ConnectionFirst> Not supported isolationlevel - RepeatableRead Source IBM.Data.DB2 Error occurred at IBM.Data.DB2.DB2Connection.SetIsolationLevel(IsolationLevel isolevel, IntPtr hDbc) at IBM.Data.DB2.DB2ConnPool.Open(DB2Connection connection, String& szConnectionString, DB2ConnSettings& ppSettings, Object& ppConn) at IBM.Data.DB2.DB2Connection.Open() at BComDL.BComDL.Commands.ConnectionFirst(ConfigSettings Configuration) in F:\ajimnair\BCom_v97fp6_dev\BCom\BComDL\Commands.vb:line 1407. InnerExceptions: 2012-11-30-8.19.19.230 <PID:5236> <TID:3> <BComDL.BaseDatabase.GetServerVersion> Failed to connect to DB GWDB3. SQLSTATE= SQLCODE=. Error occurred at BComDL.BComDL.BaseDatabase.GetServerVersion(String& StrServerVersion) in F:\ajimnair\BCom_v97fp6_dev\BCom\BComDL\BaseDatabase.vb:line 313 2012-11-30-8.19.19.230 <PID:5236> <TID:3> <BCom.Engine.Start> Fatal error encountered when OpenBranch.ERROR: <BranchCOM> Failed to get server release information for participating DB GWDB3 SQLSTATE= SQLCODE= | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * .Net provider users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * upgrade to DB2 Client v10.1 fp3 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
first fixed in db2_v101fp3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.04.2013 04.11.2013 04.11.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |