Have you ever noticed "PREEMPTIVE_XE_CALLBACKEXECUTE" wait type on one of your SPID which is not letting you perform any operation at SQL Server instance???
I have seen this wait type when using SQL Server auditing and it seems that transaction is stuck and blocking meta deta. The exclusive lock was placed on sysclsobj in master database
If you try to see corresponding OS thread(KPID), you would notice that thread actually belongs to sql server agent task.
Below are some additional findings :
SPID for server audit is blocking all other instance level operation
Stopping and restarting sql server agent job does nothing
"PREEMPTIVE_XE_CALLBACKEXECUTE" reflects that sql thread is waiting on OS level resource
Eventually there is no wait resource
This is a bug in SQL Server 2008 R2 SP1 and is fixed in CU 6 : ): )
Puneet
No comments:
Post a Comment