|
Problem IC96684
|
Status: Closed |
BATCH EXECUTION INTRODUCES INTERNAL COMMIT (EVEN WITH AUTOCOMMIT OFF) |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When using CLP commands even with AUTOCOMMIT OFF combined with
batch execution, the batch run will introduce an internal commit
which might result in unexpected behaviour as anything that was
executed previous to the batch will commit implicitly regardless
of the setting of autocommit.
Simple test case:
db2 connect to sample
cat t_maria
create table AAAAABBBBB(c1 int);
1. db2 +c "create table AAAAAA(c1 int)"
2. db2 +c -stf t_maria
3. db2 rollback
NONE of the tables should exist on the system after the
rollback, but the execution with the batch file is doing a
commit implicitly, so the first table creation gets committed.
db2 list tables for all | grep -i AA
AAAAAA MARIAJ T
2013-08-15-12.11.07.819349 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description. This problem was introduced in DB2 *
* version 9.5 and Fix Pack 8, DB2 version 9.7 and Fix Pack 5 *
* and DB2 version 10.1 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 and Fix Pack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2013
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
