DB2 - Problem description
Problem IC84198 | Status: Closed |
DB2 may encounter 'deadlock' on system catalog SYSIBM.SYSCOLAUTH when performing two DROP TABLE statements simultaneously. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Deadlocks on system catalog may occur when concurrently perform two DROP TABLE statements on two different tables. To identify the problem, you need to use DB2 event monitor to collect detailed information for deadlocks. When the deadlock error occurs, in the event monitor output you will see the following entries: ============================================= Table of lock waited on : SYSPLANDEP Schema of lock waited on : SYSIBM Type of lock: Row Mode of lock: X - Exclusive Mode application requested on lock: S - Share Text : drop table NEWTON.T1 Table of lock waited on : SYSCOLAUTH Schema of lock waited on : SYSIBM Type of lock: Row Mode of lock: U - Update Mode application requested on lock: U - Update Text : drop table NEWTON.T2 ============================================= | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users of version 10.1 on Linux, Unix and Windows * * platforms. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW Version 10.1 FixPak 1 or higher levels. * **************************************************************** | |
Local Fix: | |
Perform the two DROP TABLE statements sequentially. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 LUW Version 10.1 FixPak 1. | |
Workaround | |
Perform the two DROP TABLE statements sequentially. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.06.2012 23.06.2013 23.06.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |