DB2 - Problem description
Problem IT27868 | Status: Closed |
IN CERTAIN SITUATION ON PURESCALE, "DIA8132C CONDITIONAL LOCK ERROR? MAY BE REPORTED AS ERROR, WHICH SHOULD BE AT WARNING LEVE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
IN PURESCALE, "DIA8132C Conditional lock error? MAY BE REPORTED AS ERROR LEVEL with the following message patterns. 20XX-XX-XX-23.10.12.919865+660 I41392E785 LEVEL: Error ..,, EDUID : 202 EDUNAME: db2loggr (XXXX) 0 FUNCTION: DB2 UDB, data protection services, sqlpgReadStartUse, probe:1100 MESSAGE : ZRC=0x80100079=-2146434951=SQLP_LCON "Conditional Conflict" DIA8132C Conditional lock error occurred, lock name was "". DATA #1 : String, 35 bytes logStreamId / extentNum / lockMode: DATA #2 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes X DATA #3 : unsigned integer, 4 bytes XXXX DATA #4 : Lock Mode, PD_TYPE_SQLP_LOCK_MODE, 8 bytes SQLP_LOOX (..X) - Exclusive Lock In certain scenarios, the message does not need to be concerned and can be treated as WARNING LEVEL. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.01.2019 16.01.2020 16.01.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |