suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT26394 Status: Closed

DB2 TAKES Z LOCK WHEN ATTACHING PARTITION TO TABLE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Command such as
ALTER TABLE MYSCHEMA.TESTTABLE ATTACH PARTITION
STARTING('2018-01-25') ENDING('2018-01-25') FROM
MYSCHEMA.TESTTABLE1

May result in.
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL0911N The current transaction has been rolled back because of
a deadlock
or timeout. Reason code "68". SQLSTATE=40001

This may due to a z lock that should not be acquired during the
process. This can happen when a table has columns with default
values that is being attached to the partition table with
different default values. This triggers an ALTER TABLE under the
covers that acquires the z-lock and conflicts with the lock held
by the attach partition.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* upgrade to version 11.1 M4FP5                                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT30061 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.09.2018
22.08.2019
22.08.2019
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)