DB2 - Problem description
Problem IC75129 | Status: Closed |
UNDER HIGH PARALLEL QUERY LOAD , NSE FAILS TO RELEASE FEW LOCKS WHICH CAN EVENTUALLY LEAD TO CTE0119 ERROR | |
product: | |
DB2 NET SEARCH / 5765F3800 / 910 - DB2 | |
Problem description: | |
After installation of fixpack 9 customer experienced CTE0119 errors for several times. Each time he must stop and restart NSE due to resolve the issue. He also increased maxLocksPerIdx to 800 in db2extlm.cfg file. But the problem still happens. CONTROL LIST ALL LOCKS ... almost never shows any locks. Only sometimes LIST ALL LOCKS shows a S-lock. CONTROL LIST ALL LOCKS shows also no locks even when cte0119 was thrown and each search for the both indexes failed until stopping NSE (db2text stop force). So he assumes that CONTROL CLEAR ALL LOCKS can not resolve the problem too (because LIST can not see the locks). | |
Problem Summary: | |
UNDER HIGH PARALLEL QUERY LOAD , NSE FAILS TO RELEASE FEW LOCKS WHICH CAN EVENTUALLY LEAD TO CTE0119 ERROR | |
Local Fix: | |
Nonr | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows | |
Solution | |
Upgrade to V91fp11 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.03.2011 28.11.2011 28.11.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP11 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.11 |