| Author |
Message |
ChrisAVWood
Joined: 18 Dec 2007
Posts: 308
Location: Edmonton, Alberta, CANADA
|
 Posted: Fri Jul 04, 2008 5:46 pm Post subject: Wait Type MSQL_XP on a log backup job |
 |
|
Hi,
Running 5.3.0.178 on SQL2005 build 3239 I have a job that is stuck with a waittype of MSQL_XP. I understand this means waiting on an extended stored procedure, in this case sqlbackup. All the other backup jobs have run successfully while this one just waits.
Any ideas?
Thanks
Chris
_________________
English DBA living in CANADA |
|
| Back to top |
|
 |
ChrisAVWood
Joined: 18 Dec 2007
Posts: 308
Location: Edmonton, Alberta, CANADA
|
| Posted: Fri Jul 04, 2008 7:07 pm Post subject: |
|
|
I had cancelled the original SQL Agent job and this worked after a while. The spid is still there and a KILL spid id WITH STATUSONLY shows an estimated rollback completion of 0% but the backup job has now run successfully the next time is was scheduled in SQL Agent. Red Gate GUI shows it still running. Strange.
Chris
_________________
English DBA living in CANADA |
|
| Back to top |
|
|
shawnnwf
Joined: 03 May 2007
Posts: 12
|
| Posted: Thu Jul 24, 2008 10:28 pm Post subject: |
|
|
| I am having the same issue. Any update on the issue or a resolution? |
|
| Back to top |
|
|
ChrisAVWood
Joined: 18 Dec 2007
Posts: 308
Location: Edmonton, Alberta, CANADA
|
| Posted: Mon Jul 28, 2008 3:21 pm Post subject: |
|
|
Red Gate have sent me a new version of SQLBackup. This is supposed to fix this problem yet I had only seen it once so proving it fixes the problem will not be easy.
Chris
_________________
English DBA living in CANADA |
|
| Back to top |
|
|
joetig
Joined: 25 Mar 2009
Posts: 8
|
| Posted: Thu Mar 26, 2009 2:56 pm Post subject: Unable to Kill Process with Wait Type MXSQL_XP |
|
|
We have also encountered the same issue. I recently created a job to email us when it has detected that a job has been running longer than the max time + 20% in the past week.
Upon implementation, I discovered two processes that are runnable. When I perform an dbcc inputbuffer on these tasks, they show up as the execute sqlbackup command. Both of these processes have been in the system for over 30 days.
I attempted to kill the process, but it did nothing, now it appears as killed/rolledback. I restarted both the sql agent and the redgate and neither one helped.
It looks like only the restarting of the server will be my last alternative which I will wait for some scheduled downtime.
Does anybody have any ideas? |
|
| Back to top |
|
|
ChrisAVWood
Joined: 18 Dec 2007
Posts: 308
Location: Edmonton, Alberta, CANADA
|
| Posted: Fri Mar 27, 2009 2:54 pm Post subject: |
|
|
Joetig,
You don't mention what version you are running?
Chris
_________________
English DBA living in CANADA |
|
| Back to top |
|
|
joetig
Joined: 25 Mar 2009
Posts: 8
|
| Posted: Fri Mar 27, 2009 4:02 pm Post subject: |
|
|
Version v5.3.0.178 same as previous post. I received version upgrade to 5.4.
My issues is with the processes that appear when you run sp_who2. They are not running, they can't be killed [it appears as killed\rollback]. |
|
| Back to top |
|
|
ChrisAVWood
Joined: 18 Dec 2007
Posts: 308
Location: Edmonton, Alberta, CANADA
|
| Posted: Sun Mar 29, 2009 3:06 am Post subject: |
|
|
Joetig,
Version 5.4 I believe should fix the problem. I certainly haven't had it since upgrading to 5.4
Chris
_________________
English DBA living in CANADA |
|
| Back to top |
|
|
joetig
Joined: 25 Mar 2009
Posts: 8
|
| Posted: Sun Mar 29, 2009 1:57 pm Post subject: |
|
|
| Yes, that is good to hear. But, how do you get rid of the processes that still show in sp_who2. They cannot be killed and I am trying to avoid restrting the sql server. |
|
| Back to top |
|
|
ChrisAVWood
Joined: 18 Dec 2007
Posts: 308
Location: Edmonton, Alberta, CANADA
|
| Posted: Mon Mar 30, 2009 3:59 pm Post subject: |
|
|
Joetig,
We reboot our servers at least once a month for Microsoft Patch Maintenance so that probably would have killed the orphaned process. It happened a long time ago and I do not have exact records.
Sorry
Chris
_________________
English DBA living in CANADA |
|
| Back to top |
|
|
joetig
Joined: 25 Mar 2009
Posts: 8
|
| Posted: Mon Mar 30, 2009 4:33 pm Post subject: |
|
|
| Yes, that is what we thought. I guess we will have to wait for the next maintenance window. |
|
| Back to top |
|
|
joetig
Joined: 25 Mar 2009
Posts: 8
|
| Posted: Mon Jan 25, 2010 3:03 pm Post subject: SPID wont go away |
|
|
Upgraded from Version v5.3.0.178 to 5.4.0.55
The issue went away for 9 months, but has come back in the last week or so.
The only difference is we applied SP2 CU12 service pack to SQL 2005 this past december
Do we have any solutions for this problem?
 |
|
| Back to top |
|
|
joetig
Joined: 25 Mar 2009
Posts: 8
|
| Posted: Tue Feb 02, 2010 2:18 pm Post subject: Version Upgrade issue |
|
|
We found the issue. It appears that after applying the cu12 service pack, the machine was failed over. The other server was not running the 5.4.0.55 version. We suspect that the original redgate cluster upgrade did not work properly.
We are now running on version 5.4.0.55 |
|
| Back to top |
|
|
|
