|
Problem IC62706
|
Status: Closed |
ERROR SQL30020N WHEN A SESSION WHICH WAS ENLISTED TO AN ABORTED TRANSACTION IS ENLISTED AGAIN |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
Error SQL30020N when enlisting a session which was enlisted
before in a transcation which got "Long transaction aborted.
(-12204 RSAM error: Long transaction detected.)".
The error messages returned by the applications are:
For first transaction:
ERROR [IX000] [IBM][IDS/UNIX64] Long transaction aborted.
(-12204 RSAM error: Long transaction detected.)
For next transaction which uses the same connection:
ERROR [58009] [IBM] SQL30020N Execution of the command or SQL
statement failed because of a syntax error in the communication
data stream that will affect the successful execution of
subsequent commands and SQL statements: Reason Code
"0x124C"("0108")"". SQLSTATE=58009 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* The Data Server Driver reports error SQL30020N when *
* enlisting a session which was enlisted before in a *
* transcation which got "Long transaction aborted. *
* *
* The error messages returned by the applications are: *
* *
* For first transaction: *
* *
* ERROR [IX000] [IBM][IDS/UNIX64] Long transaction aborted. *
* *
* (-12204 RSAM error: Long transaction detected.) *
* *
* *
* For next transaction which uses the same connection: *
* *
* ERROR [58009] [IBM] SQL30020N Execution of the command or *
* SQL *
* statement failed because of a syntax error in the *
* communication *
* data stream that will affect the successful execution of *
* *
* subsequent commands and SQL statements: Reason Code *
* *
* "0x124C"("0108")"". SQLSTATE=58009 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to IBM Data Server Provider for .Net 9.7 Fix Pack 1 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 1
This fix should be applied on the client. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.08.2009
04.01.2010
04.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
