DB2 - Problembeschreibung
Problem IC73185 | Status: Geschlossen |
DB2 MIGHT ENCOUNTER 'DEAD LATCH' ISSUE AND INSTANCE WILL HANG. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
To identify the problem, issue 'db2fodc -hang' command to generate diagnostic information. Then in stack files you will see 2 agents similar to the followings: ================================ <StackTrace> sqloXlatchConflict sqlpm_write_appl_locks sqm_snap_appl_locks sqm_snap_db_locks sqlmonssagnt <LatchInformation> Waiting on latch type: (SQLO_LT_SQLP_TENTRY__tranEntryLatch) - Address: (7000001bc956e68), Line: 748, File: /view/db2_v97fp2_aix64_s100514/vbs/engn/include/sqlpi_inlines.h Holding Latch type: (SQLO_LT_sqeLocalDatabase__dblatch) - Address: (780000000780328), Line: 395, File: sqlmutil.C HoldCount: 1 Holding Latch type: (SQLO_LT_sqeAppServices__m_appServLatch) - Address: (7800000002f04f8), Line: 7822, File: sqlmonss.C HoldCount: 1 Holding Latch type: (SQLO_LT_sqeApplication__masterAppLatch) - Address: (7000002513101c4), Line: 327, File: /view/db2_v97fp2_aix64_s100514/vbs/engn/include/sqle_app_service s.h HoldCount: 1 ... <StackTrace> sqloXlatchConflict sqlkdDispatchRequest sqlkdInterrupt sqlrr2pd sqlrkcmt sqlrkcm sqlrrcom_dps sqlrr_xcommit <LatchInformation> Waiting on latch type: (SQLO_LT_sqeApplication__masterAppLatch) - Address: (7000002513101c4), Line: 997, File: /view/db2_v97fp2_aix64_s100514/vbs/engn/include/sqle_application .h Holding Latch type: (SQLO_LT_SQLP_TENTRY__tranEntryLatch) - Address: (7000001bc956e68), Line: 748, File: /view/db2_v97fp2_aix64_s100514/vbs/engn/include/sqlpi_inlines.h HoldCount: 1 ================================ The deadlatch is constructed by 'masterAppLatch' and 'tranEntryLatch'. You will have to recycle the instance to get out of the 'dead latch' situation. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * To identify the problem, issue 'db2fodc -hang' command to * * generate diagnostic information. Then in stack files you * * will see 2 agents similar to the followings: * * ================================ * * <StackTrace> * * sqloXlatchConflict * * sqlpm_write_appl_locks * * sqm_snap_appl_locks * * sqm_snap_db_locks * * sqlmonssagnt * * * * <LatchInformation> * * Waiting on latch type: (SQLO_LT_SQLP_TENTRY__tranEntryLatch) * * - Address: (7000001bc956e68), Line: 748, File: * * /view/db2_v97fp2_aix64_s100514/vbs/engn/include/sqlpi_inlines. * * * Holding Latch type: (SQLO_LT_sqeLocalDatabase__dblatch) - * * Address: (780000000780328), Line: 395, File: sqlmutil.C * * HoldCount: 1 * * Holding Latch type: (SQLO_LT_sqeAppServices__m_appServLatch) * * - Address: (7800000002f04f8), Line: 7822, File: sqlmonss.C * * HoldCount: 1 * * Holding Latch type: (SQLO_LT_sqeApplication__masterAppLatch) * * - Address: (7000002513101c4), Line: 327, File: * * /view/db2_v97fp2_aix64_s100514/vbs/engn/include/sqle_app_servi * HoldCount: 1 * * * * ... * * * * <StackTrace> * * sqloXlatchConflict * * sqlkdDispatchRequest * * sqlkdInterrupt * * sqlrr2pd * * sqlrkcmt * * sqlrkcm * * sqlrrcom_dps * * sqlrr_xcommit * * * * <LatchInformation> * * Waiting on latch type: * * (SQLO_LT_sqeApplication__masterAppLatch) - Address: * * (7000002513101c4), Line: 997, File: * * /view/db2_v97fp2_aix64_s100514/vbs/engn/include/sqle_applicati * * * Holding Latch type: (SQLO_LT_SQLP_TENTRY__tranEntryLatch) - * * Address: (7000001bc956e68), Line: 748, File: * * /view/db2_v97fp2_aix64_s100514/vbs/engn/include/sqlpi_inlines. * HoldCount: 1 * * ================================ * * The deadlatch is constructed by 'masterAppLatch' and * * 'tranEntryLatch'. * * * * You will have to recycle the instance to get out of the * * 'dead latch' situation. * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 version 9.7 fp 4 * **************************************************************** | |
Local-Fix: | |
The problem only occurs when you're getting snapshot. So it can be avoided if you don't get any snapshot. | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 10.12.2010 10.12.2010 10.12.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP4 | |
Problem behoben lt. FixList in der Version |