home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC96975 Status: Geschlossen

With Currently committed semantics disabled a statement may incorrectly
fail with SQL0901N ( REASON "IMPROPER LOCKING" )

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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)
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 version 10.5 and Fix Pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.10.2013
08.09.2014
08.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList