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

-901 ERROR WITH TEXT "WITH HOLD BUT USAGE LOCK ARGUMENT NULL"
REPORTED BY SQLRLC_REQUEST_ULOCK() AS CALLED BY SQLRLC_FED_FETCH()

Produkt:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problembeschreibung:
SELECT referencing SYSCAT.INDEX of a federated object might 
hang/crash with SQL0901N. 
 
-------Stack-------- 
0x090000000057EF14 pthread_kill + 0xD4 
0x0900000040D15FFC sqloDumpEDU + 0x9C 
0x0900000041943630 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 + 
0x150 
0x0900000042C59334 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x914 
0x0900000040E741B8 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x158 
0x0900000040E73C9C sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 
0x27C 
0x0900000040E7078C sqlrrSqlCode + 0x18C 
0x0900000043397978 
sqlrlc_request_ulock__FP8sqlrr_cbP19sqlrlc_entry_commonP20sqlrlc 
_anchor_commonPbUiN25PUiP14SQLP_LOCK_INFOT9T8 + 0x1D8 
0x0900000043396EE4 
sqlrlc_find_request_usage_lock__FP8sqlrr_cbP10sqlrlc_keyUiN23PP1 
9sqlrlc_entry_commonPUiP14SQLP_LOCK_INFOT8 + 0x664 
0x090000004592F82C 
sqlrlc_fed_fetch__FP8sqlrr_cbPUcUsT2T3T2T3UiN28P13SQLO_MEM_POOLP 
14SQLP_LOCK_INFOP21sqlrlc_systables_info + 0x3AC 
0x090000004592D7E4 
sqlnq_cat_look2__FCP20sqlnq_multipart_nameCPP9sqlnq_ftbP3loc21sq 
lnq_hierarchy_usageCbCPCUiP12sqlnq_stringT5 + 0x4F04 
0x090000004592756C 
sqlnq_cat_look__FCP20sqlnq_multipart_nameCPP9sqlnq_ftbP3loc21sql 
nq_hierarchy_usageCbCPCUiP12sqlnq_stringT5 + 0x2EC 
0x090000004386B1F4 
sqlnq_handle_qtb_extref_rec__F20sqlnq_multipart_namePP9sqlnq_qtb 
iP3loc21sqlnq_hierarchy_usageP9sqlnq_pid + 0x114 
0x090000004386EA0C 
IPRA.$sqlnq_handle_named_ref__F20sqlnq_multipart_nameiP9sqlnq_qt 
bP9sqlnq_oprT2PP9sqlnq_qtbPP9sqlnq_qunPP9sqlnq_qncPP9sqlnq_pidT6 
Pi21sqlnq_hierarchy_usageP9sqlnq_pid + 0x4EC 
0x090000004386EDB8 
IPRA.$sqlnq_handle_named_ref__F20sqlnq_multipart_nameiP9sqlnq_qt 
bP9sqlnq_oprT2PP9sqlnq_qtbPP9sqlnq_qunPP9sqlnq_qncPP9sqlnq_pidT6 
Pi21sqlnq_hierarchy_usageP9sqlnq_pid + 0x898 
0x090000004386EDB8 
IPRA.$sqlnq_handle_named_ref__F20sqlnq_multipart_nameiP9sqlnq_qt 
bP9sqlnq_oprT2PP9sqlnq_qtbPP9sqlnq_qunPP9sqlnq_qncPP9sqlnq_pidT6 
Pi21sqlnq_hierarchy_usageP9sqlnq_pid + 0x898 
0x090000004386D81C 
sqlnq_handle_named_ref_in_src__FP12sqlnq_stringiPP9sqlnq_qtbPP9s 
qlnq_qunPP9sqlnq_qncPP9sqlnq_pidP3loc21sqlnq_hierarchy_usageP20s 
qlnq_multipart_nameP9sqlnq_pid + 0x2FC 
0x09000000442157DC 
sqlnq_handle_table_ref__FP20sqlnq_multipart_namePP9sqlnq_qunP9sq 
lnq_qtbP3locP9sqlnq_opr21sqlnq_hierarchy_usageP9sqlnq_pid + 
0xADC 
0x09000000442143F8 
sqlnq_handle_from_table_ref__FP20sqlnq_multipart_namePUciPP9sqln 
q_qunP9sqlnq_qtbP3locP9sqlnq_opr21sqlnq_hierarchy_usagePP8stknod 
e_ + 0xF8 
0x090000004430B0F0 sqlnq_sem__FPP8stknode_i10actiontypePUcP3loc 
+ 0x7D70 
0x0900000044C7CFE4 sqlnp_smactn__FP8sqlnp_cbi + 0x424 
0x0900000044C74ED0 sqlnp_parser__FP8sqlnp_cb + 0x3D0 
0x0900000045D5C5A8 
sqlnp_main__FP12sqlnq_stringbP3locPP9sqlnq_qur + 0xDA8 
0x090000004571B174 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x8194 
... 
------------
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Fixpack 3 Mod 2 or higher                * 
****************************************************************
Local-Fix:
Lösung
First fixed in Db2 11.1 Fixpack 3 Mod 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.07.2018
07.08.2018
07.08.2018
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version