question

pits avatar image
pits asked

assertion failed

Hello, Noticed below error in application logs, SQL Server Assertion: File: , 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.
errormessage
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Kev Riley avatar image
Kev Riley answered
Follow the error messages suggestion and run DBCC CHECKDB on the database.
2 comments
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

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.
1 Like 1 ·
ok,but what is the issue and how the dbcc checkdb will help?
0 Likes 0 ·
Fatherjack avatar image
Fatherjack answered
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.
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Wilfred van Dijk avatar image
Wilfred van Dijk answered
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)
1 comment
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

+1 - for sure on all points. DBA == paranoid
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.