Blocking object that is causing a shared lock is not seen in Blocking History (4229345)

Chatee ahora con Soporte

Regresar

Comentarios enviados

¿Este artículo solucionó su problema?

Seleccionar calificación

Título

Blocking object that is causing a shared lock is not seen in Blocking History
Descripción

Blocking object that is causing a shared lock is not seen in Blocking History.
Scenario
There are two queries master database that are waiting 100% of the time for a lock. Normally those queries are visible somewhere in the blocking chain on Blocking History and the user can see who these queries were waiting on. But when looking at Blocking History only these two are the leader blockers (not waiting on anything).
Is there something wrong with the data it gathered?
Resolución

This is an example of how the blocking display works, in that it assumes the blocking query is the last batch run in the session.
However, if the session runs another fast batch in the same session that actually holds the lock and then immediately runs another query then this last query will be listed as the offending query, even though it was blocked by the previous statement.
Note: We believe that this session in the scenario was being run by an application using JDBC or ODBC API and running two statements in the same session.

Comentarios enviados

¿Este artículo solucionó su problema?

Seleccionar calificación

Contenido recomendado

Producto(s):: Foglight
6.1.0, 6.0.0, 5.9.8, 5.9.7, 5.9.5, 5.9.4, 5.9.3, 5.9.2, 5.7.5; Foglight Evolve
6.1.0, 6.0.0, 9.3, 9.2, 9.1, 9.0; Foglight for Databases
6.1.0, 6.0.0, 5.9.7, 5.9.5, 5.9.4, 5.9.3, 5.9.2; Foglight for Virtualization Enterprise Edition
8.9.3, 8.9.2, 8.9.1, 8.9, 8.8.5, 8.8, 8.7.5, 8.7

Historial del artículo:: Creado el: 10/14/2019
Última actualización: 5/7/2023

Título