assertion failed


Noticed below error in application logs,

SQL Server Assertion: File: <"logk.cpp">, line=1235 Failed Assertion = 'lfh->lfh_startOffset == lfcb->lfcb_startOffset'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not

can you please advise the reason and remedy for the same error.
more ▼

asked Feb 18, 2011 at 01:13 AM in Default

pits gravatar image

830 83 91 92

(comments are locked)
10|1200 characters needed characters left

3 answers: sort voted first
Follow the error messages suggestion and run DBCC CHECKDB on the database.
more ▼

answered Feb 18, 2011 at 01:19 AM

Kev Riley gravatar image

Kev Riley ♦♦
53.9k 47 49 76

ok,but what is the issue and how the dbcc checkdb will help?
Feb 18, 2011 at 01:26 AM pits
The issue is something within the internals of SQL - it has detected an issue using assertions - an assertion is a check or presumption that SQL relies on, if the assertion fails, the engine raises an error. DBCC CHECKDB will run various integrity checks on your database - the output from that will determine what, if anything, you need to do.
Feb 18, 2011 at 01:31 AM Kev Riley ♦♦
(comments are locked)
10|1200 characters needed characters left
Since it could be "... timing-related ...", it might be caused by an external event like an IO burst. In that case, it's not structural. But I do recommend a DBCC CHECKDB action (actually you should run this on a regularly base)
more ▼

answered Feb 18, 2011 at 02:34 AM

Wilfred van Dijk gravatar image

Wilfred van Dijk
1.3k 20 25 31

+1 - for sure on all points. DBA == paranoid
Feb 18, 2011 at 02:48 AM Fatherjack ♦♦
(comments are locked)
10|1200 characters needed characters left

aside from the cause/remedy I would recommend:
1 - preserving all your existing backups - dont overwrite or delete any until this is all wrapped up and you have a healthy database/server.
2 - making a backup of all your databases (see note 1, dont overwrite any existing backups)
3 - READING about CHECKDB in BOL, understand its function, options and effects.
4 - run CHECKDB
5 - celebrate that all databases are fine, back them all up again as per normal backup procedures

It is likely to be nothing but if you have encountered bad pages on a disk you need to ready for anything with as many good backups as you can put your hands on.
more ▼

answered Feb 18, 2011 at 02:26 AM

Fatherjack gravatar image

Fatherjack ♦♦
42.8k 75 79 108

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

New code box

There's a new way to format code on the site - the red speech bubble logo will automatically format T-SQL for you. The original code box is still there for XML, etc. More details here.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.



asked: Feb 18, 2011 at 01:13 AM

Seen: 1719 times

Last Updated: Feb 18, 2011 at 01:13 AM