|
Problem IT05124
|
Status: Closed |
DB2BATCH HAS ITS DEFAULT ISOLATION LEVEL AS RR WHICH MAY CAUSE PERFORMANCE ISSUES/LOCKS ON PRODUCTION |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When no option for the isolation level is used when running
db2batch, RR (Repeatable Read) is being used as its default
isolation. This may cause performance impact on running
production systems.
Ex:
db2batch -d <dbname> -f <sql_file> -o r 1 p 5 e 2 -i complete -r
<output_file>
This APAR is to change the default isolation level of db2batch
to UR. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Users on DB2 v10.5 FP6 and earlier *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.5 FP7 *
**************************************************************** |
| Local Fix: |
As a local fix, specify -iso option of db2batch:
db2batch -d <dbname> -f <sql_file> -o r 1 p 5 e 2 -i complete
-iso UR -r <output_file> |
| Solution |
First Fixed in DB2 v10.5 FP7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.10.2014
20.01.2016
20.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
