Select the product you need help with
FIX: Error message when SQL Server 2005 synchronizes a mirrored database: "Expression: result == LCK_OK"Article ID: 953625 - View products that this article applies to. Bug #: 50002736 (SQL Hotfix) Microsoft distributes Microsoft SQL
Server 2005 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 2005 fix
release. SYMPTOMSAn instance of SQL Server 2005 is configured to use database
mirroring. When SQL Server 2005 synchronizes a mirrored database, the database
mirroring session is broken. Additionally, the following error message is
logged in the SQL Server 2005 error log on the partner server: Date Time
SPID * BEGIN STACK DUMP:
Date Time SPID * 02/13/08 14:24:02 spid 130 Date Time SPID * Date Time SPID * Location: loglock.cpp:818 Date Time SPID * Expression: result == LCK_OK CAUSEThis issue occurs because lock escalation is
logged incorrectly
on the principal server. RESOLUTIONThe fix for this issue was first released in
Cumulative Update 8. For more information about how to obtain this cumulative
update package for SQL Server 2005 Service Pack 2, click the following article
number to view the article in the Microsoft Knowledge Base: 951217 Note Because the builds are cumulative, each new fix release contains
all the hotfixes and all the security fixes that were included with the
previous SQL Server 2005 fix release. Microsoft recommends that you consider
applying the most recent fix release that contains this hotfix. For more
information, click the following article number to view the article in the
Microsoft Knowledge Base:
(http://support.microsoft.com/kb/951217/LN/
)
Cumulative update package 8 for SQL Server 2005 Service Pack 2937137 Microsoft SQL Server 2005 hotfixes are created for specific SQL
Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to
an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that
is provided in a SQL Server service pack is included in the next SQL Server
service pack.
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
WORKAROUNDTo work around this issue, disable lock escalation for the
instance of SQL Server. To disable lock escalation, enable trace flag
1211. However, when you enable this trace flag, you disable all lock escalation globally for the
instance of SQL Server. Lock escalation maximizes
the efficiency of queries that are otherwise slowed down by the overhead of
acquiring and then releasing several thousand
locks. Lock escalation also
minimizes
the
memory that
is required to keep track of locks. The memory that SQL Server can dynamically allocate for lock structures is finite.
Therefore, if you disable lock escalation and the lock memory grows large
enough, attempts to allocate additional locks for any query may fail, and you may
receive the following error message:
Error: 1204, Severity: 19, State: 1 The SQL Server cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users or ask the system administrator to check the SQL Server lock and memory configuration" STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONFor more information about what
files are changed, and for information about any prerequisites to apply the
cumulative update package that contains the hotfix that is described in this
Microsoft Knowledge Base article, click the following article number to view
the article in the Microsoft Knowledge Base: 951217
(http://support.microsoft.com/kb/951217/LN/
)
Cumulative update package 8 for SQL Server 2005 Service Pack 2 REFERENCESFor more
information about the list of builds that are available after SQL Server
Service Pack 2, click the following article number to view the article in the
Microsoft Knowledge Base: 937137 For more information about the Incremental Servicing Model for SQL
Server, click the following article number to view the article in the Microsoft
Knowledge Base:
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
935897 For more information about how to obtain SQL Server 2005 Service
Pack 2, click the following article number to view the article in the Microsoft
Knowledge Base:
(http://support.microsoft.com/kb/935897/LN/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems913089 For more information about the new features and the improvements
in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/913089/LN/
)
How to obtain the latest service pack for SQL Server 2005 http://go.microsoft.com/fwlink/?LinkId=71711 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:
(http://go.microsoft.com/fwlink/?LinkId=71711)
822499 For more information about software update terminology, click the
following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/LN/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 953625 - Last Review: June 13, 2008 - Revision: 1.0 APPLIES TO
|
Back to the top
