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 IT06754 Status: Geschlossen

RUNNING TWO IDENTICAL ANONYMOUS BLOCK STATEMENT MAY RETURN SQL0901N
"NOT ABLE TO LOCK VAR"

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When running two identical statements via anonymous block, 
SQL0901N "Not able to lock var" may be returned due to a small 
timing hole in the locking protocol. 
 
The following message can be found in the db2diag.log: 
 
2015-01-16-10.53.19.008435+540 I48209136A878        LEVEL: 
Severe 
PID     : 34734                TID : 2274210343184  PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : DB01 
APPHDL  : 0-13550              APPID: *LOCAL.DB2.150130164857 
AUTHID  : USER01               HOSTNAME: HOST01 
EDUID   : 10922                EDUNAME: db2agent (DB01_ONL) 0 
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: 20 
 sqlerrmc: Not able to lock var 
 sqlerrp : SQLRA06A 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFB82      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
The following call stack can be found in the FODC_AppErr 
directory: 
 
0x0000020004DD54FC _Z13sqlzeDumpFFDCP8sqeAgentjP5sqlcai + 0x00f0 
0x0000020004DD58F6 
_Z12sqlzeSqlCodeP8sqeAgentjmjP5sqlcaitP13__va_list_tag + 0x019e 
0x0000020003C6FB0C sqlrrSqlCode + 0x0148 
0x0000020003DB5A6C 
_Z18sqlra_find_var_varP8sqlrr_cbP17sqlra_cached_stmtPP16sqlra_ca 
ched_envP14sqlra_cmpl_en 
vjii15sqlra_fill_modePiiS9_S9_P14SQLP_LOCK_INFOSB_PP16sqlra_cach 
ed_varS9_S9_S9_S9_bbPjSF_ + 0x082c 
0x0000020003DB9458 
_Z14sqlra_find_varP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idj 
jPhjthP14sqlra_cmpl_env1 
5sqlra_fill_modePiiS8_iiiS8_P14SQLP_LOCK_INFOPP16sqlra_cached_va 
rS8_b + 0x04e0 
0x0000020003E4CC6E _Z13sqlra_get_varP8sqlrr_cbiibPbS1_ + 0x1b02 
0x0000020003B899BE 
_Z13sqlrr_prepareP14db2UCinterfaceP16db2UCprepareInfo + 0x0416 
0x0000020003E6AA5E _Z25sqlraProcessPrepAnonBlockPvP5sqlca + 
0x009e
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* anonymous block statement user                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 10.1 FixPack 5 or higher              * 
****************************************************************
Local-Fix:
Avoid running the same anonymous block statement concurrently.
Lösung
Problem was first fixed in Version 10.1 FixPack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.01.2015
15.07.2015
15.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList