SQL Blocking detected Warning

[allanaklepko]

Hello, does anyone know if we need to worry about this warning?  There aren't much details provided in the error log.

Summary: SQL Blocking detected: Database Name: , Request Session ID: 72, Blocking Session ID: 12, Blocked Object Name: , Resource Type: FILE: 9:0, Requesting Text: , Blocking Text: , Request Mode: , Blocking Time: 12/2/2023 8:05:57 AM.

Thank you,

[NicolasArgente]

Hi @allanaklepko 
The warning you've received about SQL blocking is indeed something that requires attention. SQL blocking occurs when one database transaction (in this case, from Session ID 72) is prevented from proceeding because another transaction (Session ID 12) is using a resource that the first transaction needs. This can lead to performance issues and, in severe cases, database deadlocks, where two or more transactions permanently block each other.
I would suggest that you investigate first on your side before contacting support. any patterns or additional details they observe. Please document any patters or event. For instance, if the blocking occurs at specific times or under certain operational conditions, this information can be very useful for the technical team. Analyse the logs and the activity that happens at the same time. Review the Business Rules and Data Adaptors that are running at the same time. After doing this, you can report to support.
Hope it helps,
Nic

[allanaklepko]

Thanks Nicolas, are these OneStream session ID numbers? Where can i cross reference the action that may be causing the warnings?

 Task activity details are are tracked by 'Thread ID', not session ID.

[NicolasArgente]

Hi @allanaklepko 
Those ID will not make sense to us as admins/users. They are intended for the OS Support made by the SQL Server.
However, we need to know when they happen. For example, is it everyday at the same time? Is it when you open a cube view? When you rune a business rule, A consolidation? 
Lets assume the error happens at 13h04. Have a look at the task activity to see anything running before 13h04. Then do the same with the error log right before 13h04.
The idea is to bring context to this errror as it should help support o.
Hope it helps 

[allanaklepko]

The warning has occurred 3 times, but it refers to the same blocking event at 8:05 am on Dec 2nd.  Nothing was happening in the system on that date, other than recycling of app servers - so that could be the cause.

[NicolasArgente]

Can you look at the error log and task activity of the 2nd of December around 8:05am ? Do you see anything? Can you send us a printscreen?

[allanaklepko]

[NicolasArgente]

Hi @allanaklepko My understanding is that it happened only once and it was during a recycling. I would not worry on that one.

[allanaklepko]

I have attached a photo.  Nothing happening at 8:05am in the task scheduler, other than recycling of servers overnight.  We are in the Eastern time zone.