DB2 - Problem description
Problem IC96975 | Status: Closed |
With Currently committed semantics disabled a statement may incorrectly fail with SQL0901N ( REASON "IMPROPER LOCKING" ) | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
With currently committed semantics disabled (CUR_COMMIT=DISABLED in the database configuration), for specific access plans (related to predicate pushdown), a statement may fail to compile with the following error message: SQL0901N The SQL statement or command failed because of a database system error. (Reason "Improper locking".) SQLSTATE=5800 The db2diag.log will show: 2013-08-13-02.50.31.077507-240 I4695A873 LEVEL:Severe PID : 26869962 TID : 2315 PROC :db2sysc INSTANCE: db2inst1 NODE : 000 DB :SAMPLE APPHDL : 0-7 APPID:*LOCAL.db2inst1.130813064915 AUTHID : db2inst1 HOSTNAME: db2debug EDUID : 2315 EDUNAME: db2agent (SAMPLE) FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,probe:300 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 16 sqlerrmc: Improper locking sqlerrp : SQLNG22B sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)0x00000000 (4) 0x000082CC (5) 0xFFFFFC6E (6)0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: As part of the error, a FODC_AppErr_<timestamp> subdirectory is generated in the DIAGPATH with the top function in the stack trace : sqlngPushdownCB::generate sqlng_build_thread sqlng_build_TA_op sqlng_process_f_iscan sqlng_process_fetch_op sqlngProcessLolepop | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5 and Fix Pack 4 or higher. * **************************************************************** | |
Local Fix: | |
Enable currently committed semantics (CUR_COMMIT=ON) | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 version 10.5 and Fix Pack 4. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.10.2013 08.09.2014 08.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |