FIX: You may experience concurrency issues when you run the DBCC INDEXDEFRAG statement in SQL Server 2000
Bug #: 474645 (SQL Server 8.0)
Microsoft distributes 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:
SYMPTOMSWhen you run the DBCC INDEXDEFRAG statement, null mode page
locks may accumulate on defragmented pages. These page locks may consume server
resources. Then, the transactions that accumulate the locks try to escalate the
page locks to table locks. The transactions escalate the page locks to try to
reduce server resource usage. Because the DBCC INDEXDEFRAG statement takes an
exclusive page lock and also causes the lock escalation to occur, you may
experience concurrency issues. Note You can use the sp_lock stored procedure to verify the mode of a lock. For a list of all publicly released Microsoft SQL Server 2000 Post-Service Pack 4 hotfixes, see the following article in the Microsoft Knowledge Base: 894905 (http://support.microsoft.com/kb/894905/) Cumulative list of the hotfixes that are available for SQL Server 2000 SP4
RESOLUTIONThe installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
Hotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Microsoft SQL Server 2000 service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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.PrerequisitesMicrosoft SQL Server 2000 Service Pack 4 (SP4)For information about how to obtain SQL Server 2000 SP4, see the following article in the Microsoft Knowledge Base: 290211 (http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack
Restart informationYou must restart the computer after you apply this hotfix.Registry informationYou do not have to make changes to the registry after you apply this hotfix.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 tool in Control Panel. SQL Server 2000, 32-bit versions
SQL Server 2000, 64-bit version
WORKAROUNDTo work around this problem, turn on trace flag 1211 on the
connection that runs the DBCC INDEXDEFRAG stored procedure. Trace flag 1211
prevents the transactions that accumulate the locks from escalating the page
locks to table locks. The null mode locks may still accumulate. If the null
mode locks accumulate, you may receive an error message that is similar to the
following: Error : 1204, Severity: 19, State: 3 SQL
Server has run out of LOCKS. Re-run your command when there are fewer active
users, or ask your System Administrator to reconfigure SQL Server with more
LOCKS Note We only recommend this workaround as a short-term solution. You should only turn on trace flag 1211 for the duration of the DBCC INDEXDEFRAG stored procedure. If you leave the trace flag on continuously, or if you use this trace flag as a startup parameter, you may experience additional issues from the side effects that are associated with this trace flag. We recommend that you only enable this trace flag for the duration of the DBCC INDEXDEFRAG stored procedure to avoid these issues.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 Microsoft 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
APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
