FIX: A deadlock occurs when the scheduled SQL Server Agent job that you add or that you update is running in SQL Server 2000
Bug #: 310 (SQL Hotfix) Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release. On This PageSUMMARYThis article describes the following about this hotfix release:
SYMPTOMSConsider the following scenario. In Microsoft SQL Server 2000, you add a SQL Server Agent job, or you update a SQL Server Agent job. At the same time, another connection tries to delete a SQL Server Agent job. In this scenario, a deadlock occurs when the scheduled SQL Server Agent job that you add or that you update is running. If you troubleshoot the deadlock by enabling trace flag 1204, you notice that the following error message is logged in the SQL Server error log file: Deadlock encountered .... Printing deadlock information
…
Date Time SPID Node:1 … Date Time SPID SPID: 77 ECID: 0 Statement Type: DELETE Line #: 124 Date Time SPID Input Buf: Language Event: EXECUTE msdb.dbo.sp_delete_job @job_id = 0x9D8193BA4AB3E84381F15C1701991638 … Date Time SPID Node:2 … Date Time SPID SPID: 52 ECID: 0 Statement Type: SELECT Line #: 19 Date Time SPID Input Buf: Language Event: EXECUTE msdb.dbo.sp_sqlagent_refresh_job @job_id = 0x44C826041DA74947A7BFD1365474B5FB Date Time SPID Victim Resource Owner: Date Time SPID ResType:LockOwner Stype:'OR' Mode: S SPID:52 ECID:0 Ec:(0x36829558) Value:0x5b7084a0 Cost:(0/0) CAUSEThis problem occurs because SQL Server Agent does not schedule the SQL Server Agent job to run in the job cache. When SQL Server Agent runs the scheduled SQL Server Agent job, SQL Server Agent uses the sp_sqlagent_refresh_job stored procedure to update the job cache. If another connection tries to delete a SQL Server Agent job, a deadlock occurs. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.Prerequisites
Registry informationYou do not have to change the registry.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 (http://support.microsoft.com/kb/822499/)
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 (http://support.microsoft.com/kb/824684/)
Description of the standard terminology that is used to describe Microsoft software updates
For more information about trace flag 1204, visit the following Microsoft Developer Network (MSDN) Web site:http://msdn2.microsoft.com/en-us/library/aa937573(sql.80).aspx (http://msdn2.microsoft.com/en-us/library/aa937573(sql.80).aspx) APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
